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,960 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 31.214.149.0/24 | 256 | RIPE NCC |  DE | 6th May 2011 |
| 31.214.155.0/24 | 256 | RIPE NCC |  ES | 6th May 2011 |
| 31.214.200.0/23 | 512 | RIPE NCC |  IR | 6th May 2011 |
| 31.220.12.0/23 | 512 | RIPE NCC | DE | 10th May 2011 |
| 31.220.128.0/21 | 2k | RIPE NCC |  RO | 11th May 2011 |
| 31.220.147.0/24 | 256 | RIPE NCC | DE | 11th May 2011 |
| 31.220.216.0/21 | 2k | ARIN |  US | 4th Dec 2024 |
| 31.220.244.0/24 | 256 | RIPE NCC |  GB | 12th May 2011 |
| 31.220.245.0/24 | 256 | ARIN | US | 4th Dec 2024 |
| 31.220.36.0/22 | 1k | RIPE NCC | DE | 10th May 2011 |
| 31.220.8.0/22 | 1k | RIPE NCC | DE | 10th May 2011 |
| 31.222.230.0/24 | 256 | RIPE NCC |  CA | 6th Oct 2021 |
| 31.222.231.0/24 | 256 | RIPE NCC | DE | 6th Oct 2021 |
| 31.222.238.0/24 | 256 | RIPE NCC |  MD | 7th Oct 2021 |
| 31.222.251.0/24 | 256 | RIPE NCC |  SC | 7th Oct 2021 |
| 31.222.40.0/21 | 2k | RIPE NCC |  AL | 13th May 2011 |
| 31.223.176.0/21 | 2k | RIPE NCC |  PS | 16th May 2011 |
| 31.24.160.0/21 | 2k | RIPE NCC |  NL | 24th Feb 2011 |
| 31.24.254.0/24 | 256 | RIPE NCC |  TR | 29th Jun 2022 |
| 31.24.84.0/24 | 256 | RIPE NCC | DE | 11th Jan 2022 |
| 31.25.192.0/22 | 1k | RIPE NCC | US | 8th Mar 2011 |
| 31.25.232.0/23 | 512 | RIPE NCC | IR | 9th Mar 2011 |
| 31.25.80.0/21 | 2k | RIPE NCC |  IE | 3rd Mar 2011 |
| 31.28.66.0/24 | 256 | RIPE NCC | GB | 23rd Feb 2011 |
| 31.28.74.0/24 | 256 | RIPE NCC | GB | 23rd Feb 2011 |
| 31.3.148.0/23 | 512 | RIPE NCC | DE | 3rd Aug 2011 |
| 31.3.220.0/24 | 256 | RIPE NCC | ES | 8th Apr 2011 |
| 31.31.32.0/21 | 2k | RIPE NCC | NL | 17th Mar 2011 |
| 31.31.92.0/22 | 1k | RIPE NCC | DE | 18th Mar 2011 |
| 31.40.224.0/22 | 1k | RIPE NCC | RO | 9th Nov 2018 |
| 31.41.104.0/21 | 2k | RIPE NCC |  UA | 28th Mar 2011 |
| 31.41.128.0/21 | 2k | RIPE NCC | UA | 29th Mar 2011 |
| 31.41.242.0/24 | 256 | RIPE NCC |  RU | 6th Apr 2011 |
| 31.41.244.0/24 | 256 | RIPE NCC | RU | 6th Apr 2011 |
| 31.41.8.0/22 | 1k | RIPE NCC | RU | 11th Mar 2011 |
| 31.43.162.0/24 | 256 | RIPE NCC |  SI | 1st Mar 2011 |
| 31.43.164.0/23 | 512 | RIPE NCC | UA | 1st Mar 2011 |
| 31.43.166.0/23 | 512 | RIPE NCC |  FR | 1st Mar 2011 |
| 31.43.176.0/23 | 512 | RIPE NCC |  PL | 1st Mar 2011 |
| 31.43.185.0/24 | 256 | RIPE NCC | UA | 1st Mar 2011 |
| 31.43.188.0/23 | 512 | RIPE NCC | UA | 1st Mar 2011 |
| 31.43.190.0/24 | 256 | RIPE NCC | UA | 1st Mar 2011 |
| 31.47.208.0/21 | 2k | RIPE NCC | RO | 22nd Mar 2011 |
| 31.7.168.0/21 | 2k | RIPE NCC |  MK | 14th Apr 2011 |
| 31.7.224.0/20 | 4.1k | RIPE NCC | RU | 14th Apr 2011 |
| 31.71.0.0/16 | 65.5k | RIPE NCC | GB | 25th Nov 2010 |
| 31.72.0.0/14 | 262k | RIPE NCC | GB | 25th Nov 2010 |
| 31.78.0.0/15 | 131k | RIPE NCC | GB | 25th Nov 2010 |
| 31.99.128.0/20 | 4.1k | ARIN | US | 18th May 2026 |
| 31.99.144.0/21 | 2k | APNIC | US | 25th Nov 2010 |