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,318 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 213.193.235.0/24 | 256 | RIPE NCC |  IS | 28th Jun 2002 |
| 213.193.237.0/24 | 256 | RIPE NCC |  NL | 28th Jun 2002 |
| 213.193.238.0/23 | 512 | RIPE NCC |  MC | 28th Jun 2002 |
| 213.195.48.0/22 | 1k | RIPE NCC |  IR | 21st Apr 2009 |
| 213.197.96.0/19 | 8.2k | RIPE NCC |  HU | 6th Nov 2000 |
| 213.202.16.0/20 | 4.1k | RIPE NCC |  OM | 7th Sept 2011 |
| 213.202.8.0/21 | 2k | RIPE NCC | OM | 7th Sept 2011 |
| 213.204.96.0/24 | 256 | RIPE NCC |  LB | 14th May 2008 |
| 213.204.97.0/24 | 256 | RIPE NCC | LB | 14th May 2008 |
| 213.206.39.0/24 | 256 | RIPE NCC |  UZ | 26th Mar 2003 |
| 213.206.40.0/24 | 256 | RIPE NCC | UZ | 26th Mar 2003 |
| 213.206.42.0/24 | 256 | RIPE NCC | UZ | 26th Mar 2003 |
| 213.206.44.0/23 | 512 | RIPE NCC | UZ | 26th Mar 2003 |
| 213.206.47.0/24 | 256 | RIPE NCC | UZ | 26th Mar 2003 |
| 213.206.48.0/24 | 256 | RIPE NCC | UZ | 26th Mar 2003 |
| 213.206.50.0/23 | 512 | RIPE NCC | UZ | 26th Mar 2003 |
| 213.206.52.0/22 | 1k | RIPE NCC | UZ | 26th Mar 2003 |
| 213.206.58.0/24 | 256 | RIPE NCC | UZ | 26th Mar 2003 |
| 213.206.60.0/22 | 1k | RIPE NCC | UZ | 26th Mar 2003 |
| 213.211.0.0/19 | 8.2k | RIPE NCC |  TR | 26th Mar 2008 |
| 213.217.6.0/24 | 256 | RIPE NCC |  IT | 8th Nov 2018 |
| 213.218.168.0/21 | 2k | RIPE NCC |  DE | 12th May 2003 |
| 213.218.176.0/20 | 4.1k | RIPE NCC | DE | 12th May 2003 |
| 213.219.40.0/21 | 2k | RIPE NCC | NL | 9th Feb 2000 |
| 213.221.160.0/19 | 8.2k | RIPE NCC |  GB | 4th Oct 2000 |
| 213.222.0.0/19 | 8.2k | RIPE NCC | NL | 4th Nov 1999 |
| 213.225.128.0/19 | 8.2k | RIPE NCC | GB | 24th May 2000 |
| 213.226.84.0/22 | 1k | RIPE NCC |  ES | 5th Dec 2018 |
| 213.232.104.0/22 | 1k | RIPE NCC |  AT | 7th Dec 2018 |
| 213.232.193.0/24 | 256 | RIPE NCC | DE | 26th Jan 2026 |
| 213.232.216.0/24 | 256 | RIPE NCC | NL | 27th Oct 2020 |
| 213.232.227.0/24 | 256 | RIPE NCC |  RU | 15th May 2003 |
| 213.232.233.0/24 | 256 | RIPE NCC | RU | 20th Sept 2021 |
| 213.232.252.0/24 | 256 | RIPE NCC |  CY | 27th Jul 2021 |
| 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 |