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 unannounced space registered through RIPE NCC, largest first.
Unannounced blocks registered through RIPE NCC
25,269 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 185.177.108.0/22 | 1k | RIPE NCC | 11th Nov 2016 | |
| 185.177.160.0/22 | 1k | RIPE NCC | 14th Nov 2016 | |
| 185.177.208.0/24 | 256 | RIPE NCC | 31st Dec 2019 | |
| 185.177.210.0/24 | 256 | RIPE NCC | 2nd Jan 2020 | |
| 185.177.252.0/22 | 1k | RIPE NCC | 16th Nov 2016 | |
| 185.177.36.0/22 | 1k | RIPE NCC | 10th Nov 2016 | |
| 185.178.100.0/22 | 1k | RIPE NCC | 18th Nov 2016 | |
| 185.178.112.0/22 | 1k | RIPE NCC | 18th Nov 2016 | |
| 185.178.116.0/22 | 1k | RIPE NCC | 18th Nov 2016 | |
| 185.178.124.0/22 | 1k | RIPE NCC | 21st Nov 2016 | |
| 185.178.128.0/22 | 1k | RIPE NCC | 21st Nov 2016 | |
| 185.178.168.0/24 | 256 | RIPE NCC | 22nd Nov 2016 | |
| 185.178.170.0/24 | 256 | RIPE NCC | 22nd Nov 2016 | |
| 185.178.188.0/22 | 1k | RIPE NCC | 22nd Nov 2016 | |
| 185.178.230.0/24 | 256 | RIPE NCC | 23rd Nov 2016 | |
| 185.178.36.0/22 | 1k | RIPE NCC | 17th Nov 2016 | |
| 185.178.52.0/22 | 1k | RIPE NCC | 18th Nov 2016 | |
| 185.179.101.0/24 | 256 | RIPE NCC | 10th Aug 2020 | |
| 185.179.108.0/22 | 1k | RIPE NCC | 25th Nov 2016 | |
| 185.179.125.0/24 | 256 | RIPE NCC | 22nd Jan 2026 | |
| 185.179.126.0/24 | 256 | RIPE NCC | 22nd Jan 2026 | |
| 185.179.127.0/24 | 256 | RIPE NCC | 22nd Jan 2026 | |
| 185.179.160.0/22 | 1k | RIPE NCC | 29th Nov 2016 | |
| 185.179.204.0/22 | 1k | RIPE NCC | 30th Nov 2016 | |
| 185.179.240.0/22 | 1k | RIPE NCC | 30th Nov 2016 | |
| 185.179.244.0/24 | 256 | RIPE NCC | 14th Aug 2020 | |
| 185.179.4.0/22 | 1k | RIPE NCC | 24th Nov 2016 | |
| 185.18.156.0/22 | 1k | RIPE NCC | 12th Feb 2013 | |
| 185.18.160.0/22 | 1k | RIPE NCC | 12th Feb 2013 | |
| 185.18.172.0/22 | 1k | RIPE NCC | 13th Feb 2013 | |
| 185.18.88.0/23 | 512 | RIPE NCC | 7th Mar 2016 | |
| 185.180.136.0/22 | 1k | RIPE NCC | 5th Dec 2016 | |
| 185.180.164.0/22 | 1k | RIPE NCC | 6th Dec 2016 | |
| 185.180.176.0/22 | 1k | RIPE NCC | 6th Dec 2016 | |
| 185.180.208.0/22 | 1k | RIPE NCC | 7th Dec 2016 | |
| 185.180.4.0/22 | 1k | RIPE NCC | 1st Dec 2016 | |
| 185.180.84.0/22 | 1k | RIPE NCC | 5th Dec 2016 | |
| 185.181.172.0/22 | 1k | RIPE NCC | 12th Dec 2016 | |
| 185.181.184.0/22 | 1k | RIPE NCC | 13th Dec 2016 | |
| 185.181.200.0/22 | 1k | RIPE NCC | 13th Dec 2016 | |
| 185.181.56.0/22 | 1k | RIPE NCC | 8th Dec 2016 | |
| 185.181.88.0/22 | 1k | RIPE NCC | 9th Dec 2016 | |
| 185.182.16.0/22 | 1k | RIPE NCC | 14th Dec 2016 | |
| 185.182.60.0/22 | 1k | RIPE NCC | 14th Dec 2016 | |
| 185.183.204.0/22 | 1k | RIPE NCC | 29th Dec 2016 | |
| 185.183.52.0/22 | 1k | RIPE NCC | 20th Dec 2016 | |
| 185.183.8.0/22 | 1k | RIPE NCC | 20th Dec 2016 | |
| 185.183.85.0/24 | 256 | RIPE NCC | 21st Dec 2016 | |
| 185.183.86.0/23 | 512 | RIPE NCC | 21st Dec 2016 | |
| 185.183.96.0/24 | 256 | RIPE NCC | 22nd Dec 2016 |