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 in Germany
2,788 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 185.165.16.0/22 | 1k | RIPE NCC |  DE | 24th Aug 2016 |
| 185.165.84.0/22 | 1k | RIPE NCC | DE | 25th Aug 2016 |
| 185.167.156.0/22 | 1k | RIPE NCC | DE | 13th Sept 2016 |
| 185.168.148.0/24 | 256 | RIPE NCC | DE | 29th Mar 2022 |
| 185.169.112.0/22 | 1k | RIPE NCC | DE | 23rd Sept 2016 |
| 185.169.128.0/22 | 1k | RIPE NCC | DE | 23rd Sept 2016 |
| 185.169.212.0/22 | 1k | RIPE NCC | DE | 27th Sept 2016 |
| 185.170.160.0/22 | 1k | RIPE NCC | DE | 30th Sept 2016 |
| 185.170.168.0/22 | 1k | RIPE NCC | DE | 30th Sept 2016 |
| 185.172.192.0/22 | 1k | RIPE NCC | DE | 13th Oct 2016 |
| 185.172.40.0/22 | 1k | RIPE NCC | DE | 10th Oct 2016 |
| 185.172.52.0/22 | 1k | RIPE NCC | DE | 10th Oct 2016 |
| 185.175.210.0/23 | 512 | RIPE NCC | DE | 1st Nov 2016 |
| 185.175.232.0/22 | 1k | RIPE NCC | DE | 1st Nov 2016 |
| 185.175.64.0/24 | 256 | RIPE NCC | DE | 10th Dec 2025 |
| 185.176.135.0/24 | 256 | RIPE NCC | DE | 12th Jan 2024 |
| 185.176.228.0/22 | 1k | RIPE NCC | DE | 8th Nov 2016 |
| 185.178.116.0/22 | 1k | RIPE NCC | DE | 18th Nov 2016 |
| 185.178.32.0/22 | 1k | RIPE NCC | DE | 17th Nov 2016 |
| 185.178.72.0/22 | 1k | RIPE NCC | DE | 18th Nov 2016 |
| 185.179.125.0/24 | 256 | RIPE NCC | DE | 22nd Jan 2026 |
| 185.179.127.0/24 | 256 | RIPE NCC | DE | 22nd Jan 2026 |
| 185.179.152.0/22 | 1k | RIPE NCC | DE | 28th Nov 2016 |
| 185.180.164.0/22 | 1k | RIPE NCC | DE | 6th Dec 2016 |
| 185.181.112.0/22 | 1k | RIPE NCC | DE | 9th Dec 2016 |
| 185.181.120.0/22 | 1k | RIPE NCC | DE | 9th Dec 2016 |
| 185.182.232.0/22 | 1k | RIPE NCC | DE | 19th Dec 2016 |
| 185.182.44.0/22 | 1k | RIPE NCC | DE | 14th Dec 2016 |
| 185.183.204.0/22 | 1k | RIPE NCC | DE | 29th Dec 2016 |
| 185.183.52.0/22 | 1k | RIPE NCC | DE | 20th Dec 2016 |
| 185.183.85.0/24 | 256 | RIPE NCC | DE | 21st Dec 2016 |
| 185.183.86.0/23 | 512 | RIPE NCC | DE | 21st Dec 2016 |
| 185.184.188.0/22 | 1k | RIPE NCC | DE | 5th Jan 2017 |
| 185.186.236.0/22 | 1k | RIPE NCC | DE | 23rd Jan 2017 |
| 185.186.24.0/22 | 1k | RIPE NCC | DE | 17th Jan 2017 |
| 185.188.16.0/24 | 256 | RIPE NCC | DE | 31st Jan 2017 |
| 185.188.204.0/22 | 1k | RIPE NCC | DE | 6th Sept 2018 |
| 185.188.240.0/22 | 1k | RIPE NCC | DE | 7th Feb 2017 |
| 185.189.0.0/22 | 1k | RIPE NCC | DE | 7th Feb 2017 |
| 185.189.96.0/22 | 1k | RIPE NCC | DE | 9th Feb 2017 |
| 185.19.36.0/22 | 1k | RIPE NCC | DE | 19th Feb 2013 |
| 185.19.60.0/22 | 1k | RIPE NCC | DE | 11th Dec 2014 |
| 185.190.228.0/22 | 1k | RIPE NCC | DE | 20th Feb 2017 |
| 185.190.236.0/22 | 1k | RIPE NCC | DE | 20th Feb 2017 |
| 185.192.172.0/22 | 1k | RIPE NCC | DE | 2nd Mar 2017 |
| 185.192.200.0/22 | 1k | RIPE NCC | DE | 2nd Mar 2017 |
| 185.194.13.0/24 | 256 | RIPE NCC | DE | 28th Sept 2020 |
| 185.194.149.0/24 | 256 | RIPE NCC | DE | 15th Mar 2017 |
| 185.194.36.0/22 | 1k | RIPE NCC | DE | 13th Mar 2017 |
| 185.195.112.0/22 | 1k | RIPE NCC | DE | 21st Mar 2017 |