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,818 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 80.73.249.0/24 | 256 | RIPE NCC |  IT | 7th Feb 2005 |
| 80.73.251.0/24 | 256 | RIPE NCC |  GB | 7th Feb 2005 |
| 80.73.252.0/24 | 256 | RIPE NCC |  CH | 7th Feb 2005 |
| 80.73.253.0/24 | 256 | RIPE NCC | GB | 7th Feb 2005 |
| 80.74.0.0/20 | 4.1k | RIPE NCC | GB | 18th Jun 2001 |
| 80.74.224.0/20 | 4.1k | RIPE NCC | GB | 19th Jun 2001 |
| 80.74.32.0/20 | 4.1k | RIPE NCC |  CZ | 18th Jun 2001 |
| 80.74.80.0/20 | 4.1k | RIPE NCC |  SA | 11th Feb 2005 |
| 80.75.216.0/24 | 256 | RIPE NCC |  NL | 9th Jan 2024 |
| 80.75.222.0/24 | 256 | RIPE NCC | NL | 9th Jan 2024 |
| 80.75.223.0/24 | 256 | RIPE NCC |  RU | 9th Jan 2024 |
| 80.77.116.0/24 | 256 | RIPE NCC |  HU | 9th Mar 2005 |
| 80.77.118.0/23 | 512 | RIPE NCC | HU | 9th Mar 2005 |
| 80.77.120.0/23 | 512 | RIPE NCC | HU | 9th Mar 2005 |
| 80.78.80.0/20 | 4.1k | RIPE NCC |  DE | 16th Mar 2005 |
| 80.79.12.0/24 | 256 | RIPE NCC |  DK | 11th Jan 2024 |
| 80.79.14.0/24 | 256 | RIPE NCC | SA | 11th Jan 2024 |
| 80.81.192.0/20 | 4.1k | RIPE NCC | DE | 24th Jul 2001 |
| 80.82.192.0/21 | 2k | RIPE NCC | CZ | 7th Jun 2012 |
| 80.84.0.0/20 | 4.1k | RIPE NCC | DE | 6th Aug 2001 |
| 80.85.242.0/23 | 512 | RIPE NCC | RU | 12th Feb 2010 |
| 80.85.48.0/21 | 2k | RIPE NCC | HU | 26th Apr 2005 |
| 80.85.88.0/21 | 2k | RIPE NCC | NL | 19th May 2003 |
| 80.87.0.0/20 | 4.1k | RIPE NCC | GB | 21st Aug 2001 |
| 80.88.7.0/24 | 256 | AFRINIC |  NG | 21st Feb 2017 |
| 80.90.66.0/23 | 512 | RIPE NCC | RU | 6th Sept 2001 |
| 80.90.68.0/22 | 1k | RIPE NCC | RU | 6th Sept 2001 |
| 80.90.72.0/21 | 2k | RIPE NCC | RU | 6th Sept 2001 |
| 80.91.144.0/20 | 4.1k | RIPE NCC |  BE | 14th Jun 2005 |
| 80.91.213.0/24 | 256 | RIPE NCC |  CY | 25th Jan 2022 |
| 80.91.217.0/24 | 256 | RIPE NCC | DE | 25th Jan 2022 |
| 80.92.144.0/20 | 4.1k | RIPE NCC | GB | 27th Jun 2005 |
| 80.92.160.0/20 | 4.1k | RIPE NCC | RU | 24th Sept 2001 |
| 80.92.204.0/23 | 512 | RIPE NCC |  MD | 24th Sept 2001 |
| 80.92.206.0/24 | 256 | RIPE NCC | MD | 24th Sept 2001 |
| 81.127.192.0/18 | 16.4k | RIPE NCC | IT | 8th Jul 2002 |
| 81.16.128.0/22 | 1k | RIPE NCC |  RO | 16th Aug 2018 |
| 81.16.136.0/22 | 1k | RIPE NCC |  AT | 16th Aug 2018 |
| 81.16.180.0/22 | 1k | RIPE NCC | DE | 28th Feb 2005 |
| 81.160.0.0/17 | 32.8k | RIPE NCC | DE | 12th Nov 2003 |
| 81.162.128.0/18 | 16.4k | RIPE NCC |  TR | 6th Dec 2011 |
| 81.163.64.0/21 | 2k | RIPE NCC | RU | 25th Aug 2011 |
| 81.163.88.0/21 | 2k | RIPE NCC | RU | 30th Aug 2011 |
| 81.17.124.0/22 | 1k | RIPE NCC | DE | 4th Aug 2003 |
| 81.17.160.0/20 | 4.1k | RIPE NCC |  KZ | 18th Nov 2008 |
| 81.172.0.0/19 | 8.2k | RIPE NCC |  US | 14th Jan 2003 |
| 81.172.116.0/24 | 256 | RIPE NCC | US | 14th Jan 2003 |
| 81.172.45.0/24 | 256 | RIPE NCC | DE | 14th Jan 2003 |
| 81.172.48.0/21 | 2k | RIPE NCC | US | 14th Jan 2003 |
| 81.172.56.0/22 | 1k | RIPE NCC | US | 14th Jan 2003 |