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 |
|---|---|---|---|---|
| 187.94.57.0/24 | 256 | LACNIC |  BR | 14th Sept 2009 |
| 187.94.58.0/23 | 512 | LACNIC | BR | 14th Sept 2009 |
| 187.94.60.0/22 | 1k | LACNIC | BR | 14th Sept 2009 |
| 187.95.192.0/20 | 4.1k | LACNIC | BR | 4th Nov 2009 |
| 188.0.242.0/23 | 512 | RIPE NCC |  IR | 27th May 2011 |
| 188.116.12.0/22 | 1k | RIPE NCC |  DE | 29th May 2009 |
| 188.116.18.0/23 | 512 | RIPE NCC |  AT | 29th May 2009 |
| 188.116.48.0/23 | 512 | RIPE NCC | AT | 29th May 2009 |
| 188.116.56.0/23 | 512 | RIPE NCC |  IT | 29th May 2009 |
| 188.119.153.0/24 | 256 | RIPE NCC |  MC | 6th Jul 2009 |
| 188.119.88.0/22 | 1k | RIPE NCC |  BZ | 23rd Nov 2018 |
| 188.120.124.0/24 | 256 | RIPE NCC |  RS | 27th Apr 2009 |
| 188.122.160.0/19 | 8.2k | RIPE NCC |  RU | 4th Jun 2009 |
| 188.123.120.0/21 | 2k | RIPE NCC |  SK | 11th Jun 2009 |
| 188.125.161.0/24 | 256 | RIPE NCC |  TR | 14th Jul 2009 |
| 188.125.164.0/24 | 256 | RIPE NCC | TR | 14th Jul 2009 |
| 188.125.165.0/24 | 256 | RIPE NCC | TR | 14th Jul 2009 |
| 188.125.167.0/24 | 256 | RIPE NCC | TR | 14th Jul 2009 |
| 188.125.174.0/24 | 256 | RIPE NCC | TR | 14th Jul 2009 |
| 188.125.175.0/24 | 256 | RIPE NCC | TR | 14th Jul 2009 |
| 188.132.147.0/24 | 256 | RIPE NCC | TR | 21st Apr 2009 |
| 188.132.159.0/24 | 256 | RIPE NCC | TR | 21st Apr 2009 |
| 188.132.168.0/24 | 256 | RIPE NCC | TR | 21st Apr 2009 |
| 188.138.12.0/22 | 1k | RIPE NCC | DE | 8th May 2009 |
| 188.138.20.0/22 | 1k | RIPE NCC | DE | 8th May 2009 |
| 188.138.48.0/21 | 2k | RIPE NCC | DE | 8th May 2009 |
| 188.139.0.0/17 | 32.8k | RIPE NCC |  SA | 20th May 2009 |
| 188.144.0.0/15 | 131k | RIPE NCC | DE | 13th Mar 2009 |
| 188.190.112.0/24 | 256 | RIPE NCC |  NL | 17th Oct 2018 |
| 188.191.144.0/23 | 512 | RIPE NCC |  UA | 21st Feb 2011 |
| 188.191.60.0/22 | 1k | RIPE NCC |  GB | 18th Feb 2011 |
| 188.208.104.0/22 | 1k | RIPE NCC |  MD | 8th May 2009 |
| 188.208.112.0/22 | 1k | RIPE NCC | MD | 8th May 2009 |
| 188.208.134.0/24 | 256 | RIPE NCC |  RO | 8th May 2009 |
| 188.208.136.0/22 | 1k | RIPE NCC | RO | 8th May 2009 |
| 188.208.192.0/22 | 1k | RIPE NCC | MD | 8th May 2009 |
| 188.208.204.0/22 | 1k | RIPE NCC | MD | 8th May 2009 |
| 188.208.208.0/21 | 2k | RIPE NCC | IR | 8th May 2009 |
| 188.208.31.0/24 | 256 | RIPE NCC | RO | 8th May 2009 |
| 188.208.96.0/22 | 1k | RIPE NCC | MD | 8th May 2009 |
| 188.209.144.0/21 | 2k | ARIN |  US | 23rd Jul 2018 |
| 188.210.240.0/21 | 2k | RIPE NCC | MD | 8th May 2009 |
| 188.210.248.0/22 | 1k | RIPE NCC | MD | 8th May 2009 |
| 188.210.89.0/24 | 256 | RIPE NCC | RO | 8th May 2009 |
| 188.210.93.0/24 | 256 | RIPE NCC | US | 8th May 2009 |
| 188.211.128.0/19 | 8.2k | RIPE NCC | IR | 8th May 2009 |
| 188.211.224.0/22 | 1k | RIPE NCC | RO | 8th May 2009 |
| 188.211.228.0/22 | 1k | RIPE NCC |  ES | 8th May 2009 |
| 188.212.126.0/24 | 256 | RIPE NCC | RO | 8th May 2009 |
| 188.212.128.0/23 | 512 | RIPE NCC | RO | 8th May 2009 |