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
24,902 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 80.117.0.0/16 | 65.5k | RIPE NCC |  IT | 6th Aug 2001 |
| 80.173.112.0/22 | 1k | RIPE NCC |  ES | 11th Jun 2003 |
| 80.173.116.0/23 | 512 | RIPE NCC | ES | 11th Jun 2003 |
| 80.173.118.0/23 | 512 | RIPE NCC |  AM | 11th Jun 2003 |
| 80.173.120.0/21 | 2k | RIPE NCC | ES | 11th Jun 2003 |
| 80.173.128.0/22 | 1k | RIPE NCC |  HR | 11th Jun 2003 |
| 80.173.132.0/22 | 1k | RIPE NCC | HR | 11th Jun 2003 |
| 80.173.174.0/24 | 256 | RIPE NCC | ES | 11th Jun 2003 |
| 80.173.175.0/24 | 256 | RIPE NCC | AM | 11th Jun 2003 |
| 80.173.224.0/22 | 1k | RIPE NCC | IT | 11th Jun 2003 |
| 80.173.64.0/19 | 8.2k | RIPE NCC | ES | 11th Jun 2003 |
| 80.173.96.0/20 | 4.1k | RIPE NCC | ES | 11th Jun 2003 |
| 80.210.80.0/20 | 4.1k | RIPE NCC |  NO | 12th Dec 2001 |
| 80.224.0.0/17 | 32.8k | RIPE NCC | ES | 28th Sept 2001 |
| 80.224.128.0/19 | 8.2k | RIPE NCC | ES | 28th Sept 2001 |
| 80.224.160.0/20 | 4.1k | RIPE NCC | ES | 28th Sept 2001 |
| 80.224.176.0/22 | 1k | RIPE NCC | ES | 28th Sept 2001 |
| 80.224.180.0/23 | 512 | RIPE NCC |  AE | 28th Sept 2001 |
| 80.224.182.0/23 | 512 | RIPE NCC | ES | 28th Sept 2001 |
| 80.224.184.0/22 | 1k | RIPE NCC | ES | 28th Sept 2001 |
| 80.224.188.0/24 | 256 | RIPE NCC |  EE | 28th Sept 2001 |
| 80.224.190.0/24 | 256 | RIPE NCC | IT | 28th Sept 2001 |
| 80.224.191.0/24 | 256 | RIPE NCC | ES | 28th Sept 2001 |
| 80.224.208.0/21 | 2k | RIPE NCC | ES | 28th Sept 2001 |
| 80.224.216.0/23 | 512 | RIPE NCC |  CH | 28th Sept 2001 |
| 80.224.248.0/22 | 1k | RIPE NCC | IT | 28th Sept 2001 |
| 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 |