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.227.79.128/25 | 128 | RIPE NCC |  RU | 15th Sept 2011 |
| 91.227.8.0/22 | 1k | RIPE NCC | RU | 2nd May 2011 |
| 91.228.0.0/22 | 1k | RIPE NCC |  IE | 19th May 2011 |
| 91.228.10.0/24 | 256 | RIPE NCC |  MD | 7th Feb 2023 |
| 91.228.134.0/24 | 256 | RIPE NCC |  US | 11th Nov 2019 |
| 91.228.144.0/24 | 256 | RIPE NCC |  DE | 31st May 2011 |
| 91.228.149.0/24 | 256 | RIPE NCC | US | 11th Nov 2019 |
| 91.228.151.0/24 | 256 | RIPE NCC |  NL | 1st Jun 2011 |
| 91.228.160.0/24 | 256 | RIPE NCC | US | 11th Nov 2019 |
| 91.228.177.0/24 | 256 | RIPE NCC | RU | 6th Jun 2011 |
| 91.228.18.0/23 | 512 | RIPE NCC |  RS | 20th May 2011 |
| 91.228.184.0/24 | 256 | RIPE NCC | RU | 6th Jun 2011 |
| 91.228.192.0/24 | 256 | RIPE NCC |  IR | 22nd May 2025 |
| 91.228.206.0/24 | 256 | RIPE NCC | US | 11th Nov 2019 |
| 91.228.22.0/23 | 512 | RIPE NCC | IR | 3rd Oct 2019 |
| 91.228.226.0/24 | 256 | RIPE NCC | RU | 8th Jun 2011 |
| 91.228.237.0/24 | 256 | RIPE NCC |  PL | 9th Jun 2011 |
| 91.228.243.0/24 | 256 | RIPE NCC | DE | 9th Jun 2011 |
| 91.228.78.0/23 | 512 | RIPE NCC |  GB | 25th May 2011 |
| 91.228.80.0/22 | 1k | RIPE NCC | PL | 25th May 2011 |
| 91.229.101.0/24 | 256 | RIPE NCC |  UA | 20th Jun 2011 |
| 91.229.115.0/24 | 256 | RIPE NCC | UA | 20th Jun 2011 |
| 91.229.130.0/23 | 512 | RIPE NCC |  FR | 20th Jun 2011 |
| 91.229.140.0/24 | 256 | RIPE NCC |  CH | 20th Jun 2011 |
| 91.229.155.0/24 | 256 | RIPE NCC | UA | 25th Mar 2025 |
| 91.229.166.0/24 | 256 | RIPE NCC | GB | 21st Jun 2011 |
| 91.229.167.0/24 | 256 | RIPE NCC |  IT | 8th Oct 2025 |
| 91.229.180.0/24 | 256 | RIPE NCC | GB | 31st May 2023 |
| 91.229.181.0/24 | 256 | RIPE NCC | NL | 23rd Jun 2011 |
| 91.229.184.0/24 | 256 | RIPE NCC |  TR | 23rd Jun 2011 |
| 91.229.187.0/24 | 256 | RIPE NCC | GB | 23rd Jun 2011 |
| 91.229.2.0/24 | 256 | RIPE NCC | RU | 10th Jun 2011 |
| 91.229.201.0/24 | 256 | RIPE NCC | GB | 18th Nov 2024 |
| 91.229.204.0/22 | 1k | RIPE NCC | UA | 24th Jun 2011 |
| 91.229.211.0/24 | 256 | RIPE NCC | RU | 27th Jun 2011 |
| 91.229.225.0/24 | 256 | RIPE NCC |  SK | 27th Jun 2011 |
| 91.229.232.0/24 | 256 | RIPE NCC | NL | 28th Jun 2011 |
| 91.229.248.0/24 | 256 | RIPE NCC | DE | 11th Nov 2019 |
| 91.229.4.0/24 | 256 | RIPE NCC | GB | 10th Jun 2011 |
| 91.229.40.0/22 | 1k | RIPE NCC | PL | 15th Jun 2011 |
| 91.229.49.0/24 | 256 | RIPE NCC | NL | 15th Jun 2011 |
| 91.229.96.0/22 | 1k | RIPE NCC | RU | 17th Jun 2011 |
| 91.230.104.0/23 | 512 | RIPE NCC |  ES | 11th Jul 2011 |
| 91.230.123.0/24 | 256 | RIPE NCC |  RO | 12th Jul 2011 |
| 91.230.126.0/23 | 512 | RIPE NCC |  SE | 12th Jul 2011 |
| 91.230.128.0/22 | 1k | RIPE NCC | SE | 12th Jul 2011 |
| 91.230.132.0/24 | 256 | RIPE NCC | SE | 12th Jul 2011 |
| 91.230.151.0/24 | 256 | RIPE NCC | IT | 25th Nov 2024 |
| 91.230.158.0/24 | 256 | RIPE NCC |  SC | 2nd Jun 2025 |
| 91.230.162.0/23 | 512 | RIPE NCC | PL | 15th Jul 2011 |