Allocated but unannounced space
Every block here was allocated or assigned by a regional internet registry, and none of them appeared in any routing table we collected at our last snapshot — neither as a route of their own, nor covered by a larger announcement, nor carved up into more specifics.
“Unannounced” does not mean “unused”
Plenty of allocated space is deliberately kept off the public internet: private interconnects, lab and lawful-intercept ranges, networks reachable only inside one operator, and space held in reserve. Some of it is announced somewhere our collectors cannot see, which is a limit of our vantage points rather than a fact about the block.
It is also a snapshot, not a history: a block announced yesterday and withdrawn this morning appears here today. Nothing on this page means a block is unallocated, available, or free to announce.
Browse by registry
Browse by country
Countries with the most unannounced blocks, largest first.
Unannounced blocks
84,755 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 91.213.147.0/24 | 256 | RIPE NCC |  SI | 11th Aug 2009 |
| 91.213.154.0/24 | 256 | RIPE NCC |  UA | 13th Aug 2009 |
| 91.213.155.0/24 | 256 | RIPE NCC |  HK | 9th Aug 2021 |
| 91.213.159.0/24 | 256 | RIPE NCC |  CH | 17th Aug 2009 |
| 91.213.166.0/24 | 256 | RIPE NCC |  RU | 19th Aug 2009 |
| 91.213.171.0/24 | 256 | RIPE NCC | CH | 19th Aug 2009 |
| 91.213.182.0/24 | 256 | RIPE NCC |  TR | 19th May 2025 |
| 91.213.183.0/24 | 256 | RIPE NCC |  GB | 25th Aug 2009 |
| 91.213.206.0/24 | 256 | RIPE NCC |  PL | 7th Sept 2009 |
| 91.213.209.0/24 | 256 | RIPE NCC | UA | 10th Aug 2012 |
| 91.213.211.0/26 | 64 | RIPE NCC |  AE | 9th Apr 2026 |
| 91.213.211.128/26 | 64 | RIPE NCC |  NL | 3rd Jun 2026 |
| 91.213.211.192/26 | 64 | RIPE NCC |  OM | 6th Jul 2026 |
| 91.213.211.64/26 | 64 | RIPE NCC |  IL | 28th May 2026 |
| 91.213.214.0/24 | 256 | RIPE NCC |  US | 9th Sept 2009 |
| 91.213.216.0/24 | 256 | RIPE NCC | GB | 14th Sept 2009 |
| 91.213.228.0/24 | 256 | RIPE NCC |  GR | 17th Sept 2009 |
| 91.213.236.0/24 | 256 | RIPE NCC |  FR | 22nd Sept 2009 |
| 91.213.250.0/24 | 256 | RIPE NCC |  SE | 25th Sept 2009 |
| 91.213.255.0/24 | 256 | RIPE NCC | PL | 28th Sept 2009 |
| 91.213.3.0/24 | 256 | RIPE NCC | US | 10th Jun 2009 |
| 91.213.42.0/24 | 256 | RIPE NCC | GB | 2nd Jul 2009 |
| 91.213.45.0/24 | 256 | RIPE NCC | GB | 6th Jul 2009 |
| 91.213.47.0/24 | 256 | RIPE NCC |  NO | 7th Jul 2009 |
| 91.213.48.0/24 | 256 | RIPE NCC | RU | 9th Dec 2024 |
| 91.213.63.0/24 | 256 | RIPE NCC | GB | 14th Jul 2009 |
| 91.213.66.0/24 | 256 | RIPE NCC | NO | 28th Mar 2011 |
| 91.213.72.0/24 | 256 | RIPE NCC | NL | 8th Nov 2019 |
| 91.213.73.0/26 | 64 | RIPE NCC | PL | 2nd Apr 2026 |
| 91.213.73.128/26 | 64 | RIPE NCC | PL | 2nd Apr 2026 |
| 91.213.73.192/26 | 64 | RIPE NCC | PL | 2nd Apr 2026 |
| 91.213.73.64/26 | 64 | RIPE NCC | PL | 2nd Apr 2026 |
| 91.213.86.0/24 | 256 | RIPE NCC |  RO | 23rd Jul 2009 |
| 91.213.9.0/24 | 256 | RIPE NCC |  HU | 12th Jun 2009 |
| 91.213.93.0/24 | 256 | RIPE NCC | NL | 8th Nov 2019 |
| 91.213.94.0/24 | 256 | RIPE NCC | NL | 8th Nov 2019 |
| 91.214.113.0/24 | 256 | RIPE NCC | FR | 2nd Jun 2009 |
| 91.214.120.0/23 | 512 | RIPE NCC | RU | 3rd Jun 2009 |
| 91.214.212.0/22 | 1k | RIPE NCC | RU | 29th Jun 2009 |
| 91.214.232.0/22 | 1k | RIPE NCC | UA | 2nd Jul 2009 |
| 91.214.236.0/22 | 1k | RIPE NCC |  CY | 2nd Jul 2009 |
| 91.214.92.0/22 | 1k | RIPE NCC |  DE | 20th Apr 2018 |
| 91.214.96.0/22 | 1k | RIPE NCC | RU | 28th May 2009 |
| 91.215.100.0/22 | 1k | RIPE NCC | DE | 23rd Jul 2009 |
| 91.215.116.0/22 | 1k | RIPE NCC | DE | 28th Jul 2009 |
| 91.215.132.0/22 | 1k | RIPE NCC |  FI | 6th Aug 2009 |
| 91.215.168.0/22 | 1k | RIPE NCC | RU | 21st Aug 2009 |
| 91.215.212.0/22 | 1k | RIPE NCC | RU | 26th Aug 2009 |
| 91.215.228.0/22 | 1k | RIPE NCC | PL | 27th Aug 2009 |
| 91.215.240.0/22 | 1k | RIPE NCC |  AT | 1st Sept 2009 |