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 |
|---|---|---|---|---|
| 85.93.94.0/23 | 512 | RIPE NCC |  DE | 8th Dec 2004 |
| 86.104.216.0/22 | 1k | RIPE NCC | DE | 18th Apr 2005 |
| 86.107.191.0/24 | 256 | RIPE NCC | DE | 18th Apr 2005 |
| 86.62.28.0/22 | 1k | RIPE NCC | DE | 19th Nov 2018 |
| 87.119.192.0/23 | 512 | RIPE NCC | DE | 17th Nov 2005 |
| 87.119.196.0/22 | 1k | RIPE NCC | DE | 17th Nov 2005 |
| 87.119.208.0/21 | 2k | RIPE NCC | DE | 17th Nov 2005 |
| 87.120.144.0/21 | 2k | RIPE NCC | DE | 12th Jul 2005 |
| 87.121.28.0/22 | 1k | RIPE NCC | DE | 12th Jul 2005 |
| 87.199.126.0/24 | 256 | RIPE NCC | DE | 28th Jun 2006 |
| 87.199.148.0/22 | 1k | RIPE NCC | DE | 28th Jun 2006 |
| 87.199.96.0/21 | 2k | RIPE NCC | DE | 28th Jun 2006 |
| 87.230.32.0/22 | 1k | RIPE NCC | DE | 25th Jul 2005 |
| 87.230.48.0/23 | 512 | RIPE NCC | DE | 25th Jul 2005 |
| 87.230.64.0/24 | 256 | RIPE NCC | DE | 25th Jul 2005 |
| 87.230.65.0/24 | 256 | RIPE NCC | DE | 25th Jul 2005 |
| 87.230.66.0/23 | 512 | RIPE NCC | DE | 25th Jul 2005 |
| 87.230.68.0/22 | 1k | RIPE NCC | DE | 25th Jul 2005 |
| 87.230.76.0/22 | 1k | RIPE NCC | DE | 25th Jul 2005 |
| 87.230.80.0/23 | 512 | RIPE NCC | DE | 25th Jul 2005 |
| 87.237.165.0/24 | 256 | RIPE NCC | DE | 8th May 2020 |
| 87.237.88.0/21 | 2k | RIPE NCC | DE | 10th Nov 2005 |
| 87.247.240.0/21 | 2k | RIPE NCC | DE | 3rd Feb 2006 |
| 87.252.120.0/22 | 1k | RIPE NCC | DE | 21st Sept 2005 |
| 87.252.124.0/23 | 512 | RIPE NCC | DE | 21st Sept 2005 |
| 87.253.176.0/21 | 2k | RIPE NCC | DE | 6th Oct 2005 |
| 88.80.192.0/19 | 8.2k | RIPE NCC | DE | 1st Dec 2005 |
| 88.82.224.0/19 | 8.2k | RIPE NCC | DE | 27th Dec 2005 |
| 89.207.156.0/24 | 256 | RIPE NCC | DE | 7th Jan 2025 |
| 89.34.3.0/24 | 256 | RIPE NCC | DE | 29th Nov 2005 |
| 89.37.141.0/24 | 256 | RIPE NCC | DE | 29th Nov 2005 |
| 89.38.36.0/23 | 512 | RIPE NCC | DE | 29th Nov 2005 |
| 89.40.134.0/23 | 512 | RIPE NCC | DE | 29th Nov 2005 |
| 91.102.121.0/24 | 256 | RIPE NCC | DE | 31st Mar 2026 |
| 91.103.216.0/21 | 2k | RIPE NCC | DE | 6th Dec 2006 |
| 91.109.40.0/22 | 1k | RIPE NCC | DE | 18th Jun 2012 |
| 91.132.0.0/22 | 1k | RIPE NCC | DE | 18th Dec 2018 |
| 91.143.240.0/20 | 4.1k | RIPE NCC | DE | 8th Nov 2006 |
| 91.146.104.0/21 | 2k | RIPE NCC | DE | 8th Sept 2011 |
| 91.190.248.0/21 | 2k | RIPE NCC | DE | 11th Jan 2007 |
| 91.192.163.0/24 | 256 | RIPE NCC | DE | 13th Oct 2025 |
| 91.193.113.0/24 | 256 | RIPE NCC | DE | 15th May 2020 |
| 91.193.72.0/24 | 256 | RIPE NCC | DE | 4th Jun 2012 |
| 91.195.104.0/23 | 512 | RIPE NCC | DE | 7th Sept 2007 |
| 91.195.242.0/23 | 512 | RIPE NCC | DE | 25th Oct 2007 |
| 91.195.48.0/23 | 512 | RIPE NCC | DE | 23rd Aug 2007 |
| 91.196.220.0/22 | 1k | RIPE NCC | DE | 26th Jun 2018 |
| 91.198.142.0/24 | 256 | RIPE NCC | DE | 2nd Nov 2026 |
| 91.198.165.0/24 | 256 | RIPE NCC | DE | 1st Oct 2007 |
| 91.198.189.0/24 | 256 | RIPE NCC | DE | 14th Sept 2011 |