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
85,356 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 213.142.138.0/23 | 512 | RIPE NCC |  RU | 12th Oct 2009 |
| 213.142.144.0/23 | 512 | RIPE NCC |  TR | 12th Oct 2009 |
| 213.142.157.0/24 | 256 | RIPE NCC | TR | 12th Oct 2009 |
| 213.147.224.0/19 | 8.2k | RIPE NCC |  GB | 20th Jan 2003 |
| 213.154.128.0/19 | 8.2k | RIPE NCC |  RO | 28th Jan 2000 |
| 213.154.96.0/19 | 8.2k | RIPE NCC | RO | 3rd May 2002 |
| 213.159.72.0/21 | 2k | RIPE NCC |  MD | 1st Mar 2000 |
| 213.162.160.0/19 | 8.2k | RIPE NCC |  NL | 10th May 2001 |
| 213.163.250.0/23 | 512 | RIPE NCC |  DE | 10th Feb 2003 |
| 213.164.160.0/19 | 8.2k | RIPE NCC |  ES | 17th May 2001 |
| 213.170.143.0/24 | 256 | RIPE NCC |  US | 16th Feb 2000 |
| 213.170.200.0/22 | 1k | RIPE NCC | GB | 6th Nov 2018 |
| 213.170.204.0/22 | 1k | RIPE NCC |  RS | 6th Nov 2018 |
| 213.173.16.0/20 | 4.1k | RIPE NCC | DE | 4th Jan 2000 |
| 213.175.0.0/19 | 8.2k | RIPE NCC |  IT | 18th Jan 2000 |
| 213.177.160.0/24 | 256 | RIPE NCC | TR | 15th Oct 2025 |
| 213.177.161.0/24 | 256 | RIPE NCC |  AL | 15th Oct 2025 |
| 213.177.163.0/24 | 256 | RIPE NCC | DE | 15th Oct 2025 |
| 213.177.166.0/24 | 256 | RIPE NCC |  FR | 15th Oct 2025 |
| 213.177.168.0/24 | 256 | RIPE NCC | FR | 15th Oct 2025 |
| 213.177.169.0/24 | 256 | RIPE NCC |  SE | 15th Oct 2025 |
| 213.177.170.0/24 | 256 | RIPE NCC |  SG | 15th Oct 2025 |
| 213.177.171.0/24 | 256 | RIPE NCC | TR | 15th Oct 2025 |
| 213.177.175.0/24 | 256 | RIPE NCC |  QA | 16th Oct 2025 |
| 213.177.183.0/24 | 256 | RIPE NCC | RU | 24th Oct 2025 |
| 213.177.187.0/24 | 256 | RIPE NCC |  LT | 9th Jan 2026 |
| 213.177.191.0/24 | 256 | RIPE NCC | RU | 19th Jan 2026 |
| 213.177.32.0/19 | 8.2k | RIPE NCC | GB | 12th Jan 2001 |
| 213.178.128.0/22 | 1k | RIPE NCC | DE | 18th Mar 2019 |
| 213.178.144.0/22 | 1k | RIPE NCC | GB | 18th Mar 2019 |
| 213.178.153.0/24 | 256 | RIPE NCC | RU | 18th Mar 2019 |
| 213.185.86.0/23 | 512 | RIPE NCC | NL | 24th Mar 2000 |
| 213.185.88.0/21 | 2k | RIPE NCC | NL | 24th Mar 2000 |
| 213.187.144.0/22 | 1k | RIPE NCC | NL | 18th Feb 2000 |
| 213.187.148.0/22 | 1k | RIPE NCC | US | 18th Feb 2000 |
| 213.187.32.0/19 | 8.2k | RIPE NCC | GB | 5th Feb 2001 |
| 213.189.193.0/24 | 256 | RIPE NCC | RU | 9th May 2000 |
| 213.189.96.0/19 | 8.2k | RIPE NCC | SE | 10th Dec 2002 |
| 213.193.193.0/24 | 256 | RIPE NCC | NL | 28th Jun 2002 |
| 213.193.194.0/24 | 256 | RIPE NCC |  TJ | 28th Jun 2002 |
| 213.193.195.0/24 | 256 | RIPE NCC | NL | 28th Jun 2002 |
| 213.193.208.0/24 | 256 | RIPE NCC | LT | 28th Jun 2002 |
| 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 |