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 unannounced space registered through RIPE NCC, largest first.
Unannounced blocks registered through RIPE NCC
25,269 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 80.244.2.0/24 | 256 | RIPE NCC |  ES | 24th Jan 2024 |
| 80.244.8.0/24 | 256 | RIPE NCC |  GB | 12th Feb 2024 |
| 80.246.48.0/20 | 4.1k | RIPE NCC |  DE | 28th Apr 2009 |
| 80.247.192.0/20 | 4.1k | RIPE NCC |  NL | 13th Nov 2001 |
| 80.247.208.0/21 | 2k | RIPE NCC | NL | 14th Jan 2002 |
| 80.248.137.0/24 | 256 | RIPE NCC | ES | 19th Nov 2001 |
| 80.249.133.0/24 | 256 | RIPE NCC |  CZ | 22nd Oct 2020 |
| 80.249.192.0/21 | 2k | RIPE NCC |  RU | 19th Oct 2010 |
| 80.250.126.0/24 | 256 | RIPE NCC |  EE | 11th Nov 2005 |
| 80.251.80.0/20 | 4.1k | RIPE NCC | DE | 15th Nov 2005 |
| 80.252.116.0/22 | 1k | RIPE NCC | EE | 28th Nov 2005 |
| 80.254.232.0/22 | 1k | RIPE NCC | CZ | 15th Aug 2018 |
| 80.254.236.0/22 | 1k | RIPE NCC | CZ | 15th Aug 2018 |
| 80.255.192.0/20 | 4.1k | RIPE NCC | GB | 28th Dec 2001 |
| 80.255.208.0/20 | 4.1k | RIPE NCC | GB | 6th Jun 2003 |
| 80.65.220.0/22 | 1k | RIPE NCC |  RO | 13th Aug 2018 |
| 80.68.144.0/24 | 256 | RIPE NCC | DE | 25th Jan 2022 |
| 80.68.149.0/24 | 256 | RIPE NCC |  AT | 25th Jan 2022 |
| 80.68.153.0/24 | 256 | RIPE NCC |  SI | 25th Jan 2022 |
| 80.68.157.0/24 | 256 | RIPE NCC |  LU | 25th Jan 2022 |
| 80.68.16.0/20 | 4.1k | RIPE NCC | GB | 21st Feb 2004 |
| 80.70.160.0/23 | 512 | RIPE NCC | DE | 1st Jun 2001 |
| 80.70.162.0/23 | 512 | RIPE NCC | DE | 1st Jun 2001 |
| 80.70.192.0/20 | 4.1k | RIPE NCC |  US | 29th Sept 2009 |
| 80.70.80.0/20 | 4.1k | RIPE NCC |  UA | 27th May 2004 |
| 80.71.145.0/24 | 256 | RIPE NCC |  TR | 23rd Sept 2021 |
| 80.71.148.0/24 | 256 | RIPE NCC | DE | 23rd Sept 2021 |
| 80.71.157.0/24 | 256 | RIPE NCC |  MD | 23rd Sept 2021 |
| 80.72.215.0/24 | 256 | RIPE NCC | RU | 31st Jan 2005 |
| 80.73.135.0/24 | 256 | RIPE NCC | US | 18th Jun 2001 |
| 80.73.136.0/21 | 2k | RIPE NCC | NL | 18th Jun 2001 |
| 80.73.218.0/24 | 256 | RIPE NCC |  FK | 7th Feb 2005 |
| 80.73.248.0/24 | 256 | RIPE NCC | GB | 7th Feb 2005 |
| 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 |