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,818 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 85.137.20.0/22 | 1k | RIPE NCC | 3rd Nov 2004 | |
| 85.137.208.0/22 | 1k | RIPE NCC | 3rd Nov 2004 | |
| 85.137.212.0/23 | 512 | RIPE NCC | 3rd Nov 2004 | |
| 85.137.215.0/24 | 256 | RIPE NCC | 3rd Nov 2004 | |
| 85.137.216.0/22 | 1k | RIPE NCC | 3rd Nov 2004 | |
| 85.137.224.0/22 | 1k | RIPE NCC | 3rd Nov 2004 | |
| 85.137.236.0/24 | 256 | RIPE NCC | 3rd Nov 2004 | |
| 85.137.80.0/24 | 256 | RIPE NCC | 3rd Nov 2004 | |
| 85.137.81.0/24 | 256 | RIPE NCC | 3rd Nov 2004 | |
| 85.137.82.0/23 | 512 | RIPE NCC | 3rd Nov 2004 | |
| 85.149.240.0/20 | 4.1k | RIPE NCC | 6th Oct 2004 | |
| 85.155.0.0/19 | 8.2k | RIPE NCC | 5th Nov 2004 | |
| 85.155.192.0/19 | 8.2k | RIPE NCC | 5th Nov 2004 | |
| 85.159.112.0/24 | 256 | RIPE NCC | 30th Dec 2019 | |
| 85.159.113.0/24 | 256 | RIPE NCC | 30th Dec 2019 | |
| 85.159.120.0/21 | 2k | RIPE NCC | 15th Mar 2005 | |
| 85.159.136.0/21 | 2k | RIPE NCC | 21st Mar 2005 | |
| 85.159.184.0/21 | 2k | RIPE NCC | 30th Mar 2005 | |
| 85.159.56.0/21 | 2k | RIPE NCC | 24th Feb 2005 | |
| 85.184.200.0/21 | 2k | RIPE NCC | 19th Nov 2004 | |
| 85.184.208.0/20 | 4.1k | RIPE NCC | 19th Nov 2004 | |
| 85.188.192.0/18 | 16.4k | RIPE NCC | 13th Apr 2006 | |
| 85.194.192.0/23 | 512 | RIPE NCC | 4th Jan 2005 | |
| 85.194.232.0/24 | 256 | RIPE NCC | 4th Jan 2005 | |
| 85.194.234.0/23 | 512 | RIPE NCC | 4th Jan 2005 | |
| 85.194.252.0/23 | 512 | RIPE NCC | 4th Jan 2005 | |
| 85.194.254.0/23 | 512 | RIPE NCC | 4th Jan 2005 | |
| 85.197.192.0/18 | 16.4k | RIPE NCC | 25th Jan 2005 | |
| 85.198.48.0/20 | 4.1k | RIPE NCC | 31st Jan 2005 | |
| 85.198.92.0/22 | 1k | RIPE NCC | 31st Jan 2005 | |
| 85.199.248.0/24 | 256 | RIPE NCC | 8th Feb 2005 | |
| 85.202.200.0/24 | 256 | RIPE NCC | 12th Feb 2020 | |
| 85.202.204.0/22 | 1k | RIPE NCC | 22nd Aug 2018 | |
| 85.202.208.0/20 | 4.1k | RIPE NCC | 6th Feb 2008 | |
| 85.204.119.0/24 | 256 | RIPE NCC | 13th Jan 2005 | |
| 85.204.132.0/23 | 512 | RIPE NCC | 13th Jan 2005 | |
| 85.204.136.0/23 | 512 | RIPE NCC | 13th Jan 2005 | |
| 85.204.147.0/24 | 256 | RIPE NCC | 13th Jan 2005 | |
| 85.204.194.0/23 | 512 | RIPE NCC | 13th Jan 2005 | |
| 85.204.198.0/24 | 256 | RIPE NCC | 13th Jan 2005 | |
| 85.204.39.0/24 | 256 | RIPE NCC | 13th Jan 2005 | |
| 85.204.41.0/24 | 256 | RIPE NCC | 13th Jan 2005 | |
| 85.208.100.0/22 | 1k | RIPE NCC | 21st Feb 2019 | |
| 85.208.120.0/22 | 1k | RIPE NCC | 21st Feb 2019 | |
| 85.208.132.0/22 | 1k | RIPE NCC | 21st Feb 2019 | |
| 85.208.152.0/22 | 1k | RIPE NCC | 21st Feb 2019 | |
| 85.208.156.0/22 | 1k | RIPE NCC | 21st Feb 2019 | |
| 85.208.164.0/22 | 1k | RIPE NCC | 22nd Feb 2019 | |
| 85.208.232.0/22 | 1k | RIPE NCC | 22nd Feb 2019 | |
| 85.208.88.0/22 | 1k | RIPE NCC | 21st Feb 2019 |