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 |
|---|---|---|---|---|
| 36.255.144.0/22 | 1k | APNIC |  KH | 19th Feb 2016 |
| 36.255.160.0/22 | 1k | APNIC |  JP | 22nd Feb 2016 |
| 36.255.172.0/22 | 1k | APNIC |  CN | 22nd Feb 2016 |
| 36.255.176.0/22 | 1k | APNIC | CN | 22nd Feb 2016 |
| 36.255.196.0/22 | 1k | APNIC |  IN | 23rd Feb 2016 |
| 36.255.244.0/24 | 256 | APNIC |  TW | 29th Feb 2016 |
| 36.255.245.0/24 | 256 | APNIC |  PH | 29th Feb 2016 |
| 36.255.246.0/24 | 256 | APNIC | TW | 29th Feb 2016 |
| 36.255.36.0/22 | 1k | APNIC | JP | 11th Feb 2016 |
| 36.3.160.0/19 | 8.2k | APNIC |  SG | 1st Feb 2011 |
| 36.37.0.0/19 | 8.2k | APNIC | CN | 12th Apr 2011 |
| 36.37.36.0/23 | 512 | APNIC | CN | 14th Apr 2011 |
| 36.37.38.0/24 | 256 | APNIC |  AU | 11th Aug 2011 |
| 36.37.39.0/24 | 256 | APNIC | CN | 14th Apr 2011 |
| 36.37.40.0/21 | 2k | APNIC | CN | 12th Apr 2011 |
| 36.37.48.0/20 | 4.1k | APNIC | CN | 12th Apr 2011 |
| 36.50.120.0/23 | 512 | APNIC |  ID | 14th Dec 2023 |
| 36.50.126.0/23 | 512 | APNIC | ID | 15th Dec 2023 |
| 36.50.136.0/23 | 512 | APNIC | ID | 15th Dec 2023 |
| 36.50.16.0/23 | 512 | APNIC |  VN | 27th Nov 2023 |
| 36.50.208.0/23 | 512 | APNIC | VN | 22nd Dec 2023 |
| 36.50.215.0/24 | 256 | APNIC | ID | 22nd Dec 2023 |
| 36.50.216.0/23 | 512 | APNIC | ID | 22nd Dec 2023 |
| 36.50.242.0/23 | 512 | APNIC | ID | 27th Dec 2023 |
| 36.50.244.0/23 | 512 | APNIC | ID | 27th Dec 2023 |
| 36.50.246.0/23 | 512 | APNIC | ID | 28th Dec 2023 |
| 36.50.254.0/23 | 512 | APNIC | CN | 28th Dec 2023 |
| 36.50.28.0/23 | 512 | APNIC | VN | 27th Nov 2023 |
| 36.50.93.0/24 | 256 | APNIC | ID | 13th Dec 2023 |
| 36.52.112.0/21 | 2k | APNIC | JP | 3rd Feb 2011 |
| 36.52.120.0/22 | 1k | APNIC | JP | 3rd Feb 2011 |
| 36.52.124.0/23 | 512 | APNIC | JP | 3rd Feb 2011 |
| 36.52.144.0/21 | 2k | APNIC | JP | 3rd Feb 2011 |
| 36.52.16.0/21 | 2k | APNIC | JP | 3rd Feb 2011 |
| 36.52.168.0/22 | 1k | APNIC | JP | 3rd Feb 2011 |
| 36.52.172.0/23 | 512 | APNIC | JP | 3rd Feb 2011 |
| 36.52.224.0/21 | 2k | APNIC | JP | 3rd Feb 2011 |
| 36.52.232.0/22 | 1k | APNIC | JP | 3rd Feb 2011 |
| 36.52.236.0/23 | 512 | APNIC | JP | 3rd Feb 2011 |
| 36.52.24.0/23 | 512 | APNIC | JP | 3rd Feb 2011 |
| 39.0.0.0/24 | 256 | APNIC | CN | 14th Apr 2011 |
| 39.0.1.0/24 | 256 | APNIC | AU | 2nd Mar 2011 |
| 39.0.128.0/17 | 32.8k | APNIC | CN | 12th Apr 2011 |
| 39.0.16.0/20 | 4.1k | APNIC | CN | 12th Apr 2011 |
| 39.0.2.0/23 | 512 | APNIC | CN | 14th Apr 2011 |
| 39.0.32.0/19 | 8.2k | APNIC | CN | 12th Apr 2011 |
| 39.0.4.0/22 | 1k | APNIC | CN | 14th Apr 2011 |
| 39.0.64.0/18 | 16.4k | APNIC | CN | 12th Apr 2011 |
| 39.0.8.0/21 | 2k | APNIC | CN | 12th Apr 2011 |
| 39.109.124.0/23 | 512 | APNIC |  HK | 5th Apr 2011 |