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 in Germany
2,730 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 185.124.48.0/22 | 1k | RIPE NCC |  DE | 30th Oct 2015 |
| 185.124.66.0/24 | 256 | RIPE NCC | DE | 25th Jan 2022 |
| 185.124.67.0/24 | 256 | RIPE NCC | DE | 25th Jan 2022 |
| 185.127.200.0/22 | 1k | RIPE NCC | DE | 31st Oct 2018 |
| 185.128.126.0/23 | 512 | RIPE NCC | DE | 26th Nov 2015 |
| 185.128.44.0/22 | 1k | RIPE NCC | DE | 24th Nov 2015 |
| 185.13.68.0/22 | 1k | RIPE NCC | DE | 13th Dec 2012 |
| 185.131.201.0/24 | 256 | RIPE NCC | DE | 10th Jan 2024 |
| 185.132.208.0/22 | 1k | RIPE NCC | DE | 23rd Dec 2015 |
| 185.134.4.0/24 | 256 | RIPE NCC | DE | 11th Jan 2016 |
| 185.134.5.0/24 | 256 | RIPE NCC | DE | 11th Jan 2016 |
| 185.135.24.0/22 | 1k | RIPE NCC | DE | 20th Jan 2016 |
| 185.136.140.0/22 | 1k | RIPE NCC | DE | 1st Feb 2016 |
| 185.137.157.0/24 | 256 | RIPE NCC | DE | 7th Jan 2025 |
| 185.138.24.0/22 | 1k | RIPE NCC | DE | 9th Feb 2016 |
| 185.139.72.0/22 | 1k | RIPE NCC | DE | 18th Feb 2016 |
| 185.139.96.0/22 | 1k | RIPE NCC | DE | 18th Feb 2016 |
| 185.141.148.0/22 | 1k | RIPE NCC | DE | 3rd Mar 2016 |
| 185.142.108.0/22 | 1k | RIPE NCC | DE | 9th Mar 2016 |
| 185.145.190.0/24 | 256 | RIPE NCC | DE | 4th Apr 2016 |
| 185.145.234.0/24 | 256 | RIPE NCC | DE | 23rd Jun 2021 |
| 185.147.4.0/22 | 1k | RIPE NCC | DE | 12th Apr 2016 |
| 185.147.54.0/24 | 256 | RIPE NCC | DE | 18th Aug 2021 |
| 185.148.88.0/22 | 1k | RIPE NCC | DE | 20th Apr 2016 |
| 185.149.224.0/22 | 1k | RIPE NCC | DE | 28th Apr 2016 |
| 185.153.233.0/24 | 256 | RIPE NCC | DE | 30th Sept 2020 |
| 185.153.88.0/22 | 1k | RIPE NCC | DE | 23rd May 2016 |
| 185.154.104.0/22 | 1k | RIPE NCC | DE | 31st May 2016 |
| 185.154.28.0/22 | 1k | RIPE NCC | DE | 27th May 2016 |
| 185.159.245.0/24 | 256 | RIPE NCC | DE | 22nd Nov 2023 |
| 185.159.86.0/24 | 256 | RIPE NCC | DE | 23rd Jun 2021 |
| 185.160.172.0/22 | 1k | RIPE NCC | DE | 30th Jan 2019 |
| 185.160.200.0/22 | 1k | RIPE NCC | DE | 25th Jul 2016 |
| 185.160.240.0/22 | 1k | RIPE NCC | DE | 26th Jul 2016 |
| 185.160.78.0/23 | 512 | RIPE NCC | DE | 20th Jul 2016 |
| 185.160.84.0/22 | 1k | RIPE NCC | DE | 20th Jul 2016 |
| 185.164.161.0/24 | 256 | RIPE NCC | DE | 13th Mar 2023 |
| 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.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.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.192.0/22 | 1k | RIPE NCC | DE | 5th Aug 2019 |