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,783 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 86.226.0.0/16 | 65.5k | RIPE NCC |  US | 2nd Mar 2005 |
| 86.38.110.0/24 | 256 | RIPE NCC |  LT | 19th May 2005 |
| 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.56.0/22 | 1k | RIPE NCC |  RO | 19th Nov 2018 |
| 87.101.80.0/22 | 1k | RIPE NCC | RO | 22nd Aug 2018 |
| 87.104.128.0/18 | 16.4k | RIPE NCC | DK | 18th Jul 2005 |
| 87.111.0.0/16 | 65.5k | RIPE NCC |  ES | 20th Sept 2005 |
| 87.116.64.0/22 | 1k | RIPE NCC |  BG | 13th Sept 2005 |
| 87.116.68.0/22 | 1k | RIPE NCC | BG | 13th Sept 2005 |
| 87.116.72.0/21 | 2k | RIPE NCC | BG | 13th Sept 2005 |
| 87.116.82.0/24 | 256 | RIPE NCC | BG | 13th Sept 2005 |
| 87.116.83.0/24 | 256 | RIPE NCC | BG | 13th Sept 2005 |
| 87.116.84.0/22 | 1k | RIPE NCC | BG | 13th Sept 2005 |
| 87.116.92.0/22 | 1k | RIPE NCC | BG | 13th Sept 2005 |
| 87.117.139.0/24 | 256 | RIPE NCC |  RU | 28th Sept 2005 |
| 87.117.144.0/23 | 512 | RIPE NCC | RU | 28th Sept 2005 |
| 87.117.150.0/23 | 512 | RIPE NCC | RU | 28th Sept 2005 |
| 87.119.192.0/23 | 512 | RIPE NCC |  DE | 17th Nov 2005 |
| 87.119.196.0/22 | 1k | RIPE NCC | DE | 17th Nov 2005 |
| 87.119.208.0/21 | 2k | RIPE NCC | DE | 17th Nov 2005 |
| 87.120.144.0/21 | 2k | RIPE NCC | DE | 12th Jul 2005 |
| 87.120.16.0/20 | 4.1k | RIPE NCC | GB | 12th Jul 2005 |
| 87.120.164.0/24 | 256 | RIPE NCC |  LU | 12th Jul 2005 |