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,593 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 103.241.12.0/22 | 1k | APNIC |  CN | 23rd Aug 2013 |
| 103.241.132.0/22 | 1k | APNIC |  IN | 2nd Sept 2013 |
| 103.241.152.0/22 | 1k | APNIC |  JP | 3rd Sept 2013 |
| 103.241.160.0/22 | 1k | APNIC | CN | 3rd Sept 2013 |
| 103.241.172.0/23 | 512 | APNIC | CN | 24th Jul 2023 |
| 103.241.184.0/22 | 1k | APNIC | CN | 4th Sept 2013 |
| 103.241.188.0/22 | 1k | APNIC | CN | 4th Sept 2013 |
| 103.241.68.0/22 | 1k | APNIC |  TW | 27th Aug 2013 |
| 103.241.96.0/22 | 1k | APNIC | CN | 29th Aug 2013 |
| 103.242.144.0/22 | 1k | APNIC |  TH | 20th Sept 2013 |
| 103.242.160.0/22 | 1k | APNIC | CN | 22nd Sept 2013 |
| 103.242.176.0/22 | 1k | APNIC | CN | 23rd Sept 2013 |
| 103.242.200.0/22 | 1k | APNIC | CN | 24th Sept 2013 |
| 103.242.208.0/23 | 512 | APNIC |  ID | 25th Sept 2013 |
| 103.242.220.0/22 | 1k | APNIC | CN | 26th Sept 2013 |
| 103.242.240.0/22 | 1k | APNIC | CN | 29th Sept 2013 |
| 103.242.252.0/22 | 1k | APNIC | JP | 30th Sept 2013 |
| 103.242.64.0/22 | 1k | APNIC | CN | 12th Sept 2013 |
| 103.243.104.0/22 | 1k | APNIC |  VN | 10th Oct 2013 |
| 103.243.108.0/23 | 512 | APNIC | ID | 10th Oct 2013 |
| 103.243.12.0/22 | 1k | APNIC |  SG | 2nd Oct 2013 |
| 103.243.120.0/22 | 1k | APNIC | JP | 11th Oct 2013 |
| 103.243.208.0/22 | 1k | APNIC | JP | 17th Oct 2013 |
| 103.243.236.0/24 | 256 | APNIC | IN | 18th Oct 2013 |
| 103.243.248.0/22 | 1k | APNIC | TW | 21st Oct 2013 |
| 103.243.36.0/22 | 1k | APNIC | IN | 4th Oct 2013 |
| 103.244.100.0/22 | 1k | APNIC | SG | 13th Dec 2012 |
| 103.244.16.0/22 | 1k | APNIC | CN | 6th Dec 2012 |
| 103.244.160.0/23 | 512 | APNIC | ID | 18th Dec 2012 |
| 103.244.164.0/22 | 1k | APNIC | CN | 19th Dec 2012 |
| 103.244.184.0/22 | 1k | APNIC |  BD | 20th Dec 2012 |
| 103.244.20.0/23 | 512 | APNIC | IN | 27th Jul 2023 |
| 103.244.22.0/24 | 256 | APNIC | IN | 27th Jul 2023 |
| 103.244.24.0/23 | 512 | APNIC | IN | 27th Jul 2023 |
| 103.244.252.0/22 | 1k | APNIC | CN | 28th Dec 2012 |
| 103.244.26.0/23 | 512 | APNIC | CN | 28th Jul 2023 |
| 103.244.48.0/24 | 256 | APNIC | IN | 11th Dec 2012 |
| 103.244.50.0/24 | 256 | APNIC |  NZ | 24th Jan 2013 |
| 103.244.51.0/24 | 256 | APNIC | ID | 18th Dec 2012 |
| 103.244.60.0/22 | 1k | APNIC | CN | 11th Dec 2012 |
| 103.244.68.0/22 | 1k | APNIC | CN | 11th Dec 2012 |
| 103.244.72.0/22 | 1k | APNIC | CN | 11th Dec 2012 |
| 103.244.76.0/22 | 1k | APNIC | CN | 12th Dec 2012 |
| 103.244.84.0/22 | 1k | APNIC | CN | 12th Dec 2012 |
| 103.244.94.0/23 | 512 | APNIC | IN | 28th Jul 2023 |
| 103.245.120.0/23 | 512 | APNIC |  MY | 11th Jan 2013 |
| 103.245.124.0/22 | 1k | APNIC | CN | 11th Jan 2013 |
| 103.245.146.0/24 | 256 | APNIC |  AU | 17th Jan 2013 |
| 103.245.167.0/24 | 256 | APNIC |  LA | 18th Jan 2013 |
| 103.245.168.0/23 | 512 | APNIC | ID | 1st Aug 2023 |