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.230.189.0/24 | 256 | RIPE NCC |  GB | 18th Jul 2011 |
| 91.230.190.0/24 | 256 | RIPE NCC |  VC | 18th Jul 2011 |
| 91.230.214.0/24 | 256 | RIPE NCC |  MD | 21st Jul 2011 |
| 91.230.216.0/24 | 256 | RIPE NCC |  CH | 27th Jan 2026 |
| 91.230.228.0/23 | 512 | RIPE NCC |  RU | 3rd Oct 2019 |
| 91.230.246.0/24 | 256 | RIPE NCC | GB | 28th Jul 2011 |
| 91.230.28.0/22 | 1k | RIPE NCC |  CA | 1st Jul 2011 |
| 91.230.33.0/24 | 256 | RIPE NCC |  NL | 1st Jul 2011 |
| 91.230.34.0/23 | 512 | RIPE NCC | NL | 1st Jul 2011 |
| 91.230.64.0/24 | 256 | RIPE NCC |  BE | 6th Jul 2011 |
| 91.230.74.0/24 | 256 | RIPE NCC |  PL | 6th Jul 2011 |
| 91.230.80.0/24 | 256 | RIPE NCC | GB | 14th Jan 2020 |
| 91.230.81.0/24 | 256 | RIPE NCC |  TR | 7th Jul 2011 |
| 91.231.114.0/23 | 512 | RIPE NCC | RU | 21st Sept 2011 |
| 91.231.142.0/23 | 512 | RIPE NCC |  SC | 3rd Oct 2019 |
| 91.231.144.0/24 | 256 | RIPE NCC |  IR | 26th Jan 2026 |
| 91.231.145.0/24 | 256 | RIPE NCC | RU | 7th May 2025 |
| 91.231.154.0/23 | 512 | RIPE NCC |  IE | 27th Sept 2011 |
| 91.231.180.0/24 | 256 | RIPE NCC | RU | 8th Jul 2021 |
| 91.231.181.0/24 | 256 | RIPE NCC |  UA | 8th Jul 2021 |
| 91.231.212.0/24 | 256 | RIPE NCC | GB | 19th Jun 2024 |
| 91.231.22.0/24 | 256 | RIPE NCC |  IT | 19th Dec 2023 |
| 91.231.34.0/24 | 256 | RIPE NCC | GB | 28th Apr 2020 |
| 91.231.46.0/24 | 256 | RIPE NCC | GB | 29th Aug 2011 |
| 91.231.52.0/24 | 256 | RIPE NCC | TR | 23rd Apr 2024 |
| 91.231.64.0/23 | 512 | RIPE NCC | RU | 13th Sept 2011 |
| 91.231.98.0/24 | 256 | RIPE NCC | UA | 20th Sept 2011 |
| 91.232.148.0/23 | 512 | RIPE NCC | GB | 10th Sept 2012 |
| 91.232.153.0/24 | 256 | RIPE NCC | GB | 18th Nov 2011 |
| 91.232.228.0/24 | 256 | RIPE NCC |  RO | 23rd Nov 2011 |
| 91.232.229.0/24 | 256 | RIPE NCC |  LI | 24th Nov 2011 |
| 91.232.24.0/23 | 512 | RIPE NCC | NL | 26th Oct 2011 |
| 91.232.244.0/23 | 512 | RIPE NCC | RU | 25th Nov 2011 |
| 91.232.80.0/24 | 256 | RIPE NCC | RU | 2nd Nov 2011 |
| 91.232.88.0/23 | 512 | RIPE NCC |  LU | 3rd Nov 2011 |
| 91.233.101.0/24 | 256 | RIPE NCC | UA | 7th Dec 2011 |
| 91.233.119.0/24 | 256 | RIPE NCC |  FR | 8th Dec 2011 |
| 91.233.124.0/24 | 256 | RIPE NCC | GB | 9th Dec 2011 |
| 91.233.126.0/24 | 256 | RIPE NCC | CH | 9th Dec 2011 |
| 91.233.130.0/23 | 512 | RIPE NCC | RO | 4th Oct 2019 |
| 91.233.132.0/22 | 1k | RIPE NCC | RU | 9th Dec 2011 |
| 91.233.16.0/24 | 256 | RIPE NCC | GB | 29th Nov 2011 |
| 91.233.198.0/24 | 256 | ARIN |  US | 5th Jun 2023 |
| 91.233.212.0/24 | 256 | RIPE NCC | RU | 30th Jul 2012 |
| 91.233.224.0/23 | 512 | RIPE NCC | NL | 19th Dec 2011 |
| 91.233.249.0/24 | 256 | RIPE NCC |  DE | 20th Dec 2011 |
| 91.233.38.0/23 | 512 | RIPE NCC | DE | 3rd Oct 2019 |
| 91.233.81.0/24 | 256 | RIPE NCC | GB | 6th Dec 2011 |
| 91.234.144.0/24 | 256 | RIPE NCC | PL | 24th Jan 2012 |
| 91.234.178.0/24 | 256 | RIPE NCC | RU | 26th Jan 2012 |