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
85,356 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 217.22.2.0/24 | 256 | RIPE NCC |  NO | 26th Jun 2026 |
| 217.22.3.0/24 | 256 | RIPE NCC |  NL | 26th Jun 2026 |
| 217.22.4.0/24 | 256 | RIPE NCC |  FR | 26th Jun 2026 |
| 217.22.6.0/24 | 256 | RIPE NCC |  UA | 26th Jun 2026 |
| 217.22.64.0/20 | 4.1k | RIPE NCC |  SE | 2nd Oct 2000 |
| 217.22.8.0/24 | 256 | RIPE NCC |  GB | 26th Jun 2026 |
| 217.22.9.0/24 | 256 | RIPE NCC |  RU | 26th Jun 2026 |
| 217.23.209.0/24 | 256 | RIPE NCC |  ES | 10th Mar 2003 |
| 217.23.210.0/23 | 512 | RIPE NCC | ES | 10th Mar 2003 |
| 217.23.212.0/22 | 1k | RIPE NCC | ES | 10th Mar 2003 |
| 217.23.216.0/21 | 2k | RIPE NCC | ES | 10th Mar 2003 |
| 217.23.96.0/20 | 4.1k | RIPE NCC |  DK | 5th Oct 2000 |
| 217.26.220.0/24 | 256 | RIPE NCC |  CY | 22nd Jan 2024 |
| 217.28.135.0/24 | 256 | RIPE NCC | NL | 13th Apr 2022 |
| 217.28.138.0/24 | 256 | RIPE NCC | NL | 13th Apr 2022 |
| 217.28.142.0/24 | 256 | RIPE NCC |  PL | 13th Apr 2022 |
| 217.29.196.0/22 | 1k | RIPE NCC | GB | 23rd Oct 2000 |
| 217.29.200.0/21 | 2k | RIPE NCC | GB | 23rd Oct 2000 |
| 217.64.240.0/20 | 4.1k | RIPE NCC |  BE | 17th Jun 2003 |
| 217.65.130.0/24 | 256 | RIPE NCC | FR | 26th Jan 2026 |
| 217.65.65.0/24 | 256 | RIPE NCC |  IT | 1st May 2025 |
| 217.65.69.0/24 | 256 | RIPE NCC |  CZ | 12th May 2025 |
| 217.65.71.0/24 | 256 | RIPE NCC | PL | 26th May 2025 |
| 217.65.74.0/24 | 256 | RIPE NCC | GB | 11th Jun 2025 |
| 217.67.32.0/20 | 4.1k | RIPE NCC |  DE | 8th Nov 2000 |
| 217.70.0.0/24 | 256 | RIPE NCC | DE | 30th Jul 2025 |
| 217.70.15.0/24 | 256 | RIPE NCC | IT | 24th Sept 2025 |
| 217.70.2.0/24 | 256 | RIPE NCC | CZ | 30th Jul 2025 |
| 217.70.5.0/24 | 256 | RIPE NCC | RU | 30th Jul 2025 |
| 217.70.8.0/24 | 256 | RIPE NCC | UA | 6th Aug 2025 |
| 217.70.9.0/24 | 256 | RIPE NCC | DE | 7th Aug 2025 |
| 217.71.160.0/20 | 4.1k | RIPE NCC | RU | 29th Jan 2007 |
| 217.72.12.0/22 | 1k | RIPE NCC | CY | 23rd Nov 2000 |
| 217.73.240.0/20 | 4.1k | RIPE NCC | PL | 7th Jul 2009 |
| 217.75.136.0/23 | 512 | RIPE NCC |  BG | 28th Dec 2000 |
| 217.75.138.0/24 | 256 | RIPE NCC | BG | 28th Dec 2000 |
| 217.75.139.0/24 | 256 | RIPE NCC | BG | 28th Dec 2000 |
| 217.75.142.0/24 | 256 | RIPE NCC | BG | 28th Dec 2000 |
| 217.75.143.0/24 | 256 | RIPE NCC | BG | 28th Dec 2000 |
| 217.75.32.0/20 | 4.1k | RIPE NCC | NL | 22nd Dec 2000 |
| 217.78.240.0/20 | 4.1k | RIPE NCC |  CW | 4th Nov 2003 |
| 217.8.240.0/20 | 4.1k | RIPE NCC | DE | 21st Oct 2002 |
| 217.8.64.0/20 | 4.1k | RIPE NCC |  SA | 7th Aug 2000 |
| 217.9.176.0/20 | 4.1k | RIPE NCC | PL | 6th Feb 2001 |
| 218.100.0.0/24 | 256 | APNIC |  AU | 13th Feb 2002 |
| 218.100.10.0/24 | 256 | APNIC |  VN | 17th Sept 2003 |
| 218.100.11.0/24 | 256 | APNIC |  ID | 20th Nov 2003 |
| 218.100.12.0/24 | 256 | APNIC | AU | 16th May 2003 |
| 218.100.128.0/17 | 32.8k | APNIC |  CN | 12th Apr 2011 |
| 218.100.13.0/24 | 256 | APNIC | AU | 19th May 2003 |