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 Singapore
552 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 203.152.58.0/24 | 256 | APNIC | 15th Jan 2003 | |
| 203.174.28.0/23 | 512 | APNIC | 9th Apr 2008 | |
| 203.190.176.0/21 | 2k | APNIC | 16th May 2006 | |
| 203.195.125.0/24 | 256 | APNIC | 5th Jun 2008 | |
| 203.20.105.0/24 | 256 | APNIC | 1st Aug 2005 | |
| 203.201.176.0/22 | 1k | APNIC | 27th Jan 2009 | |
| 203.208.22.0/24 | 256 | APNIC | 15th Jun 2006 | |
| 203.211.60.0/22 | 1k | APNIC | 20th Jun 2008 | |
| 203.24.28.0/22 | 1k | APNIC | 20th Feb 1996 | |
| 203.30.168.0/23 | 512 | APNIC | 24th Sept 2007 | |
| 203.30.48.0/23 | 512 | APNIC | 1st Sept 2005 | |
| 203.34.237.0/24 | 256 | APNIC | 22nd Nov 1996 | |
| 203.55.48.0/23 | 512 | APNIC | 3rd Dec 1996 | |
| 203.62.195.0/24 | 256 | APNIC | 19th Jun 2007 | |
| 203.81.32.0/23 | 512 | APNIC | 1st Feb 2001 | |
| 203.81.35.0/24 | 256 | APNIC | 1st Feb 2001 | |
| 203.81.38.0/23 | 512 | APNIC | 1st Feb 2001 | |
| 203.83.250.0/24 | 256 | APNIC | 30th Jan 2007 | |
| 203.84.130.0/23 | 512 | APNIC | 28th Oct 2005 | |
| 209.103.160.0/19 | 8.2k | APNIC | 23rd Feb 2000 | |
| 210.247.128.0/18 | 16.4k | APNIC | 15th Nov 2005 | |
| 213.177.170.0/24 | 256 | RIPE NCC | 15th Oct 2025 | |
| 218.186.0.0/17 | 32.8k | APNIC | 2nd Nov 2001 | |
| 218.186.192.0/18 | 16.4k | APNIC | 17th Apr 2003 | |
| 220.232.0.0/19 | 8.2k | APNIC | 19th Jan 2004 | |
| 221.128.117.0/24 | 256 | APNIC | 8th Oct 2003 | |
| 221.128.80.0/24 | 256 | APNIC | 8th Oct 2003 | |
| 223.130.0.0/22 | 1k | APNIC | 8th Dec 2010 | |
| 2400:1100::/32 | 4.3B × /64 | APNIC | 31st Mar 2011 | |
| 2400:1d00::/32 | 4.3B × /64 | APNIC | 4th Apr 2011 | |
| 2400:3b20::/32 | 4.3B × /64 | APNIC | 6th Dec 2021 | |
| 2400:4680::/32 | 4.3B × /64 | APNIC | 30th Oct 2013 | |
| 2400:6780::/32 | 4.3B × /64 | APNIC | 28th Nov 2013 | |
| 2400:7980::/32 | 4.3B × /64 | APNIC | 16th Dec 2013 | |
| 2400:7e80::/32 | 4.3B × /64 | APNIC | 19th Dec 2013 | |
| 2400:8900::/32 | 4.3B × /64 | APNIC | 28th Apr 2011 | |
| 2400:aa20::/32 | 4.3B × /64 | APNIC | 13th Sept 2022 | |
| 2400:da80::/32 | 4.3B × /64 | APNIC | 7th Apr 2014 | |
| 2400:dea0::/32 | 4.3B × /64 | APNIC | 13th Feb 2023 | |
| 2400:ec80::/32 | 4.3B × /64 | APNIC | 28th Apr 2014 | |
| 2400:f040::/32 | 4.3B × /64 | APNIC | 31st Mar 2017 | |
| 2400:fb80::/32 | 4.3B × /64 | APNIC | 12th May 2014 | |
| 2401:1120::/32 | 4.3B × /64 | APNIC | 29th Jun 2023 | |
| 2401:17e0::/32 | 4.3B × /64 | APNIC | 13th Jul 2023 | |
| 2401:2020::/32 | 4.3B × /64 | APNIC | 3rd Aug 2023 | |
| 2401:22c0::/32 | 4.3B × /64 | APNIC | 12th May 2017 | |
| 2401:26e0::/32 | 4.3B × /64 | APNIC | 15th Aug 2023 | |
| 2401:3460::/32 | 4.3B × /64 | APNIC | 7th Sept 2023 | |
| 2401:3740::/32 | 4.3B × /64 | APNIC | 5th Jun 2017 | |
| 2401:3ec0::/32 | 4.3B × /64 | APNIC | 6th Jun 2017 |