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
85,493 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 202.42.238.0/24 | 256 | APNIC |  JP | 8th Sept 1999 |
| 202.42.50.0/24 | 256 | APNIC | JP | 9th Jul 1999 |
| 202.42.55.0/24 | 256 | APNIC | JP | 9th Jul 1999 |
| 202.42.57.0/24 | 256 | APNIC | JP | 9th Jul 1999 |
| 202.42.58.0/24 | 256 | APNIC | JP | 9th Jul 1999 |
| 202.42.66.0/24 | 256 | APNIC | JP | 9th Jul 1999 |
| 202.42.68.0/23 | 512 | APNIC | JP | 9th Jul 1999 |
| 202.42.71.0/24 | 256 | APNIC | JP | 9th Jul 1999 |
| 202.42.72.0/21 | 2k | APNIC | JP | 9th Jul 1999 |
| 202.42.8.0/21 | 2k | APNIC | JP | 9th Jul 1999 |
| 202.42.80.0/20 | 4.1k | APNIC | JP | 9th Jul 1999 |
| 202.43.0.0/23 | 512 | APNIC |  TH | 6th Jul 2005 |
| 202.43.104.0/22 | 1k | APNIC | JP | 3rd Jun 2009 |
| 202.43.124.0/22 | 1k | APNIC |  HK | 6th Nov 2015 |
| 202.43.144.0/20 | 4.1k | APNIC |  CN | 19th Jul 2005 |
| 202.43.32.0/20 | 4.1k | APNIC | TH | 3rd Nov 2005 |
| 202.43.76.0/22 | 1k | APNIC | CN | 21st May 2009 |
| 202.43.82.0/24 | 256 | APNIC | HK | 29th May 2009 |
| 202.43.88.0/23 | 512 | APNIC |  ID | 29th May 2009 |
| 202.43.91.0/24 | 256 | APNIC |  US | 17th Aug 2016 |
| 202.44.129.0/24 | 256 | APNIC | CN | 14th Apr 2011 |
| 202.44.132.0/23 | 512 | APNIC | CN | 14th Apr 2011 |
| 202.44.146.0/23 | 512 | APNIC | CN | 14th Apr 2011 |
| 202.44.152.0/21 | 2k | APNIC |  AU | 21st Jul 2003 |
| 202.44.16.0/20 | 4.1k | APNIC | CN | 12th Apr 2011 |
| 202.44.48.0/22 | 1k | APNIC | CN | 29th Oct 2015 |
| 202.44.67.0/24 | 256 | APNIC | CN | 14th Apr 2011 |
| 202.44.74.0/24 | 256 | APNIC | CN | 14th Apr 2011 |
| 202.44.96.0/24 | 256 | APNIC | TH | 23rd Mar 2005 |
| 202.44.97.0/24 | 256 | APNIC | CN | 9th Jun 2016 |
| 202.45.0.0/23 | 512 | APNIC | CN | 14th Apr 2011 |
| 202.45.12.0/24 | 256 | APNIC | JP | 21st Jan 2005 |
| 202.45.129.0/24 | 256 | APNIC | JP | 29th Sept 2004 |
| 202.45.13.0/24 | 256 | APNIC | AU | 10th Mar 2005 |
| 202.45.14.0/24 | 256 | APNIC | HK | 27th Aug 2004 |
| 202.45.15.0/24 | 256 | APNIC | CN | 14th Apr 2011 |
| 202.45.150.0/23 | 512 | APNIC | AU | 3rd Jul 2008 |
| 202.45.16.0/20 | 4.1k | APNIC | CN | 12th Apr 2011 |
| 202.45.2.0/24 | 256 | APNIC | CN | 14th Apr 2011 |
| 202.46.128.0/24 | 256 | APNIC | CN | 14th Apr 2011 |
| 202.46.132.0/22 | 1k | APNIC | AU | 15th Jul 2003 |
| 202.46.16.0/23 | 512 | APNIC | CN | 14th Apr 2011 |
| 202.46.18.0/24 | 256 | APNIC | CN | 14th Apr 2011 |
| 202.46.192.0/20 | 4.1k | APNIC |  IN | 11th Oct 2002 |
| 202.46.20.0/23 | 512 | APNIC | CN | 14th Apr 2011 |
| 202.46.208.0/20 | 4.1k | APNIC | IN | 30th Jun 2004 |
| 202.46.96.0/20 | 4.1k | APNIC | ID | 12th Jul 2001 |
| 202.47.100.0/22 | 1k | APNIC | CN | 21st Nov 2015 |
| 202.47.126.0/24 | 256 | APNIC | CN | 14th Apr 2011 |
| 202.47.127.0/24 | 256 | APNIC | IN | 6th Oct 2004 |