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,586 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 103.10.198.0/24 | 256 | APNIC |  HK | 29th Jul 2011 |
| 103.10.199.0/24 | 256 | APNIC | HK | 29th Jul 2011 |
| 103.10.232.0/24 | 256 | APNIC |  AU | 3rd Aug 2011 |
| 103.10.244.0/22 | 1k | APNIC |  JP | 4th Aug 2011 |
| 103.10.40.0/22 | 1k | APNIC |  MY | 23rd May 2011 |
| 103.10.57.0/24 | 256 | APNIC | MY | 19th Jul 2023 |
| 103.100.0.0/22 | 1k | APNIC |  CN | 31st Aug 2017 |
| 103.100.116.0/22 | 1k | APNIC | CN | 6th Sept 2017 |
| 103.100.138.0/23 | 512 | APNIC | HK | 8th Sept 2017 |
| 103.100.144.0/22 | 1k | APNIC | CN | 8th Sept 2017 |
| 103.100.164.0/22 | 1k | APNIC |  TW | 8th Sept 2017 |
| 103.100.194.0/24 | 256 | APNIC | AU | 12th Sept 2017 |
| 103.100.195.0/24 | 256 | APNIC |  ID | 12th Sept 2017 |
| 103.100.236.0/22 | 1k | APNIC | CN | 13th Sept 2017 |
| 103.100.240.0/22 | 1k | APNIC | CN | 13th Sept 2017 |
| 103.100.248.0/22 | 1k | APNIC | CN | 14th Sept 2017 |
| 103.100.252.0/22 | 1k | APNIC | CN | 14th Sept 2017 |
| 103.100.32.0/22 | 1k | APNIC | CN | 4th Sept 2017 |
| 103.100.40.0/22 | 1k | APNIC | CN | 4th Sept 2017 |
| 103.100.46.0/23 | 512 | APNIC | MY | 5th Sept 2017 |
| 103.100.48.0/22 | 1k | APNIC | CN | 4th Sept 2017 |
| 103.100.52.0/22 | 1k | APNIC | CN | 5th Sept 2017 |
| 103.100.56.0/22 | 1k | APNIC | CN | 5th Sept 2017 |
| 103.100.8.0/23 | 512 | APNIC |  IN | 31st Aug 2017 |
| 103.100.85.0/24 | 256 | APNIC | ID | 6th Sept 2017 |
| 103.100.88.0/22 | 1k | APNIC | CN | 6th Sept 2017 |
| 103.101.12.0/22 | 1k | APNIC | CN | 14th Sept 2017 |
| 103.101.120.0/22 | 1k | APNIC | CN | 26th Sept 2017 |
| 103.101.135.0/24 | 256 | APNIC | AU | 26th Sept 2017 |
| 103.101.140.0/23 | 512 | APNIC | ID | 2nd Mar 2023 |
| 103.101.144.0/22 | 1k | APNIC | CN | 27th Sept 2017 |
| 103.101.148.0/22 | 1k | APNIC | CN | 27th Sept 2017 |
| 103.101.154.0/23 | 512 | APNIC | ID | 27th Sept 2017 |
| 103.101.173.0/24 | 256 | APNIC | AU | 28th Sept 2017 |
| 103.101.184.0/22 | 1k | APNIC | CN | 28th Sept 2017 |
| 103.101.20.0/22 | 1k | APNIC | ID | 14th Sept 2017 |
| 103.101.252.0/24 | 256 | APNIC |  NP | 6th Oct 2017 |
| 103.101.60.0/22 | 1k | APNIC | CN | 19th Sept 2017 |
| 103.101.65.0/24 | 256 | APNIC | IN | 30th Nov 2022 |
| 103.101.66.0/23 | 512 | APNIC | ID | 19th Sept 2017 |
| 103.101.72.0/22 | 1k | APNIC | JP | 20th Sept 2017 |
| 103.101.8.0/22 | 1k | APNIC | CN | 14th Sept 2017 |
| 103.101.95.0/24 | 256 | APNIC | ID | 26th Sept 2017 |
| 103.102.106.0/23 | 512 | APNIC | IN | 13th Oct 2017 |
| 103.102.168.0/22 | 1k | APNIC | CN | 19th Oct 2017 |
| 103.102.172.0/22 | 1k | APNIC | CN | 19th Oct 2017 |
| 103.102.180.0/22 | 1k | APNIC | CN | 23rd Oct 2017 |
| 103.102.184.0/22 | 1k | APNIC | CN | 23rd Oct 2017 |
| 103.102.188.0/22 | 1k | APNIC | CN | 23rd Oct 2017 |
| 103.102.192.0/22 | 1k | APNIC | CN | 23rd Oct 2017 |