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 |
|---|---|---|---|---|
| 212.40.169.0/24 | 256 | RIPE NCC |  DE | 19th Mar 1999 |
| 212.40.170.0/23 | 512 | RIPE NCC | DE | 19th Mar 1999 |
| 212.40.172.0/23 | 512 | RIPE NCC | DE | 19th Mar 1999 |
| 212.40.174.0/23 | 512 | RIPE NCC | DE | 19th Mar 1999 |
| 212.40.177.0/24 | 256 | RIPE NCC | DE | 19th Mar 1999 |
| 212.40.178.0/23 | 512 | RIPE NCC | DE | 19th Mar 1999 |
| 212.40.180.0/24 | 256 | RIPE NCC | DE | 19th Mar 1999 |
| 212.40.184.0/23 | 512 | RIPE NCC | DE | 19th Mar 1999 |
| 212.40.187.0/24 | 256 | RIPE NCC | DE | 19th Mar 1999 |
| 212.40.188.0/22 | 1k | RIPE NCC | DE | 19th Mar 1999 |
| 212.47.38.0/24 | 256 | RIPE NCC | DE | 20th Jan 2026 |
| 212.47.63.0/24 | 256 | RIPE NCC | DE | 23rd Jun 2026 |
| 212.63.160.0/19 | 8.2k | RIPE NCC | DE | 17th Mar 1999 |
| 212.78.109.0/24 | 256 | RIPE NCC | DE | 10th Nov 1999 |
| 212.78.110.0/23 | 512 | RIPE NCC | DE | 10th Nov 1999 |
| 212.78.96.0/21 | 2k | RIPE NCC | DE | 10th Nov 1999 |
| 212.79.224.0/19 | 8.2k | RIPE NCC | DE | 19th May 2000 |
| 212.88.192.0/19 | 8.2k | RIPE NCC | DE | 21st Apr 1999 |
| 213.134.3.0/24 | 256 | RIPE NCC | DE | 9th Jan 2024 |
| 213.163.250.0/23 | 512 | RIPE NCC | DE | 10th Feb 2003 |
| 213.173.16.0/20 | 4.1k | RIPE NCC | DE | 4th Jan 2000 |
| 213.177.163.0/24 | 256 | RIPE NCC | DE | 15th Oct 2025 |
| 213.178.128.0/22 | 1k | RIPE NCC | DE | 18th Mar 2019 |
| 213.218.168.0/21 | 2k | RIPE NCC | DE | 12th May 2003 |
| 213.218.176.0/20 | 4.1k | RIPE NCC | DE | 12th May 2003 |
| 213.232.193.0/24 | 256 | RIPE NCC | DE | 26th Jan 2026 |
| 213.244.44.0/22 | 1k | RIPE NCC | DE | 11th Jul 2002 |
| 217.115.138.0/23 | 512 | RIPE NCC | DE | 1st Feb 2001 |
| 217.115.144.0/24 | 256 | RIPE NCC | DE | 29th May 2001 |
| 217.118.16.0/23 | 512 | RIPE NCC | DE | 22nd Nov 2004 |
| 217.118.18.0/24 | 256 | RIPE NCC | DE | 22nd Nov 2004 |
| 217.118.20.0/23 | 512 | RIPE NCC | DE | 22nd Nov 2004 |
| 217.118.22.0/24 | 256 | RIPE NCC | DE | 22nd Nov 2004 |
| 217.118.25.0/24 | 256 | RIPE NCC | DE | 22nd Nov 2004 |
| 217.118.28.0/22 | 1k | RIPE NCC | DE | 22nd Nov 2004 |
| 217.119.48.0/24 | 256 | RIPE NCC | DE | 26th Feb 2004 |
| 217.119.49.0/24 | 256 | RIPE NCC | DE | 26th Feb 2004 |
| 217.119.50.0/24 | 256 | RIPE NCC | DE | 26th Feb 2004 |
| 217.119.51.0/24 | 256 | RIPE NCC | DE | 26th Feb 2004 |
| 217.119.54.0/24 | 256 | RIPE NCC | DE | 26th Feb 2004 |
| 217.119.56.0/24 | 256 | RIPE NCC | DE | 26th Feb 2004 |
| 217.119.57.0/24 | 256 | RIPE NCC | DE | 26th Feb 2004 |
| 217.119.60.0/22 | 1k | RIPE NCC | DE | 26th Feb 2004 |
| 217.154.128.0/23 | 512 | RIPE NCC | DE | 19th Feb 2001 |
| 217.154.130.0/24 | 256 | RIPE NCC | DE | 19th Feb 2001 |
| 217.154.136.0/24 | 256 | RIPE NCC | DE | 19th Feb 2001 |
| 217.154.139.0/24 | 256 | RIPE NCC | DE | 19th Feb 2001 |
| 217.154.140.0/24 | 256 | RIPE NCC | DE | 19th Feb 2001 |
| 217.154.29.0/24 | 256 | RIPE NCC | DE | 19th Feb 2001 |
| 217.172.160.0/23 | 512 | RIPE NCC | DE | 6th Apr 2001 |