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,075 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 185.130.128.0/22 | 1k | RIPE NCC | 8th Dec 2015 | |
| 185.130.209.0/24 | 256 | RIPE NCC | 10th Dec 2015 | |
| 185.130.210.0/23 | 512 | RIPE NCC | 10th Dec 2015 | |
| 185.130.51.0/24 | 256 | RIPE NCC | 11th Jan 2024 | |
| 185.130.91.0/24 | 256 | RIPE NCC | 21st Jun 2021 | |
| 185.130.96.0/22 | 1k | RIPE NCC | 8th Dec 2015 | |
| 185.131.104.0/22 | 1k | RIPE NCC | 16th Dec 2015 | |
| 185.131.201.0/24 | 256 | RIPE NCC | 10th Jan 2024 | |
| 185.131.202.0/24 | 256 | RIPE NCC | 16th Mar 2026 | |
| 185.131.4.0/22 | 1k | RIPE NCC | 11th Dec 2015 | |
| 185.131.56.0/22 | 1k | RIPE NCC | 15th Dec 2015 | |
| 185.132.100.0/22 | 1k | RIPE NCC | 22nd Dec 2015 | |
| 185.132.190.0/23 | 512 | RIPE NCC | 23rd Dec 2015 | |
| 185.132.192.0/22 | 1k | RIPE NCC | 23rd Dec 2015 | |
| 185.132.208.0/22 | 1k | RIPE NCC | 23rd Dec 2015 | |
| 185.132.248.0/22 | 1k | RIPE NCC | 28th Dec 2015 | |
| 185.133.140.0/22 | 1k | RIPE NCC | 5th Jan 2016 | |
| 185.133.144.0/22 | 1k | RIPE NCC | 5th Jan 2016 | |
| 185.133.148.0/22 | 1k | RIPE NCC | 5th Jan 2016 | |
| 185.133.176.0/22 | 1k | RIPE NCC | 6th Jan 2016 | |
| 185.133.192.0/22 | 1k | RIPE NCC | 7th Jan 2016 | |
| 185.133.252.0/22 | 1k | RIPE NCC | 11th Jan 2016 | |
| 185.133.34.0/24 | 256 | RIPE NCC | 27th Jan 2026 | |
| 185.134.105.0/24 | 256 | RIPE NCC | 28th May 2025 | |
| 185.134.188.0/24 | 256 | RIPE NCC | 11th Aug 2025 | |
| 185.134.190.0/24 | 256 | RIPE NCC | 11th Aug 2025 | |
| 185.134.200.0/22 | 1k | RIPE NCC | 18th Jan 2016 | |
| 185.134.4.0/24 | 256 | RIPE NCC | 11th Jan 2016 | |
| 185.134.5.0/24 | 256 | RIPE NCC | 11th Jan 2016 | |
| 185.134.92.0/22 | 1k | RIPE NCC | 14th Jan 2016 | |
| 185.135.0.0/22 | 1k | RIPE NCC | 19th Jan 2016 | |
| 185.135.108.0/22 | 1k | RIPE NCC | 21st Jan 2016 | |
| 185.135.152.0/22 | 1k | RIPE NCC | 22nd Jan 2016 | |
| 185.135.196.0/24 | 256 | RIPE NCC | 3rd Feb 2026 | |
| 185.135.197.0/24 | 256 | RIPE NCC | 3rd Feb 2026 | |
| 185.135.199.0/24 | 256 | RIPE NCC | 5th Feb 2026 | |
| 185.135.24.0/22 | 1k | RIPE NCC | 20th Jan 2016 | |
| 185.135.45.0/24 | 256 | RIPE NCC | 7th Mar 2023 | |
| 185.135.46.0/24 | 256 | RIPE NCC | 7th Mar 2023 | |
| 185.136.140.0/22 | 1k | RIPE NCC | 1st Feb 2016 | |
| 185.136.228.0/22 | 1k | RIPE NCC | 2nd Feb 2016 | |
| 185.136.232.0/22 | 1k | RIPE NCC | 2nd Feb 2016 | |
| 185.136.240.0/24 | 256 | RIPE NCC | 21st Jan 2026 | |
| 185.136.241.0/24 | 256 | RIPE NCC | 21st Jan 2026 | |
| 185.136.32.0/22 | 1k | RIPE NCC | 27th Jan 2016 | |
| 185.136.60.0/22 | 1k | RIPE NCC | 27th Jan 2016 | |
| 185.136.8.0/22 | 1k | RIPE NCC | 26th Jan 2016 | |
| 185.137.157.0/24 | 256 | RIPE NCC | 7th Jan 2025 | |
| 185.137.192.0/22 | 1k | RIPE NCC | 8th Feb 2016 | |
| 185.137.243.0/24 | 256 | RIPE NCC | 8th Feb 2016 |