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 United States
599 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 200.163.80.0/20 | 4.1k | RIPE NCC | 13th Mar 2025 | |
| 200.169.176.0/20 | 4.1k | RIPE NCC | 13th Mar 2025 | |
| 200.181.80.0/20 | 4.1k | RIPE NCC | 13th Mar 2025 | |
| 200.203.0.0/20 | 4.1k | RIPE NCC | 13th Mar 2025 | |
| 200.240.0.0/19 | 8.2k | RIPE NCC | 17th Nov 1999 | |
| 2001:1510::/32 | 4.3B × /64 | RIPE NCC | 23rd Jul 2003 | |
| 2001:3540::/29 | 34.4B × /64 | RIPE NCC | 12th Sept 2024 | |
| 2001:38c0::/32 | 4.3B × /64 | RIPE NCC | 17th Sept 2024 | |
| 2001:678:106c::/48 | 65.5k × /64 | RIPE NCC | 10th Apr 2025 | |
| 2001:678:218::/48 | 65.5k × /64 | RIPE NCC | 1st Sept 2025 | |
| 2001:678:34c::/48 | 65.5k × /64 | RIPE NCC | 22nd Dec 2016 | |
| 2001:678:c04::/48 | 65.5k × /64 | RIPE NCC | 10th Jun 2025 | |
| 2001:67c:114c::/48 | 65.5k × /64 | RIPE NCC | 15th Feb 2023 | |
| 2001:67c:25f8::/48 | 65.5k × /64 | RIPE NCC | 12th Dec 2011 | |
| 2001:67c:29bc::/48 | 65.5k × /64 | RIPE NCC | 4th Mar 2020 | |
| 2001:67c:a0c::/48 | 65.5k × /64 | RIPE NCC | 13th Jun 2022 | |
| 2001:67c:c88::/48 | 65.5k × /64 | RIPE NCC | 11th Feb 2026 | |
| 2001:67c:cc0::/48 | 65.5k × /64 | RIPE NCC | 21st Jul 2023 | |
| 2001:67c:cc4::/48 | 65.5k × /64 | RIPE NCC | 21st Jul 2023 | |
| 2001:67c:d58::/48 | 65.5k × /64 | RIPE NCC | 29th Nov 2023 | |
| 2001:67c:d80::/48 | 65.5k × /64 | RIPE NCC | 10th Jan 2024 | |
| 2001:7f8:fd::/48 | 65.5k × /64 | RIPE NCC | 6th Jul 2020 | |
| 201.11.224.0/20 | 4.1k | RIPE NCC | 13th Mar 2025 | |
| 201.58.128.0/18 | 16.4k | RIPE NCC | 6th Mar 2025 | |
| 201.8.64.0/18 | 16.4k | RIPE NCC | 6th Mar 2025 | |
| 203.81.192.0/20 | 4.1k | RIPE NCC | 10th Jul 2001 | |
| 205.209.28.0/24 | 256 | RIPE NCC | 2nd Mar 2017 | |
| 206.206.16.0/20 | 4.1k | RIPE NCC | 19th Jul 1995 | |
| 207.229.116.0/24 | 256 | RIPE NCC | 30th Dec 1996 | |
| 207.229.122.0/24 | 256 | RIPE NCC | 30th Dec 1996 | |
| 209.16.176.0/24 | 256 | RIPE NCC | 31st Jan 1997 | |
| 209.16.178.0/24 | 256 | RIPE NCC | 31st Jan 1997 | |
| 209.162.144.0/21 | 2k | RIPE NCC | 14th Nov 1997 | |
| 209.162.152.0/23 | 512 | RIPE NCC | 14th Nov 1997 | |
| 209.162.155.0/24 | 256 | RIPE NCC | 14th Nov 1997 | |
| 209.162.156.0/24 | 256 | RIPE NCC | 14th Nov 1997 | |
| 209.162.157.0/24 | 256 | RIPE NCC | 14th Nov 1997 | |
| 209.162.158.0/23 | 512 | RIPE NCC | 14th Nov 1997 | |
| 212.117.32.0/20 | 4.1k | RIPE NCC | 30th Jan 2008 | |
| 212.47.62.0/24 | 256 | RIPE NCC | 23rd Jun 2026 | |
| 212.6.42.0/24 | 256 | RIPE NCC | 17th Jan 2025 | |
| 213.109.104.0/22 | 1k | RIPE NCC | 9th Sept 2009 | |
| 213.134.24.0/24 | 256 | RIPE NCC | 16th Jan 2024 | |
| 213.134.28.0/24 | 256 | RIPE NCC | 22nd Jan 2024 | |
| 213.170.143.0/24 | 256 | RIPE NCC | 16th Feb 2000 | |
| 213.187.148.0/22 | 1k | RIPE NCC | 18th Feb 2000 | |
| 216.150.24.0/22 | 1k | RIPE NCC | 14th Jul 1999 | |
| 216.247.120.0/21 | 2k | RIPE NCC | 21st Oct 1999 | |
| 2a00:42e0::/29 | 34.4B × /64 | RIPE NCC | 6th Jan 2016 | |
| 2a00:47c0::/32 | 4.3B × /64 | RIPE NCC | 29th Nov 2011 |