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,580 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 160.19.184.0/23 | 512 | APNIC |  ID | 15th May 2024 |
| 160.19.204.0/23 | 512 | APNIC |  VN | 15th May 2024 |
| 160.19.212.0/22 | 1k | APNIC |  CN | 3rd Mar 2016 |
| 160.19.216.0/22 | 1k | APNIC | CN | 3rd Mar 2016 |
| 160.19.220.0/22 | 1k | APNIC |  IN | 3rd Mar 2016 |
| 160.19.34.0/24 | 256 | APNIC | IN | 8th May 2024 |
| 160.19.43.0/24 | 256 | APNIC | IN | 13th May 2024 |
| 160.19.48.0/22 | 1k | APNIC |  HK | 5th Sept 2016 |
| 160.19.58.0/23 | 512 | APNIC | IN | 10th May 2024 |
| 160.19.74.0/23 | 512 | APNIC | IN | 10th May 2024 |
| 160.19.82.0/23 | 512 | APNIC | CN | 14th May 2024 |
| 160.19.87.0/24 | 256 | APNIC | IN | 14th May 2024 |
| 160.19.90.0/23 | 512 | APNIC |  TW | 14th May 2024 |
| 160.191.104.0/23 | 512 | APNIC | CN | 25th Oct 2024 |
| 160.191.110.0/23 | 512 | APNIC | CN | 27th Oct 2024 |
| 160.191.134.0/23 | 512 | APNIC | ID | 29th Oct 2024 |
| 160.191.142.0/23 | 512 | APNIC |  JP | 30th Oct 2024 |
| 160.191.212.0/24 | 256 | APNIC |  BD | 10th Nov 2024 |
| 160.191.216.0/23 | 512 | APNIC | VN | 11th Nov 2024 |
| 160.191.218.0/23 | 512 | APNIC | VN | 11th Nov 2024 |
| 160.191.222.0/23 | 512 | APNIC | VN | 11th Nov 2024 |
| 160.191.23.0/24 | 256 | APNIC | ID | 17th Oct 2024 |
| 160.191.230.0/23 | 512 | APNIC | VN | 12th Nov 2024 |
| 160.191.24.0/23 | 512 | APNIC |  PH | 17th Oct 2024 |
| 160.191.252.0/23 | 512 | APNIC | VN | 13th Nov 2024 |
| 160.191.254.0/23 | 512 | APNIC | VN | 13th Nov 2024 |
| 160.191.30.0/23 | 512 | APNIC | IN | 17th Oct 2024 |
| 160.191.62.0/24 | 256 | APNIC | ID | 22nd Oct 2024 |
| 160.191.67.0/24 | 256 | APNIC | ID | 29th Oct 2024 |
| 160.191.90.0/23 | 512 | APNIC | VN | 24th Oct 2024 |
| 160.191.92.0/23 | 512 | APNIC | VN | 24th Oct 2024 |
| 160.191.94.0/23 | 512 | APNIC | VN | 24th Oct 2024 |
| 160.191.96.0/23 | 512 | APNIC | VN | 24th Oct 2024 |
| 160.191.98.0/23 | 512 | APNIC | VN | 24th Oct 2024 |
| 160.195.0.0/16 | 65.5k | APNIC | JP | 24th Jul 1992 |
| 160.196.0.0/16 | 65.5k | APNIC | JP | 24th Jul 1992 |
| 160.20.121.0/24 | 256 | APNIC | BD | 21st May 2024 |
| 160.20.130.0/23 | 512 | APNIC | CN | 23rd May 2024 |
| 160.20.140.0/23 | 512 | APNIC | JP | 22nd May 2024 |
| 160.20.143.0/24 | 256 | APNIC |  PG | 27th May 2024 |
| 160.20.16.0/23 | 512 | APNIC | CN | 16th May 2024 |
| 160.20.250.0/24 | 256 | APNIC | ID | 30th May 2024 |
| 160.20.48.0/22 | 1k | APNIC | CN | 4th Mar 2016 |
| 160.20.76.0/23 | 512 | APNIC | ID | 16th May 2024 |
| 160.20.78.0/24 | 256 | APNIC | ID | 16th May 2024 |
| 160.201.0.0/16 | 65.5k | APNIC | JP | 27th Jul 1992 |
| 160.202.148.0/22 | 1k | APNIC | CN | 31st Mar 2016 |
| 160.202.176.0/22 | 1k | APNIC |  KR | 1st Apr 2016 |
| 160.202.216.0/22 | 1k | APNIC | CN | 2nd Apr 2016 |
| 160.202.220.0/22 | 1k | APNIC | CN | 2nd Apr 2016 |