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 Japan
1,422 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 210.88.48.0/21 | 2k | APNIC |  JP | 22nd Oct 1997 |
| 210.88.64.0/19 | 8.2k | APNIC | JP | 22nd Oct 1997 |
| 210.88.96.0/19 | 8.2k | APNIC | JP | 10th Dec 1998 |
| 210.89.0.0/19 | 8.2k | APNIC | JP | 4th Jul 2001 |
| 210.89.96.0/22 | 1k | APNIC | JP | 6th Aug 2003 |
| 218.100.42.0/24 | 256 | APNIC | JP | 14th Jun 2006 |
| 218.100.5.0/24 | 256 | APNIC | JP | 9th Jul 2003 |
| 218.100.67.0/24 | 256 | APNIC | JP | 11th Nov 2009 |
| 218.100.8.0/24 | 256 | APNIC | JP | 15th Aug 2003 |
| 218.100.9.0/24 | 256 | APNIC | JP | 15th Aug 2003 |
| 218.33.128.0/17 | 32.8k | APNIC | JP | 4th Dec 2003 |
| 219.0.0.0/13 | 524k | APNIC | JP | 31st Oct 2001 |
| 219.73.128.0/17 | 32.8k | APNIC | JP | 23rd Aug 2006 |
| 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.232.162.0/23 | 512 | APNIC | JP | 19th Nov 2004 |
| 220.232.164.0/23 | 512 | APNIC | JP | 19th Nov 2004 |
| 220.232.254.0/24 | 256 | APNIC | JP | 19th Nov 2004 |
| 220.32.0.0/14 | 262k | APNIC | JP | 12th Apr 2002 |
| 220.38.0.0/18 | 16.4k | APNIC | JP | 12th Apr 2002 |
| 220.38.104.0/21 | 2k | APNIC | JP | 12th Apr 2002 |
| 220.38.112.0/20 | 4.1k | APNIC | JP | 12th Apr 2002 |
| 220.38.128.0/17 | 32.8k | APNIC | JP | 12th Apr 2002 |
| 220.38.64.0/19 | 8.2k | APNIC | JP | 12th Apr 2002 |
| 220.38.96.0/21 | 2k | APNIC | JP | 12th Apr 2002 |
| 220.39.0.0/16 | 65.5k | APNIC | JP | 12th Apr 2002 |
| 220.40.0.0/15 | 131k | APNIC | JP | 12th Apr 2002 |