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,591 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 103.138.11.0/24 | 256 | APNIC |  PK | 9th Apr 2019 |
| 103.138.110.0/23 | 512 | APNIC |  VN | 19th Apr 2019 |
| 103.138.134.0/23 | 512 | APNIC |  CN | 24th Apr 2019 |
| 103.138.2.0/23 | 512 | APNIC | CN | 8th Apr 2019 |
| 103.138.20.0/23 | 512 | APNIC |  IN | 9th Apr 2019 |
| 103.138.208.0/23 | 512 | APNIC | CN | 6th May 2019 |
| 103.138.210.0/24 | 256 | APNIC |  AU | 7th May 2019 |
| 103.138.220.0/23 | 512 | APNIC | CN | 7th May 2019 |
| 103.138.225.0/24 | 256 | APNIC |  KH | 8th May 2019 |
| 103.138.231.0/24 | 256 | APNIC | AU | 8th May 2019 |
| 103.138.246.0/23 | 512 | APNIC |  SG | 9th May 2019 |
| 103.138.248.0/23 | 512 | APNIC | CN | 9th May 2019 |
| 103.138.30.0/23 | 512 | APNIC |  BD | 11th Apr 2019 |
| 103.138.8.0/23 | 512 | APNIC | IN | 8th Apr 2019 |
| 103.138.90.0/23 | 512 | APNIC | VN | 17th Apr 2019 |
| 103.138.97.0/24 | 256 | APNIC |  ID | 18th Apr 2019 |
| 103.138.98.0/23 | 512 | APNIC | IN | 18th Apr 2019 |
| 103.139.120.0/23 | 512 | APNIC | ID | 22nd May 2019 |
| 103.139.134.0/23 | 512 | APNIC | CN | 24th May 2019 |
| 103.139.148.0/22 | 1k | APNIC | BD | 28th May 2019 |
| 103.139.168.0/23 | 512 | APNIC | IN | 29th May 2019 |
| 103.139.176.0/23 | 512 | APNIC | PK | 30th May 2019 |
| 103.139.194.0/24 | 256 | APNIC |  MM | 3rd Jun 2019 |
| 103.139.204.0/23 | 512 | APNIC | CN | 5th Jun 2019 |
| 103.139.208.0/23 | 512 | APNIC | MM | 5th Jun 2019 |
| 103.139.22.0/23 | 512 | APNIC | CN | 13th May 2019 |
| 103.139.233.0/24 | 256 | APNIC | IN | 11th Jun 2019 |
| 103.139.250.0/23 | 512 | APNIC |  JP | 11th Jun 2019 |
| 103.139.54.0/23 | 512 | APNIC | IN | 10th May 2023 |
| 103.139.63.0/24 | 256 | APNIC | AU | 16th May 2019 |
| 103.139.70.0/23 | 512 | APNIC | IN | 16th May 2019 |
| 103.139.76.0/23 | 512 | APNIC | ID | 17th May 2019 |
| 103.139.80.0/24 | 256 | APNIC |  PH | 17th May 2019 |
| 103.139.90.0/24 | 256 | APNIC |  HK | 19th May 2019 |
| 103.139.92.0/23 | 512 | APNIC | CN | 15th Aug 2022 |
| 103.14.108.0/24 | 256 | APNIC | ID | 9th Jul 2012 |
| 103.14.146.0/23 | 512 | APNIC | VN | 17th Nov 2022 |
| 103.14.156.0/22 | 1k | APNIC | CN | 3rd Aug 2012 |
| 103.14.176.0/22 | 1k | APNIC | JP | 6th Aug 2012 |
| 103.14.196.0/22 | 1k | APNIC | IN | 30th Oct 2015 |
| 103.14.228.0/24 | 256 | APNIC | AU | 10th Aug 2012 |
| 103.14.240.0/22 | 1k | APNIC | CN | 13th Aug 2012 |
| 103.14.25.0/24 | 256 | APNIC | AU | 17th Nov 2015 |
| 103.14.64.0/22 | 1k | APNIC | AU | 3rd Jul 2012 |
| 103.14.84.0/22 | 1k | APNIC | CN | 5th Jul 2012 |
| 103.140.100.0/23 | 512 | APNIC | VN | 25th Jun 2019 |
| 103.140.108.0/23 | 512 | APNIC | ID | 25th Jun 2019 |
| 103.140.123.0/24 | 256 | APNIC | PK | 26th Jun 2019 |
| 103.140.135.0/24 | 256 | APNIC | IN | 27th Jun 2019 |
| 103.140.140.0/23 | 512 | APNIC | CN | 27th Jun 2019 |