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 |
|---|---|---|---|---|
| 89.34.76.0/24 | 256 | RIPE NCC | 29th Nov 2005 | |
| 89.34.80.0/21 | 2k | RIPE NCC | 29th Nov 2005 | |
| 89.34.93.0/24 | 256 | RIPE NCC | 29th Nov 2005 | |
| 89.35.116.0/24 | 256 | RIPE NCC | 29th Nov 2005 | |
| 89.35.120.0/22 | 1k | RIPE NCC | 29th Nov 2005 | |
| 89.35.152.0/24 | 256 | RIPE NCC | 29th Nov 2005 | |
| 89.35.172.0/24 | 256 | RIPE NCC | 29th Nov 2005 | |
| 89.35.179.0/24 | 256 | RIPE NCC | 29th Nov 2005 | |
| 89.35.180.0/22 | 1k | RIPE NCC | 29th Nov 2005 | |
| 89.35.184.0/21 | 2k | RIPE NCC | 29th Nov 2005 | |
| 89.35.200.0/22 | 1k | RIPE NCC | 29th Nov 2005 | |
| 89.35.216.0/21 | 2k | RIPE NCC | 29th Nov 2005 | |
| 89.35.237.0/24 | 256 | RIPE NCC | 29th Nov 2005 | |
| 89.35.239.0/24 | 256 | RIPE NCC | 29th Nov 2005 | |
| 89.35.240.0/21 | 2k | RIPE NCC | 29th Nov 2005 | |
| 89.35.26.0/24 | 256 | RIPE NCC | 29th Nov 2005 | |
| 89.35.40.0/21 | 2k | RIPE NCC | 29th Nov 2005 | |
| 89.35.51.0/24 | 256 | RIPE NCC | 29th Nov 2005 | |
| 89.35.64.0/21 | 2k | RIPE NCC | 29th Nov 2005 | |
| 89.35.72.0/24 | 256 | RIPE NCC | 29th Nov 2005 | |
| 89.35.84.0/22 | 1k | RIPE NCC | 29th Nov 2005 | |
| 89.36.150.0/23 | 512 | RIPE NCC | 29th Nov 2005 | |
| 89.36.155.0/24 | 256 | RIPE NCC | 29th Nov 2005 | |
| 89.36.156.0/22 | 1k | RIPE NCC | 29th Nov 2005 | |
| 89.36.21.0/24 | 256 | RIPE NCC | 29th Nov 2005 | |
| 89.36.228.0/24 | 256 | RIPE NCC | 29th Nov 2005 | |
| 89.36.240.0/21 | 2k | RIPE NCC | 29th Nov 2005 | |
| 89.36.248.0/22 | 1k | RIPE NCC | 29th Nov 2005 | |
| 89.36.252.0/23 | 512 | RIPE NCC | 29th Nov 2005 | |
| 89.36.255.0/24 | 256 | RIPE NCC | 29th Nov 2005 | |
| 89.36.73.0/24 | 256 | RIPE NCC | 29th Nov 2005 | |
| 89.36.77.0/24 | 256 | RIPE NCC | 29th Nov 2005 | |
| 89.36.88.0/24 | 256 | RIPE NCC | 29th Nov 2005 | |
| 89.36.92.0/24 | 256 | RIPE NCC | 29th Nov 2005 | |
| 89.37.141.0/24 | 256 | RIPE NCC | 29th Nov 2005 | |
| 89.37.142.0/24 | 256 | RIPE NCC | 29th Nov 2005 | |
| 89.37.160.0/21 | 2k | RIPE NCC | 29th Nov 2005 | |
| 89.37.200.0/21 | 2k | RIPE NCC | 29th Nov 2005 | |
| 89.37.32.0/21 | 2k | RIPE NCC | 29th Nov 2005 | |
| 89.37.44.0/22 | 1k | RIPE NCC | 29th Nov 2005 | |
| 89.37.48.0/21 | 2k | RIPE NCC | 29th Nov 2005 | |
| 89.37.57.0/24 | 256 | RIPE NCC | 29th Nov 2005 | |
| 89.37.94.0/24 | 256 | RIPE NCC | 29th Nov 2005 | |
| 89.38.0.0/21 | 2k | RIPE NCC | 29th Nov 2005 | |
| 89.38.108.0/22 | 1k | RIPE NCC | 29th Nov 2005 | |
| 89.38.168.0/21 | 2k | RIPE NCC | 29th Nov 2005 | |
| 89.38.235.0/24 | 256 | RIPE NCC | 29th Nov 2005 | |
| 89.38.237.0/24 | 256 | RIPE NCC | 29th Nov 2005 | |
| 89.38.27.0/24 | 256 | RIPE NCC | 29th Nov 2005 | |
| 89.38.36.0/23 | 512 | RIPE NCC | 29th Nov 2005 |