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.140.144.0/23 | 512 | APNIC |  CN | 27th Jun 2019 |
| 103.140.150.0/23 | 512 | APNIC |  PH | 28th Jun 2019 |
| 103.140.168.0/24 | 256 | APNIC |  IN | 1st Jul 2019 |
| 103.140.174.0/23 | 512 | APNIC | IN | 2nd Jul 2019 |
| 103.140.182.0/23 | 512 | APNIC | IN | 2nd Jul 2019 |
| 103.140.184.0/24 | 256 | APNIC |  ID | 8th Jul 2019 |
| 103.140.192.0/23 | 512 | APNIC | CN | 3rd Jul 2019 |
| 103.140.20.0/23 | 512 | APNIC | ID | 14th Jun 2019 |
| 103.140.200.0/23 | 512 | APNIC |  JP | 4th Jul 2019 |
| 103.140.222.0/23 | 512 | APNIC |  AU | 8th Jul 2019 |
| 103.140.230.0/23 | 512 | APNIC | IN | 8th Jul 2019 |
| 103.140.246.0/23 | 512 | APNIC |  LA | 9th Jul 2019 |
| 103.140.33.0/24 | 256 | APNIC | AU | 18th Jun 2019 |
| 103.140.40.0/23 | 512 | APNIC |  VN | 18th Jun 2019 |
| 103.140.48.0/23 | 512 | APNIC | JP | 19th Jun 2019 |
| 103.140.52.0/24 | 256 | APNIC | IN | 19th Jun 2019 |
| 103.140.58.0/23 | 512 | APNIC | AU | 20th Jun 2019 |
| 103.140.6.0/23 | 512 | APNIC |  MY | 13th Jun 2019 |
| 103.140.66.0/23 | 512 | APNIC | ID | 20th Jun 2019 |
| 103.140.80.0/23 | 512 | APNIC | ID | 21st Jun 2019 |
| 103.140.84.0/24 | 256 | APNIC | IN | 24th Jun 2019 |
| 103.140.88.0/23 | 512 | APNIC | ID | 24th Jun 2019 |
| 103.140.96.0/24 | 256 | APNIC | ID | 16th Jan 2023 |
| 103.141.128.0/23 | 512 | APNIC | CN | 24th Jul 2019 |
| 103.141.156.0/23 | 512 | APNIC | ID | 26th Jul 2019 |
| 103.141.162.0/23 | 512 | APNIC | ID | 29th Jul 2019 |
| 103.141.168.0/23 | 512 | APNIC | IN | 29th Jul 2019 |
| 103.141.185.0/24 | 256 | APNIC |  HK | 31st Jul 2019 |
| 103.141.186.0/23 | 512 | APNIC | CN | 31st Jul 2019 |
| 103.141.194.0/23 | 512 | APNIC | ID | 31st Jul 2019 |
| 103.141.213.0/24 | 256 | APNIC | IN | 5th Aug 2019 |
| 103.141.242.0/23 | 512 | APNIC | CN | 8th Aug 2019 |
| 103.141.32.0/24 | 256 | APNIC |  US | 15th Jul 2019 |
| 103.141.40.0/23 | 512 | APNIC | ID | 16th Jul 2019 |
| 103.141.58.0/23 | 512 | APNIC | CN | 18th Jul 2019 |
| 103.141.76.0/24 | 256 | APNIC |  BD | 8th Sept 2023 |
| 103.141.77.0/24 | 256 | APNIC | IN | 22nd Jul 2019 |
| 103.142.122.0/23 | 512 | APNIC | CN | 27th Aug 2019 |
| 103.142.127.0/24 | 256 | APNIC | JP | 27th Aug 2019 |
| 103.142.128.0/23 | 512 | APNIC | CN | 27th Aug 2019 |
| 103.142.154.0/23 | 512 | APNIC | CN | 30th Aug 2019 |
| 103.142.156.0/23 | 512 | APNIC | CN | 30th Aug 2019 |
| 103.142.172.0/23 | 512 | APNIC | CN | 2nd Sept 2019 |
| 103.142.176.0/23 | 512 | APNIC |  TW | 2nd Sept 2019 |
| 103.142.180.0/23 | 512 | APNIC | CN | 2nd Sept 2019 |
| 103.142.182.0/23 | 512 | APNIC | ID | 2nd Sept 2019 |
| 103.142.186.0/23 | 512 | APNIC | CN | 3rd Sept 2019 |
| 103.142.192.0/23 | 512 | APNIC | BD | 4th Sept 2019 |
| 103.142.20.0/24 | 256 | APNIC | ID | 11th Sept 2023 |
| 103.142.204.0/23 | 512 | APNIC | US | 4th Sept 2019 |