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.50.80.0/22 | 1k | APNIC |  NZ | 12th May 1996 |
| 202.51.248.0/22 | 1k | RIPE NCC |  FR | 29th Oct 2015 |
| 202.51.4.0/22 | 1k | APNIC |  JP | 27th Jan 2005 |
| 202.52.131.0/24 | 256 | APNIC |  ID | 15th Jul 2010 |
| 202.52.143.0/24 | 256 | APNIC |  CN | 9th Jun 2016 |
| 202.52.145.0/24 | 256 | APNIC |  AU | 5th Aug 2010 |
| 202.52.151.0/24 | 256 | APNIC | JP | 12th Aug 2010 |
| 202.52.157.0/24 | 256 | APNIC | NZ | 3rd Feb 2017 |
| 202.52.159.0/24 | 256 | APNIC | AU | 20th Aug 2010 |
| 202.52.192.0/20 | 4.1k | APNIC |  HK | 25th Jan 2001 |
| 202.52.2.0/23 | 512 | APNIC |  IN | 27th Apr 2005 |
| 202.52.208.0/20 | 4.1k | APNIC | HK | 18th Dec 2002 |
| 202.52.248.0/22 | 1k | APNIC |  SG | 23rd Feb 1999 |
| 202.52.33.0/24 | 256 | APNIC | CN | 9th Jun 2016 |
| 202.52.34.0/24 | 256 | APNIC | CN | 9th Jun 2016 |
| 202.52.47.0/24 | 256 | APNIC | CN | 9th Jun 2016 |
| 202.52.51.0/24 | 256 | APNIC | SG | 1st Jul 2010 |
| 202.53.131.0/24 | 256 | APNIC |  BD | 28th Mar 2019 |
| 202.53.132.0/24 | 256 | APNIC | BD | 28th Mar 2019 |
| 202.53.140.0/24 | 256 | APNIC | CN | 9th Jun 2016 |
| 202.53.142.0/24 | 256 | APNIC | IN | 7th May 2024 |
| 202.53.143.0/24 | 256 | APNIC | CN | 9th Jun 2016 |
| 202.53.208.0/20 | 4.1k | APNIC | JP | 26th Mar 2004 |
| 202.53.96.0/20 | 4.1k | APNIC | IN | 9th May 2001 |
| 202.56.56.0/24 | 256 | APNIC | IN | 9th Oct 2023 |
| 202.56.58.0/23 | 512 | APNIC | IN | 24th Jul 2009 |
| 202.56.62.0/23 | 512 | APNIC |  NL | 29th Jul 2009 |
| 202.56.8.0/21 | 2k | APNIC | HK | 15th Oct 2004 |
| 202.57.132.0/22 | 1k | APNIC |  TH | 22nd Feb 1999 |
| 202.57.136.0/21 | 2k | APNIC | TH | 22nd Feb 1999 |
| 202.57.144.0/20 | 4.1k | APNIC | TH | 22nd Feb 1999 |
| 202.57.16.0/24 | 256 | APNIC | ID | 7th Jan 2002 |
| 202.57.17.0/24 | 256 | APNIC | ID | 7th Jan 2002 |
| 202.57.18.0/24 | 256 | APNIC | ID | 7th Jan 2002 |
| 202.57.212.0/22 | 1k | APNIC | CN | 6th Nov 2015 |
| 202.57.216.0/22 | 1k | APNIC | CN | 29th Oct 2015 |
| 202.57.220.0/22 | 1k | APNIC | HK | 21st Oct 1999 |
| 202.57.240.0/20 | 4.1k | APNIC | CN | 12th Apr 2011 |
| 202.58.0.0/24 | 256 | APNIC | CN | 14th Apr 2011 |
| 202.58.112.0/22 | 1k | APNIC | CN | 29th Oct 2015 |
| 202.58.122.0/23 | 512 | APNIC | CN | 30th Sept 2025 |
| 202.58.127.0/24 | 256 | APNIC | IN | 25th Mar 2009 |
| 202.58.228.0/24 | 256 | APNIC | IN | 13th Jan 2010 |
| 202.58.28.0/22 | 1k | APNIC | HK | 21st Apr 2004 |
| 202.58.4.0/22 | 1k | APNIC | JP | 8th Apr 2005 |
| 202.59.0.0/24 | 256 | APNIC | CN | 14th Apr 2011 |
| 202.59.1.0/24 | 256 | APNIC | CN | 9th Jun 2016 |
| 202.59.216.0/21 | 2k | APNIC |  KR | 7th Apr 2011 |
| 202.59.229.0/24 | 256 | APNIC | AU | 25th Aug 2010 |
| 202.59.230.0/24 | 256 | APNIC |  BN | 26th Aug 2010 |