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 |
|---|---|---|---|---|
| 162.4.168.0/23 | 512 | APNIC |  CN | 22nd May 2026 |
| 162.4.183.0/24 | 256 | APNIC |  ID | 25th May 2026 |
| 162.4.184.0/23 | 512 | APNIC |  PH | 25th May 2026 |
| 162.4.190.0/24 | 256 | APNIC |  DK | 26th May 2026 |
| 162.4.191.0/24 | 256 | APNIC | PH | 26th May 2026 |
| 162.4.198.0/23 | 512 | APNIC | CN | 28th May 2026 |
| 162.4.200.0/23 | 512 | APNIC |  VN | 1st Jun 2026 |
| 162.4.202.0/23 | 512 | APNIC | CN | 1st Jun 2026 |
| 162.4.204.0/23 | 512 | APNIC |  HK | 2nd Jun 2026 |
| 162.4.206.0/24 | 256 | APNIC |  AU | 4th Jun 2026 |
| 162.4.207.0/24 | 256 | APNIC | AU | 5th Jun 2026 |
| 162.4.212.0/23 | 512 | APNIC | ID | 5th Jun 2026 |
| 162.4.230.0/23 | 512 | APNIC | CN | 10th Jun 2026 |
| 162.4.234.0/23 | 512 | APNIC |  IN | 11th Jun 2026 |
| 162.4.238.0/24 | 256 | APNIC |  JP | 12th Jun 2026 |
| 162.4.239.0/24 | 256 | APNIC | ID | 12th Jun 2026 |
| 162.4.242.0/24 | 256 | APNIC | ID | 12th Jun 2026 |
| 162.4.244.0/23 | 512 | APNIC | IN | 12th Jun 2026 |
| 162.4.248.0/23 | 512 | APNIC | PH | 16th Jun 2026 |
| 162.4.254.0/23 | 512 | APNIC | PH | 17th Jun 2026 |
| 162.4.28.0/23 | 512 | APNIC | JP | 22nd Apr 2026 |
| 162.4.30.0/23 | 512 | APNIC | ID | 22nd Apr 2026 |
| 162.4.46.0/24 | 256 | APNIC | ID | 28th Apr 2026 |
| 162.4.47.0/24 | 256 | APNIC | ID | 29th Apr 2026 |
| 162.4.50.0/23 | 512 | APNIC |  KR | 29th Apr 2026 |
| 162.4.54.0/23 | 512 | APNIC | CN | 29th Apr 2026 |
| 162.4.59.0/24 | 256 | APNIC |  BD | 30th Apr 2026 |
| 162.4.60.0/23 | 512 | APNIC | BD | 30th Apr 2026 |
| 162.4.62.0/24 | 256 | APNIC | ID | 30th Apr 2026 |
| 162.4.71.0/24 | 256 | APNIC | ID | 4th May 2026 |
| 162.4.76.0/23 | 512 | APNIC |  SG | 5th May 2026 |
| 162.4.79.0/24 | 256 | APNIC | JP | 5th May 2026 |
| 162.4.8.0/23 | 512 | APNIC | VN | 21st Apr 2026 |
| 162.4.85.0/24 | 256 | APNIC | PH | 7th May 2026 |
| 162.4.90.0/23 | 512 | APNIC | ID | 7th May 2026 |
| 162.4.92.0/24 | 256 | APNIC |  TW | 7th May 2026 |
| 162.4.93.0/24 | 256 | APNIC | IN | 8th May 2026 |
| 162.56.0.0/16 | 65.5k | APNIC | IN | 4th Aug 1992 |
| 163.122.0.0/16 | 65.5k | APNIC | AU | 20th Jul 1992 |
| 163.128.0.0/23 | 512 | APNIC | KR | 3rd Mar 2026 |
| 163.128.102.0/23 | 512 | APNIC | IN | 24th Mar 2026 |
| 163.128.116.0/23 | 512 | APNIC | PH | 25th Mar 2026 |
| 163.128.118.0/24 | 256 | APNIC | JP | 26th Mar 2026 |
| 163.128.119.0/24 | 256 | APNIC | AU | 27th Mar 2026 |
| 163.128.12.0/23 | 512 | APNIC | IN | 5th Mar 2026 |
| 163.128.120.0/23 | 512 | APNIC | TW | 27th Mar 2026 |
| 163.128.129.0/24 | 256 | APNIC | ID | 1st Apr 2026 |
| 163.128.136.0/23 | 512 | APNIC | ID | 1st Apr 2026 |
| 163.128.139.0/24 | 256 | APNIC | ID | 1st Apr 2026 |
| 163.128.152.0/23 | 512 | APNIC | CN | 3rd Apr 2026 |