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 |
|---|---|---|---|---|
| 160.70.0.0/16 | 65.5k | RIPE NCC |  DE | 5th Apr 2004 |
| 161.218.0.0/16 | 65.5k | RIPE NCC | DE | 1st Sept 1993 |
| 161.38.64.0/18 | 16.4k | RIPE NCC | DE | 14th May 1992 |
| 162.33.128.0/20 | 4.1k | RIPE NCC | DE | 20th Jul 1992 |
| 163.242.0.0/16 | 65.5k | RIPE NCC | DE | 1st Sept 1993 |
| 164.34.0.0/16 | 65.5k | RIPE NCC | DE | 22nd Sept 1992 |
| 164.37.42.0/24 | 256 | RIPE NCC | DE | 31st Jan 1993 |
| 164.37.52.0/22 | 1k | RIPE NCC | DE | 31st Jan 1993 |
| 165.218.0.0/16 | 65.5k | RIPE NCC | DE | 1st Sept 1993 |
| 167.104.0.0/19 | 8.2k | RIPE NCC | DE | 28th Mar 1993 |
| 167.104.128.0/19 | 8.2k | RIPE NCC | DE | 28th Mar 1993 |
| 167.104.224.0/19 | 8.2k | RIPE NCC | DE | 28th Mar 1993 |
| 167.87.0.0/16 | 65.5k | RIPE NCC | DE | 17th May 1993 |
| 171.25.178.0/24 | 256 | RIPE NCC | DE | 11th Apr 2012 |
| 176.101.168.0/24 | 256 | RIPE NCC | DE | 24th Jun 2020 |
| 176.110.109.0/24 | 256 | RIPE NCC | DE | 21st Apr 2021 |
| 176.113.76.0/22 | 1k | RIPE NCC | DE | 15th Oct 2018 |
| 176.115.224.0/21 | 2k | RIPE NCC | DE | 4th May 2012 |
| 176.119.144.0/24 | 256 | RIPE NCC | DE | 4th Feb 2020 |
| 176.120.23.0/24 | 256 | RIPE NCC | DE | 27th Aug 2024 |
| 176.123.48.0/24 | 256 | RIPE NCC | DE | 27th Jul 2012 |
| 176.126.74.0/24 | 256 | RIPE NCC | DE | 14th Sept 2012 |
| 176.28.56.0/22 | 1k | RIPE NCC | DE | 20th May 2011 |
| 176.28.62.0/24 | 256 | RIPE NCC | DE | 20th May 2011 |
| 176.97.209.0/24 | 256 | RIPE NCC | DE | 22nd Oct 2021 |
| 178.132.240.0/21 | 2k | RIPE NCC | DE | 3rd Oct 2011 |
| 178.20.8.0/21 | 2k | RIPE NCC | DE | 16th Feb 2010 |
| 178.213.74.0/24 | 256 | RIPE NCC | DE | 24th Sept 2010 |
| 178.217.232.0/24 | 256 | RIPE NCC | DE | 10th Jul 2020 |
| 178.23.48.0/21 | 2k | RIPE NCC | DE | 20th Apr 2010 |
| 178.239.39.0/24 | 256 | RIPE NCC | DE | 2nd Aug 2010 |
| 178.77.124.0/24 | 256 | RIPE NCC | DE | 15th Apr 2010 |
| 185.0.17.0/24 | 256 | RIPE NCC | DE | 11th Jan 2023 |
| 185.0.3.0/24 | 256 | RIPE NCC | DE | 27th Oct 2022 |
| 185.0.33.0/24 | 256 | RIPE NCC | DE | 16th Jun 2023 |
| 185.0.35.0/24 | 256 | RIPE NCC | DE | 13th Jul 2023 |
| 185.0.4.0/24 | 256 | RIPE NCC | DE | 8th Nov 2022 |
| 185.0.5.0/24 | 256 | RIPE NCC | DE | 8th Nov 2022 |
| 185.0.6.0/24 | 256 | RIPE NCC | DE | 8th Nov 2022 |
| 185.0.7.0/24 | 256 | RIPE NCC | DE | 8th Nov 2022 |
| 185.0.8.0/24 | 256 | RIPE NCC | DE | 11th Nov 2022 |
| 185.1.102.0/24 | 256 | RIPE NCC | DE | 14th Nov 2017 |
| 185.1.119.0/24 | 256 | RIPE NCC | DE | 12th Feb 2021 |
| 185.1.125.0/24 | 256 | RIPE NCC | DE | 18th Dec 2018 |
| 185.1.131.0/24 | 256 | RIPE NCC | DE | 21st Feb 2019 |
| 185.1.155.0/24 | 256 | RIPE NCC | DE | 10th Dec 2019 |
| 185.1.166.0/23 | 512 | RIPE NCC | DE | 23rd Apr 2020 |
| 185.1.170.0/23 | 512 | RIPE NCC | DE | 29th May 2020 |
| 185.1.175.0/24 | 256 | RIPE NCC | DE | 23rd Jun 2020 |
| 185.1.176.0/24 | 256 | RIPE NCC | DE | 22nd May 2023 |