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,619 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 80.224.252.0/24 | 256 | RIPE NCC |  DE | 28th Sept 2001 |
| 80.224.255.0/24 | 256 | RIPE NCC |  AT | 28th Sept 2001 |
| 80.237.144.0/21 | 2k | RIPE NCC | DE | 12th Nov 2001 |
| 80.237.196.0/22 | 1k | RIPE NCC | DE | 12th Nov 2001 |
| 80.237.208.0/22 | 1k | RIPE NCC | DE | 12th Nov 2001 |
| 80.238.32.0/19 | 8.2k | RIPE NCC |  GB | 13th Apr 2006 |
| 80.238.64.0/19 | 8.2k | RIPE NCC |  PL | 8th May 2006 |
| 80.241.156.0/23 | 512 | RIPE NCC |  BH | 1st Sept 2005 |
| 80.241.158.0/24 | 256 | RIPE NCC | BH | 1st Sept 2005 |
| 80.241.159.0/24 | 256 | RIPE NCC | BH | 1st Sept 2005 |
| 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.114.0/24 | 256 | RIPE NCC |  IR | 15th Aug 2018 |
| 80.249.128.0/24 | 256 | RIPE NCC | GB | 19th Oct 2020 |
| 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.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.44.0.0/16 | 65.5k | ARIN |  US | 12th Oct 2026 |
| 80.45.0.0/16 | 65.5k | RIPE NCC | GB | 23rd Nov 2001 |
| 80.46.0.0/17 | 32.8k | RIPE NCC | GB | 23rd Nov 2001 |
| 80.46.160.0/19 | 8.2k | ARIN | US | 21st Sept 2026 |
| 80.47.128.0/19 | 8.2k | ARIN |  CA | 17th Sept 2026 |
| 80.47.160.0/19 | 8.2k | RIPE NCC | GB | 23rd Nov 2001 |
| 80.47.240.0/20 | 4.1k | ARIN | US | 9th Sept 2026 |
| 80.47.96.0/19 | 8.2k | RIPE NCC | GB | 23rd Nov 2001 |
| 80.65.220.0/22 | 1k | RIPE NCC |  RO | 13th Aug 2018 |
| 80.65.32.0/20 | 4.1k | RIPE NCC | DE | 11th May 2001 |
| 80.68.144.0/24 | 256 | RIPE NCC | DE | 25th Jan 2022 |
| 80.68.145.0/24 | 256 | RIPE NCC |  SC | 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.158.0/24 | 256 | RIPE NCC | SC | 25th Jan 2022 |
| 80.68.16.0/20 | 4.1k | RIPE NCC | GB | 21st Feb 2004 |
| 80.69.160.0/21 | 2k | RIPE NCC |  FI | 22nd Sept 2009 |
| 80.69.168.0/22 | 1k | RIPE NCC | FI | 22nd Sept 2009 |
| 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.148.0/24 | 256 | RIPE NCC | DE | 23rd Sept 2021 |