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 registered through APNIC
22,595 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 218.100.8.0/24 | 256 | APNIC |  JP | 15th Aug 2003 |
| 218.100.85.0/24 | 256 | APNIC |  PK | 26th Jan 2011 |
| 218.100.9.0/24 | 256 | APNIC | JP | 15th Aug 2003 |
| 218.100.96.0/19 | 8.2k | APNIC |  CN | 12th Apr 2011 |
| 218.185.0.0/17 | 32.8k | APNIC |  AU | 25th Oct 2001 |
| 218.185.192.0/19 | 8.2k | APNIC | CN | 19th Oct 2004 |
| 218.214.0.0/16 | 65.5k | APNIC | AU | 19th Jun 2003 |
| 218.215.0.0/16 | 65.5k | APNIC | AU | 21st Jan 2005 |
| 218.244.64.0/19 | 8.2k | APNIC | CN | 30th Nov 2001 |
| 218.244.96.0/19 | 8.2k | APNIC | CN | 30th Nov 2001 |
| 218.33.128.0/17 | 32.8k | APNIC | JP | 4th Dec 2003 |
| 218.98.224.0/19 | 8.2k | APNIC | CN | 22nd Jun 2001 |
| 218.99.0.0/16 | 65.5k | APNIC | CN | 22nd Jun 2001 |
| 219.0.0.0/13 | 524k | APNIC | JP | 31st Oct 2001 |
| 219.151.64.0/18 | 16.4k | APNIC | CN | 21st Mar 2002 |
| 219.73.128.0/17 | 32.8k | APNIC | JP | 23rd Aug 2006 |
| 219.90.68.0/22 | 1k | APNIC | CN | 26th Nov 2015 |
| 219.90.72.0/22 | 1k | APNIC | CN | 26th Nov 2015 |
| 219.90.76.0/22 | 1k | APNIC | CN | 26th Nov 2015 |
| 220.101.128.0/18 | 16.4k | APNIC | AU | 28th Jan 2004 |
| 220.145.0.0/17 | 32.8k | APNIC | JP | 28th Nov 2002 |
| 220.145.128.0/18 | 16.4k | APNIC | JP | 28th Nov 2002 |
| 220.150.18.0/24 | 256 | APNIC | JP | 22nd Jan 2004 |
| 220.150.200.0/24 | 256 | APNIC | JP | 22nd Jan 2004 |
| 220.150.201.0/24 | 256 | APNIC | JP | 22nd Jan 2004 |
| 220.150.202.0/23 | 512 | APNIC | JP | 22nd Jan 2004 |
| 220.150.204.0/24 | 256 | APNIC | JP | 22nd Jan 2004 |
| 220.150.205.0/24 | 256 | APNIC | JP | 22nd Jan 2004 |
| 220.150.206.0/23 | 512 | APNIC | JP | 22nd Jan 2004 |
| 220.150.218.0/23 | 512 | APNIC | JP | 22nd Jan 2004 |
| 220.150.220.0/23 | 512 | APNIC | JP | 22nd Jan 2004 |
| 220.150.222.0/24 | 256 | APNIC | JP | 22nd Jan 2004 |
| 220.150.32.0/22 | 1k | APNIC | JP | 22nd Jan 2004 |
| 220.150.36.0/23 | 512 | APNIC | JP | 22nd Jan 2004 |
| 220.150.38.0/24 | 256 | APNIC | JP | 22nd Jan 2004 |
| 220.150.39.0/24 | 256 | APNIC | JP | 22nd Jan 2004 |
| 220.150.40.0/22 | 1k | APNIC | JP | 22nd Jan 2004 |
| 220.150.44.0/23 | 512 | APNIC | JP | 22nd Jan 2004 |
| 220.150.46.0/24 | 256 | APNIC | JP | 22nd Jan 2004 |
| 220.150.47.0/24 | 256 | APNIC | JP | 22nd Jan 2004 |
| 220.150.65.0/24 | 256 | APNIC | JP | 22nd Jan 2004 |
| 220.150.80.0/23 | 512 | APNIC | JP | 22nd Jan 2004 |
| 220.150.82.0/24 | 256 | APNIC | JP | 22nd Jan 2004 |
| 220.150.84.0/22 | 1k | APNIC | JP | 22nd Jan 2004 |
| 220.150.88.0/24 | 256 | APNIC | JP | 22nd Jan 2004 |
| 220.152.128.0/17 | 32.8k | APNIC | CN | 25th Aug 2006 |
| 220.155.0.0/16 | 65.5k | APNIC | CN | 16th Aug 2006 |
| 220.157.96.0/20 | 4.1k | APNIC |  ID | 11th Sept 2006 |
| 220.158.152.0/22 | 1k | APNIC |  IN | 6th Oct 2015 |
| 220.158.188.0/22 | 1k | APNIC | AU | 6th Oct 2015 |