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 registered through RIPE NCC
24,872 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 2001:8d0::/29 | 34.4B × /64 | RIPE NCC | 2nd Jul 2007 | |
| 2001:928::/32 | 4.3B × /64 | RIPE NCC | 30th Sept 2002 | |
| 2001:958::/32 | 4.3B × /64 | RIPE NCC | 18th Oct 2002 | |
| 2001:960::/32 | 4.3B × /64 | RIPE NCC | 21st Oct 2002 | |
| 2001:988::/32 | 4.3B × /64 | RIPE NCC | 25th Oct 2002 | |
| 2001:990::/32 | 4.3B × /64 | RIPE NCC | 28th Oct 2002 | |
| 2001:a20::/32 | 4.3B × /64 | RIPE NCC | 20th Nov 2002 | |
| 2001:a30::/29 | 34.4B × /64 | RIPE NCC | 27th Nov 2002 | |
| 2001:a50::/32 | 4.3B × /64 | RIPE NCC | 17th Dec 2002 | |
| 2001:a58::/32 | 4.3B × /64 | RIPE NCC | 8th Apr 2009 | |
| 2001:a80::/32 | 4.3B × /64 | RIPE NCC | 10th Jan 2003 | |
| 2001:b40::/32 | 4.3B × /64 | RIPE NCC | 24th Feb 2003 | |
| 201.24.192.0/20 | 4.1k | RIPE NCC | 13th Mar 2025 | |
| 201.24.224.0/20 | 4.1k | RIPE NCC | 13th Mar 2025 | |
| 201.51.64.0/18 | 16.4k | RIPE NCC | 6th Mar 2025 | |
| 201.58.0.0/18 | 16.4k | RIPE NCC | 6th Mar 2025 | |
| 201.58.224.0/19 | 8.2k | RIPE NCC | 13th Mar 2025 | |
| 202.4.187.0/24 | 256 | RIPE NCC | 9th Feb 2016 | |
| 202.51.248.0/22 | 1k | RIPE NCC | 29th Oct 2015 | |
| 202.89.128.0/20 | 4.1k | RIPE NCC | 5th Nov 1999 | |
| 203.12.218.0/24 | 256 | RIPE NCC | 16th Feb 1995 | |
| 203.171.64.0/19 | 8.2k | RIPE NCC | 5th Nov 2004 | |
| 203.30.195.0/24 | 256 | RIPE NCC | 11th Apr 2022 | |
| 203.31.217.0/24 | 256 | RIPE NCC | 25th Sept 1996 | |
| 203.56.162.0/23 | 512 | RIPE NCC | 20th Jan 1997 | |
| 204.137.24.0/23 | 512 | RIPE NCC | 29th Aug 1994 | |
| 204.152.98.0/24 | 256 | RIPE NCC | 12th Nov 1996 | |
| 204.48.32.0/23 | 512 | RIPE NCC | 7th Nov 2019 | |
| 204.57.218.0/24 | 256 | RIPE NCC | 18th Jul 1994 | |
| 204.62.218.0/24 | 256 | RIPE NCC | 10th Aug 1994 | |
| 205.132.144.0/21 | 2k | RIPE NCC | 2nd May 1995 | |
| 205.132.48.0/21 | 2k | RIPE NCC | 30th Sept 2008 | |
| 205.178.176.0/24 | 256 | RIPE NCC | 30th Mar 2021 | |
| 205.201.55.0/24 | 256 | RIPE NCC | 31st Mar 1995 | |
| 205.209.28.0/24 | 256 | RIPE NCC | 2nd Mar 2017 | |
| 205.210.40.0/24 | 256 | RIPE NCC | 8th Apr 1995 | |
| 205.220.225.0/24 | 256 | RIPE NCC | 30th Oct 2018 | |
| 205.220.226.0/24 | 256 | RIPE NCC | 30th Oct 2018 | |
| 206.196.125.0/24 | 256 | RIPE NCC | 19th Jul 1995 | |
| 206.245.160.0/22 | 1k | RIPE NCC | 29th Dec 1995 | |
| 206.245.208.0/22 | 1k | RIPE NCC | 10th Apr 1996 | |
| 206.245.216.0/21 | 2k | RIPE NCC | 10th Apr 1996 | |
| 206.245.224.0/19 | 8.2k | RIPE NCC | 10th Apr 1996 | |
| 207.207.206.0/24 | 256 | RIPE NCC | 14th Oct 1996 | |
| 207.207.222.0/24 | 256 | RIPE NCC | 14th Oct 1996 | |
| 207.229.116.0/24 | 256 | RIPE NCC | 30th Dec 1996 | |
| 207.229.122.0/24 | 256 | RIPE NCC | 30th Dec 1996 | |
| 207.229.64.0/24 | 256 | RIPE NCC | 30th Dec 1996 | |
| 208.116.3.0/24 | 256 | RIPE NCC | 19th Apr 2006 | |
| 208.116.4.0/24 | 256 | RIPE NCC | 19th Apr 2006 |