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
84,650 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 86.105.20.0/22 | 1k | RIPE NCC |  NO | 18th Apr 2005 |
| 86.105.215.0/24 | 256 | RIPE NCC |  PL | 18th Apr 2005 |
| 86.106.113.0/24 | 256 | RIPE NCC |  TR | 18th Apr 2005 |
| 86.106.124.0/22 | 1k | APNIC |  HK | 18th Apr 2005 |
| 86.106.134.0/24 | 256 | RIPE NCC |  RO | 18th Apr 2005 |
| 86.106.144.0/21 | 2k | RIPE NCC |  MD | 18th Apr 2005 |
| 86.106.178.0/24 | 256 | RIPE NCC | TR | 18th Apr 2005 |
| 86.106.21.0/24 | 256 | RIPE NCC | TR | 18th Apr 2005 |
| 86.106.23.0/24 | 256 | RIPE NCC |  US | 18th Apr 2005 |
| 86.106.72.0/23 | 512 | RIPE NCC | RO | 18th Apr 2005 |
| 86.106.82.0/24 | 256 | RIPE NCC | TR | 18th Apr 2005 |
| 86.106.96.0/24 | 256 | RIPE NCC |  DK | 18th Apr 2005 |
| 86.107.127.0/24 | 256 | RIPE NCC |  BE | 18th Apr 2005 |
| 86.107.184.0/24 | 256 | RIPE NCC |  IR | 18th Apr 2005 |
| 86.107.188.0/24 | 256 | RIPE NCC | TR | 18th Apr 2005 |
| 86.107.191.0/24 | 256 | RIPE NCC |  DE | 18th Apr 2005 |
| 86.107.244.0/23 | 512 | RIPE NCC |  AT | 18th Apr 2005 |
| 86.110.195.0/24 | 256 | RIPE NCC |  RU | 26th Jul 2005 |
| 86.110.213.0/24 | 256 | RIPE NCC | RU | 26th Jul 2005 |
| 86.110.214.0/24 | 256 | RIPE NCC | RU | 26th Jul 2005 |
| 86.111.54.0/23 | 512 | LACNIC |  BR | 28th Jun 2022 |
| 86.38.191.0/24 | 256 | RIPE NCC |  LT | 19th May 2005 |
| 86.38.235.0/24 | 256 | RIPE NCC | LT | 19th May 2005 |
| 86.48.128.0/18 | 16.4k | RIPE NCC |  NL | 14th Apr 2005 |
| 86.48.56.0/22 | 1k | RIPE NCC | DK | 14th Apr 2005 |
| 86.54.0.0/22 | 1k | RIPE NCC |  GB | 12th May 2005 |
| 86.54.16.0/22 | 1k | RIPE NCC | GB | 12th May 2005 |
| 86.54.168.0/22 | 1k | RIPE NCC | GB | 12th May 2005 |
| 86.54.186.0/23 | 512 | RIPE NCC | GB | 12th May 2005 |
| 86.54.188.0/22 | 1k | RIPE NCC | GB | 12th May 2005 |
| 86.54.204.0/22 | 1k | RIPE NCC | GB | 12th May 2005 |
| 86.54.21.0/24 | 256 | RIPE NCC | GB | 12th May 2005 |
| 86.54.214.0/23 | 512 | RIPE NCC | GB | 12th May 2005 |
| 86.54.216.0/21 | 2k | RIPE NCC | GB | 12th May 2005 |
| 86.54.22.0/23 | 512 | RIPE NCC | GB | 12th May 2005 |
| 86.54.226.0/23 | 512 | RIPE NCC | GB | 12th May 2005 |
| 86.54.229.0/24 | 256 | RIPE NCC | GB | 12th May 2005 |
| 86.54.230.0/23 | 512 | RIPE NCC | GB | 12th May 2005 |
| 86.54.232.0/23 | 512 | RIPE NCC | GB | 12th May 2005 |
| 86.54.236.0/22 | 1k | RIPE NCC | GB | 12th May 2005 |
| 86.54.240.0/21 | 2k | RIPE NCC | GB | 12th May 2005 |
| 86.54.250.0/23 | 512 | RIPE NCC | GB | 12th May 2005 |
| 86.54.252.0/22 | 1k | RIPE NCC | GB | 12th May 2005 |
| 86.54.40.0/23 | 512 | RIPE NCC | GB | 12th May 2005 |
| 86.54.48.0/20 | 4.1k | RIPE NCC | GB | 12th May 2005 |
| 86.54.64.0/20 | 4.1k | RIPE NCC | GB | 12th May 2005 |
| 86.54.8.0/23 | 512 | RIPE NCC | GB | 12th May 2005 |
| 86.54.84.0/23 | 512 | RIPE NCC | GB | 12th May 2005 |
| 86.54.88.0/21 | 2k | RIPE NCC | GB | 12th May 2005 |
| 86.62.28.0/22 | 1k | RIPE NCC | DE | 19th Nov 2018 |