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,108 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 188.212.250.0/24 | 256 | RIPE NCC |  RO | 8th May 2009 |
| 188.212.39.0/24 | 256 | RIPE NCC |  PL | 8th May 2009 |
| 188.212.8.0/21 | 2k | RIPE NCC |  MD | 8th May 2009 |
| 188.213.220.0/22 | 1k | RIPE NCC | MD | 8th May 2009 |
| 188.213.23.0/24 | 256 | RIPE NCC |  US | 8th May 2009 |
| 188.213.236.0/22 | 1k | RIPE NCC | MD | 8th May 2009 |
| 188.213.243.0/24 | 256 | RIPE NCC | US | 8th May 2009 |
| 188.213.244.0/22 | 1k | RIPE NCC | MD | 8th May 2009 |
| 188.213.32.0/24 | 256 | RIPE NCC | RO | 8th May 2009 |
| 188.213.36.0/22 | 1k | RIPE NCC | MD | 8th May 2009 |
| 188.213.49.0/24 | 256 | RIPE NCC |  LU | 8th May 2009 |
| 188.213.52.0/22 | 1k | RIPE NCC | MD | 8th May 2009 |
| 188.213.84.0/23 | 512 | RIPE NCC |  GB | 8th May 2009 |
| 188.213.96.0/19 | 8.2k | RIPE NCC |  IR | 8th May 2009 |
| 188.214.109.0/24 | 256 | RIPE NCC |  GE | 8th May 2009 |
| 188.214.120.0/23 | 512 | RIPE NCC | IR | 8th May 2009 |
| 188.214.151.0/24 | 256 | RIPE NCC | RO | 8th May 2009 |
| 188.214.154.0/24 | 256 | RIPE NCC | RO | 8th May 2009 |
| 188.214.26.0/24 | 256 | RIPE NCC | RO | 8th May 2009 |
| 188.214.29.0/24 | 256 | RIPE NCC |  IT | 8th May 2009 |
| 188.214.40.0/21 | 2k | RIPE NCC |  NL | 8th May 2009 |
| 188.214.48.0/21 | 2k | RIPE NCC |  ES | 8th May 2009 |
| 188.214.60.0/22 | 1k | RIPE NCC | MD | 8th May 2009 |
| 188.214.92.0/24 | 256 | RIPE NCC | RO | 8th May 2009 |
| 188.215.232.0/24 | 256 | RIPE NCC | RO | 8th May 2009 |
| 188.215.234.0/24 | 256 | RIPE NCC | RO | 8th May 2009 |
| 188.215.252.0/22 | 1k | RIPE NCC | MD | 8th May 2009 |
| 188.215.3.0/24 | 256 | RIPE NCC | RO | 8th May 2009 |
| 188.215.30.0/24 | 256 | RIPE NCC |  RS | 8th May 2009 |
| 188.215.36.0/24 | 256 | RIPE NCC | PL | 8th May 2009 |
| 188.215.38.0/24 | 256 | RIPE NCC | GB | 8th May 2009 |
| 188.215.4.0/24 | 256 | RIPE NCC | RO | 8th May 2009 |
| 188.215.40.0/22 | 1k | RIPE NCC |  TR | 8th May 2009 |
| 188.227.104.0/23 | 512 | RIPE NCC |  RU | 22nd Jul 2009 |
| 188.240.221.0/24 | 256 | RIPE NCC | RO | 23rd Jun 2009 |
| 188.240.43.0/24 | 256 | RIPE NCC | ES | 23rd Jun 2009 |
| 188.241.124.0/23 | 512 | RIPE NCC |  AT | 23rd Jun 2009 |
| 188.241.155.0/24 | 256 | RIPE NCC | RO | 23rd Jun 2009 |
| 188.241.16.0/24 | 256 | RIPE NCC | RO | 23rd Jun 2009 |
| 188.241.18.0/24 | 256 | RIPE NCC | RO | 23rd Jun 2009 |
| 188.241.180.0/23 | 512 | RIPE NCC | RO | 23rd Jun 2009 |
| 188.241.193.0/24 | 256 | RIPE NCC | US | 23rd Jun 2009 |
| 188.241.195.0/24 | 256 | RIPE NCC | RO | 23rd Jun 2009 |
| 188.241.2.0/24 | 256 | RIPE NCC | RO | 23rd Jun 2009 |
| 188.241.214.0/24 | 256 | RIPE NCC | NL | 23rd Jun 2009 |
| 188.241.224.0/20 | 4.1k | RIPE NCC | ES | 23rd Jun 2009 |
| 188.241.252.0/22 | 1k | RIPE NCC | RO | 23rd Jun 2009 |
| 188.241.38.0/24 | 256 | RIPE NCC | RO | 23rd Jun 2009 |
| 188.241.52.0/24 | 256 | RIPE NCC | NL | 23rd Jun 2009 |
| 188.241.6.0/24 | 256 | RIPE NCC | LU | 23rd Jun 2009 |