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 APNIC, largest first.
Unannounced blocks in Vietnam
822 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 2001:df7:5340::/48 | 65.5k × /64 | APNIC | 5th Aug 2026 | |
| 2001:df7:53c0::/48 | 65.5k × /64 | APNIC | 5th Aug 2026 | |
| 2001:df7:56c0::/48 | 65.5k × /64 | APNIC | 7th Aug 2026 | |
| 2001:df7:5740::/48 | 65.5k × /64 | APNIC | 7th Aug 2026 | |
| 2001:df7:7300::/48 | 65.5k × /64 | APNIC | 24th Dec 2018 | |
| 2001:df7:b40::/48 | 65.5k × /64 | APNIC | 19th May 2026 | |
| 2001:df7:ca00::/48 | 65.5k × /64 | APNIC | 12th Jan 2017 | |
| 2001:df7:cc00::/48 | 65.5k × /64 | APNIC | 4th Dec 2015 | |
| 2001:df7:d580::/48 | 65.5k × /64 | APNIC | 19th Oct 2021 | |
| 2001:df7:dc0::/48 | 65.5k × /64 | APNIC | 21st May 2026 | |
| 202.130.36.0/23 | 512 | APNIC | 2nd Apr 2009 | |
| 202.172.4.0/23 | 512 | APNIC | 25th Oct 2006 | |
| 202.181.143.0/24 | 256 | APNIC | 13th Dec 2000 | |
| 202.92.213.0/24 | 256 | APNIC | 13th Dec 2004 | |
| 202.94.88.0/23 | 512 | APNIC | 29th Dec 2010 | |
| 203.119.58.0/23 | 512 | APNIC | 3rd Nov 2008 | |
| 203.160.96.0/21 | 2k | APNIC | 30th Sept 2003 | |
| 203.163.128.0/18 | 16.4k | APNIC | 6th Apr 2011 | |
| 203.176.160.0/21 | 2k | APNIC | 1st Dec 2006 | |
| 203.195.0.0/18 | 16.4k | APNIC | 11th Apr 2011 | |
| 203.79.28.0/24 | 256 | APNIC | 13th Aug 2009 | |
| 203.89.140.0/22 | 1k | APNIC | 15th Apr 2009 | |
| 203.99.248.0/22 | 1k | APNIC | 16th Mar 2007 | |
| 210.79.176.0/23 | 512 | APNIC | 30th Nov 2023 | |
| 218.100.10.0/24 | 256 | APNIC | 17th Sept 2003 | |
| 218.100.14.0/24 | 256 | APNIC | 25th Nov 2003 | |
| 2400:1060::/32 | 4.3B × /64 | APNIC | 7th Oct 2021 | |
| 2400:16a0::/32 | 4.3B × /64 | APNIC | 19th Oct 2021 | |
| 2400:1aa0::/32 | 4.3B × /64 | APNIC | 1st Nov 2021 | |
| 2400:1da0::/32 | 4.3B × /64 | APNIC | 8th Nov 2021 | |
| 2400:3020::/32 | 4.3B × /64 | APNIC | 10th Nov 2021 | |
| 2400:3060::/32 | 4.3B × /64 | APNIC | 10th Nov 2021 | |
| 2400:31e0::/32 | 4.3B × /64 | APNIC | 15th Nov 2021 | |
| 2400:3960::/32 | 4.3B × /64 | APNIC | 30th Nov 2021 | |
| 2400:39a0::/32 | 4.3B × /64 | APNIC | 1st Dec 2021 | |
| 2400:4da0::/32 | 4.3B × /64 | APNIC | 17th Jan 2022 | |
| 2400:4de0::/32 | 4.3B × /64 | APNIC | 17th Jan 2022 | |
| 2400:5360::/32 | 4.3B × /64 | APNIC | 26th Jan 2022 | |
| 2400:5ba0::/32 | 4.3B × /64 | APNIC | 18th Feb 2022 | |
| 2400:69e0::/32 | 4.3B × /64 | APNIC | 30th Mar 2022 | |
| 2400:6ca0::/32 | 4.3B × /64 | APNIC | 7th Apr 2022 | |
| 2400:6f60::/32 | 4.3B × /64 | APNIC | 15th Apr 2022 | |
| 2400:8020::/32 | 4.3B × /64 | APNIC | 21st May 2022 | |
| 2400:82a0::/32 | 4.3B × /64 | APNIC | 30th May 2022 | |
| 2400:8360::/32 | 4.3B × /64 | APNIC | 2nd Jun 2022 | |
| 2400:83a0::/32 | 4.3B × /64 | APNIC | 2nd Jun 2022 | |
| 2400:9b20::/32 | 4.3B × /64 | APNIC | 29th Jul 2022 | |
| 2400:9b40::/32 | 4.3B × /64 | APNIC | 23rd Jan 2017 | |
| 2400:a0e0::/32 | 4.3B × /64 | APNIC | 19th Aug 2022 | |
| 2400:ac60::/32 | 4.3B × /64 | APNIC | 16th Sept 2022 |