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,872 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 213.232.84.0/22 | 1k | RIPE NCC |  DE | 7th Dec 2018 |
| 213.234.32.0/19 | 8.2k | RIPE NCC |  GB | 5th Dec 2001 |
| 213.236.26.0/24 | 256 | RIPE NCC |  ES | 16th Sept 1999 |
| 213.236.28.0/22 | 1k | RIPE NCC | ES | 16th Sept 1999 |
| 213.237.192.0/18 | 16.4k | RIPE NCC | GB | 18th Mar 2003 |
| 213.238.64.0/18 | 16.4k | RIPE NCC |  PL | 7th Mar 2001 |
| 213.239.154.0/24 | 256 | RIPE NCC |  NL | 19th Sept 2000 |
| 213.240.33.0/24 | 256 | RIPE NCC |  RS | 19th Jul 1999 |
| 213.240.34.0/23 | 512 | RIPE NCC | RS | 19th Jul 1999 |
| 213.241.196.0/23 | 512 | RIPE NCC |  RU | 28th Feb 2008 |
| 213.241.200.0/21 | 2k | RIPE NCC | RU | 28th Feb 2008 |
| 213.241.208.0/20 | 4.1k | RIPE NCC | RU | 28th Feb 2008 |
| 213.241.224.0/19 | 8.2k | RIPE NCC | RU | 28th Feb 2008 |
| 213.244.194.0/23 | 512 | RIPE NCC |  CH | 11th Jun 2003 |
| 213.244.228.0/22 | 1k | RIPE NCC | RS | 11th Jun 2003 |
| 213.244.44.0/22 | 1k | RIPE NCC | DE | 11th Jul 2002 |
| 213.251.224.0/20 | 4.1k | RIPE NCC | RU | 9th May 2003 |
| 213.254.166.0/23 | 512 | RIPE NCC | GB | 17th Oct 2000 |
| 213.255.198.0/24 | 256 | RIPE NCC |  AT | 24th Mar 2003 |
| 213.255.208.0/24 | 256 | RIPE NCC | AT | 24th Mar 2003 |
| 213.255.212.0/22 | 1k | RIPE NCC |  IL | 24th Mar 2003 |
| 213.255.220.0/22 | 1k | RIPE NCC | IL | 24th Mar 2003 |
| 213.255.232.0/21 | 2k | RIPE NCC | IL | 24th Mar 2003 |
| 213.255.252.0/22 | 1k | RIPE NCC | IL | 24th Mar 2003 |
| 213.90.128.0/17 | 32.8k | RIPE NCC |  FR | 8th Aug 2001 |
| 216.116.131.0/24 | 256 | RIPE NCC | GB | 1st Jun 2018 |
| 216.119.224.0/19 | 8.2k | RIPE NCC |  HK | 16th Nov 2000 |
| 216.150.24.0/22 | 1k | RIPE NCC |  US | 14th Jul 1999 |
| 216.162.192.0/24 | 256 | RIPE NCC |  SC | 11th Aug 1999 |
| 216.247.120.0/21 | 2k | RIPE NCC | US | 21st Oct 1999 |
| 216.249.16.0/22 | 1k | RIPE NCC | GB | 24th Jan 2001 |
| 216.30.172.0/23 | 512 | RIPE NCC | FR | 15th Nov 2002 |
| 216.52.245.0/24 | 256 | RIPE NCC | IL | 24th Aug 1998 |
| 216.87.55.0/24 | 256 | RIPE NCC | GB | 9th Jul 1999 |
| 217.10.234.0/23 | 512 | RIPE NCC |  IE | 18th Aug 2000 |
| 217.113.56.0/22 | 1k | RIPE NCC |  HU | 5th Dec 2003 |
| 217.114.32.0/24 | 256 | RIPE NCC | SC | 4th Oct 2021 |
| 217.115.138.0/23 | 512 | RIPE NCC | DE | 1st Feb 2001 |
| 217.115.144.0/24 | 256 | RIPE NCC | DE | 29th May 2001 |
| 217.115.224.0/20 | 4.1k | RIPE NCC | NL | 5th Feb 2001 |
| 217.118.144.0/20 | 4.1k | RIPE NCC |  IT | 11th Feb 2004 |
| 217.118.16.0/23 | 512 | RIPE NCC | DE | 22nd Nov 2004 |
| 217.118.18.0/24 | 256 | RIPE NCC | DE | 22nd Nov 2004 |
| 217.118.20.0/23 | 512 | RIPE NCC | DE | 22nd Nov 2004 |
| 217.118.22.0/24 | 256 | RIPE NCC | DE | 22nd Nov 2004 |
| 217.118.25.0/24 | 256 | RIPE NCC | DE | 22nd Nov 2004 |
| 217.118.28.0/22 | 1k | RIPE NCC | DE | 22nd Nov 2004 |
| 217.119.130.0/24 | 256 | RIPE NCC |  CA | 5th Oct 2021 |
| 217.119.136.0/24 | 256 | RIPE NCC |  BE | 5th Oct 2021 |
| 217.119.48.0/24 | 256 | RIPE NCC | DE | 26th Feb 2004 |