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,580 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 175.103.130.0/23 | 512 | APNIC |  JP | 4th Jan 2010 |
| 175.103.132.0/23 | 512 | APNIC | JP | 4th Jan 2010 |
| 175.103.134.0/23 | 512 | APNIC | JP | 4th Jan 2010 |
| 175.103.136.0/21 | 2k | APNIC | JP | 4th Jan 2010 |
| 175.103.152.0/22 | 1k | APNIC | JP | 4th Jan 2010 |
| 175.103.156.0/23 | 512 | APNIC | JP | 4th Jan 2010 |
| 175.103.158.0/24 | 256 | APNIC | JP | 4th Jan 2010 |
| 175.103.159.0/24 | 256 | APNIC | JP | 4th Jan 2010 |
| 175.103.160.0/22 | 1k | APNIC | JP | 4th Jan 2010 |
| 175.103.166.0/23 | 512 | APNIC | JP | 4th Jan 2010 |
| 175.103.168.0/22 | 1k | APNIC | JP | 4th Jan 2010 |
| 175.103.172.0/23 | 512 | APNIC | JP | 4th Jan 2010 |
| 175.103.174.0/23 | 512 | APNIC | JP | 4th Jan 2010 |
| 175.103.178.0/23 | 512 | APNIC | JP | 4th Jan 2010 |
| 175.103.192.0/20 | 4.1k | APNIC | JP | 4th Jan 2010 |
| 175.103.208.0/21 | 2k | APNIC | JP | 4th Jan 2010 |
| 175.103.4.0/22 | 1k | APNIC | JP | 4th Jan 2010 |
| 175.103.64.0/18 | 16.4k | APNIC |  VN | 11th Apr 2011 |
| 175.106.128.0/17 | 32.8k | APNIC |  CN | 5th Jan 2010 |
| 175.106.28.0/22 | 1k | APNIC |  AU | 15th Feb 2011 |
| 175.107.64.0/18 | 16.4k | APNIC |  KR | 12th Jan 2010 |
| 175.111.104.0/22 | 1k | APNIC |  SG | 14th Jan 2010 |
| 175.111.144.0/22 | 1k | APNIC | CN | 29th Jan 2016 |
| 175.111.148.0/22 | 1k | APNIC | CN | 29th Jan 2016 |
| 175.111.152.0/22 | 1k | APNIC | CN | 29th Jan 2016 |
| 175.111.156.0/22 | 1k | APNIC | CN | 29th Jan 2016 |
| 175.111.160.0/22 | 1k | APNIC | CN | 29th Jan 2016 |
| 175.111.164.0/22 | 1k | APNIC | CN | 29th Jan 2016 |
| 175.111.168.0/22 | 1k | APNIC | CN | 29th Jan 2016 |
| 175.111.172.0/22 | 1k | APNIC | CN | 29th Jan 2016 |
| 175.111.184.0/22 | 1k | APNIC | CN | 29th Jan 2016 |
| 175.111.32.0/19 | 8.2k | APNIC |  TW | 13th Jan 2010 |
| 175.111.98.0/23 | 512 | APNIC |  ID | 13th Oct 2023 |
| 175.158.96.0/22 | 1k | APNIC | CN | 19th Nov 2015 |
| 175.176.152.0/22 | 1k | APNIC |  HK | 19th Nov 2015 |
| 175.176.156.0/22 | 1k | APNIC | CN | 19th Nov 2015 |
| 175.176.176.0/22 | 1k | APNIC | CN | 30th Nov 2015 |
| 175.176.188.0/22 | 1k | APNIC | CN | 1st Dec 2015 |
| 175.176.224.0/19 | 8.2k | APNIC | SG | 28th Jan 2010 |
| 175.179.64.0/19 | 8.2k | APNIC | JP | 27th Jan 2010 |
| 175.184.200.0/21 | 2k | APNIC | AU | 29th Jan 2010 |
| 175.184.208.0/21 | 2k | APNIC | AU | 29th Jan 2010 |
| 175.26.0.0/16 | 65.5k | APNIC | CN | 4th Dec 2009 |
| 175.28.63.0/24 | 256 | APNIC | JP | 11th Dec 2009 |
| 175.40.0.0/16 | 65.5k | APNIC |  IN | 11th Dec 2009 |
| 175.45.240.0/20 | 4.1k | APNIC | KR | 21st Dec 2009 |
| 175.48.0.0/12 | 1M | APNIC | CN | 14th Dec 2009 |
| 175.64.0.0/11 | 2.1M | APNIC | CN | 14th Dec 2009 |
| 177.203.80.0/20 | 4.1k | APNIC | IN | 13th Mar 2025 |
| 177.4.96.0/20 | 4.1k | APNIC | IN | 13th Mar 2025 |