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.106.120.0/22 | 1k | APNIC |  CN | 25th Dec 2017 |
| 103.106.128.0/22 | 1k | APNIC | CN | 26th Dec 2017 |
| 103.106.132.0/22 | 1k | APNIC | CN | 26th Dec 2017 |
| 103.106.16.0/22 | 1k | APNIC |  MY | 15th Dec 2017 |
| 103.106.160.0/22 | 1k | APNIC | CN | 28th Dec 2017 |
| 103.106.182.0/24 | 256 | APNIC |  AF | 29th Dec 2017 |
| 103.106.196.0/22 | 1k | APNIC | CN | 2nd Jan 2018 |
| 103.106.208.0/22 | 1k | APNIC |  HK | 3rd Jan 2018 |
| 103.106.212.0/22 | 1k | APNIC | CN | 4th Jan 2018 |
| 103.106.40.0/22 | 1k | APNIC | CN | 18th Dec 2017 |
| 103.106.44.0/22 | 1k | APNIC | CN | 18th Dec 2017 |
| 103.106.48.0/22 | 1k | APNIC |  JP | 18th Dec 2017 |
| 103.106.60.0/22 | 1k | APNIC | CN | 19th Dec 2017 |
| 103.106.68.0/22 | 1k | APNIC | CN | 20th Dec 2017 |
| 103.106.74.0/23 | 512 | APNIC |  ID | 20th Dec 2017 |
| 103.106.96.0/22 | 1k | APNIC | CN | 21st Dec 2017 |
| 103.107.10.0/23 | 512 | APNIC | HK | 5th Jan 2018 |
| 103.107.108.0/22 | 1k | APNIC | CN | 11th Jan 2018 |
| 103.107.12.0/22 | 1k | APNIC | HK | 5th Jan 2018 |
| 103.107.122.0/24 | 256 | APNIC |  BD | 15th Jan 2018 |
| 103.107.141.0/24 | 256 | APNIC | ID | 15th Jan 2018 |
| 103.107.149.0/24 | 256 | APNIC |  AU | 16th Jan 2018 |
| 103.107.152.0/22 | 1k | APNIC |  PG | 16th Jan 2018 |
| 103.107.164.0/22 | 1k | APNIC | CN | 16th Jan 2018 |
| 103.107.168.0/22 | 1k | APNIC | CN | 16th Jan 2018 |
| 103.107.185.0/24 | 256 | APNIC | AU | 17th Jan 2018 |
| 103.107.188.0/22 | 1k | APNIC | CN | 17th Jan 2018 |
| 103.107.192.0/22 | 1k | APNIC | CN | 17th Jan 2018 |
| 103.107.208.0/22 | 1k | APNIC | CN | 18th Jan 2018 |
| 103.107.212.0/22 | 1k | APNIC | CN | 18th Jan 2018 |
| 103.107.224.0/23 | 512 | APNIC | AU | 19th Jan 2018 |
| 103.107.28.0/22 | 1k | APNIC | CN | 8th Jan 2018 |
| 103.107.32.0/22 | 1k | APNIC | CN | 8th Jan 2018 |
| 103.107.42.0/24 | 256 | APNIC |  SG | 8th Jan 2018 |
| 103.107.44.0/22 | 1k | APNIC | CN | 9th Jan 2018 |
| 103.107.72.0/22 | 1k | APNIC | CN | 10th Jan 2018 |
| 103.108.119.0/24 | 256 | APNIC | ID | 29th Jan 2018 |
| 103.108.160.0/22 | 1k | APNIC | CN | 1st Feb 2018 |
| 103.108.164.0/22 | 1k | APNIC | CN | 1st Feb 2018 |
| 103.108.173.0/24 | 256 | APNIC | ID | 1st Feb 2018 |
| 103.108.196.0/22 | 1k | APNIC | CN | 5th Feb 2018 |
| 103.108.208.0/22 | 1k | APNIC | CN | 5th Feb 2018 |
| 103.108.212.0/22 | 1k | APNIC | CN | 6th Feb 2018 |
| 103.108.216.0/23 | 512 | APNIC | HK | 6th Feb 2018 |
| 103.108.224.0/22 | 1k | APNIC | CN | 7th Feb 2018 |
| 103.108.52.0/22 | 1k | APNIC | CN | 23rd Jan 2018 |
| 103.108.76.0/22 | 1k | APNIC |  IN | 24th Jan 2018 |
| 103.108.83.0/24 | 256 | APNIC | IN | 24th Jan 2018 |
| 103.109.116.0/22 | 1k | APNIC |  LA | 13th Feb 2018 |
| 103.109.149.0/24 | 256 | APNIC | ID | 8th Dec 2022 |