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 the most unannounced blocks, largest first.
Unannounced blocks
85,001 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 160.236.112.0/23 | 512 | APNIC |  PK | 17th Jul 2026 |
| 160.236.114.0/23 | 512 | APNIC |  ID | 17th Jul 2026 |
| 160.236.116.0/23 | 512 | APNIC |  JP | 17th Jul 2026 |
| 160.236.120.0/23 | 512 | APNIC |  MY | 20th Jul 2026 |
| 160.236.126.0/23 | 512 | APNIC |  PH | 20th Jul 2026 |
| 160.236.13.0/24 | 256 | APNIC |  AU | 19th Jun 2026 |
| 160.236.130.0/23 | 512 | APNIC |  VN | 21st Jul 2026 |
| 160.236.132.0/23 | 512 | APNIC | ID | 21st Jul 2026 |
| 160.236.140.0/23 | 512 | APNIC | VN | 22nd Jul 2026 |
| 160.236.142.0/24 | 256 | APNIC | ID | 22nd Jul 2026 |
| 160.236.143.0/24 | 256 | APNIC | MY | 22nd Jul 2026 |
| 160.236.148.0/23 | 512 | APNIC |  CN | 23rd Jul 2026 |
| 160.236.150.0/23 | 512 | APNIC |  IN | 24th Jul 2026 |
| 160.236.154.0/23 | 512 | APNIC | ID | 24th Jul 2026 |
| 160.236.160.0/23 | 512 | APNIC | AU | 26th Jul 2026 |
| 160.236.162.0/23 | 512 | APNIC | CN | 27th Jul 2026 |
| 160.236.165.0/24 | 256 | APNIC | ID | 28th Jul 2026 |
| 160.236.168.0/23 | 512 | APNIC | ID | 28th Jul 2026 |
| 160.236.171.0/24 | 256 | APNIC | ID | 28th Jul 2026 |
| 160.236.173.0/24 | 256 | APNIC | ID | 28th Jul 2026 |
| 160.236.174.0/23 | 512 | APNIC | ID | 28th Jul 2026 |
| 160.236.176.0/24 | 256 | APNIC | ID | 28th Jul 2026 |
| 160.236.177.0/24 | 256 | APNIC | ID | 28th Jul 2026 |
| 160.236.179.0/24 | 256 | APNIC | ID | 28th Jul 2026 |
| 160.236.182.0/23 | 512 | APNIC | PH | 28th Jul 2026 |
| 160.236.187.0/24 | 256 | APNIC | ID | 29th Jul 2026 |
| 160.236.190.0/23 | 512 | APNIC | VN | 29th Jul 2026 |
| 160.236.192.0/23 | 512 | APNIC | VN | 30th Jul 2026 |
| 160.236.194.0/24 | 256 | APNIC |  BT | 30th Jul 2026 |
| 160.236.195.0/24 | 256 | APNIC |  TL | 31st Jul 2026 |
| 160.236.196.0/23 | 512 | APNIC | VN | 30th Jul 2026 |
| 160.236.20.0/24 | 256 | APNIC | ID | 22nd Jun 2026 |
| 160.236.200.0/23 | 512 | APNIC | ID | 31st Jul 2026 |
| 160.236.202.0/24 | 256 | APNIC | ID | 31st Jul 2026 |
| 160.236.203.0/24 | 256 | APNIC | ID | 31st Jul 2026 |
| 160.236.204.0/23 | 512 | APNIC | ID | 31st Jul 2026 |
| 160.236.206.0/24 | 256 | APNIC | ID | 31st Jul 2026 |
| 160.236.207.0/24 | 256 | APNIC | ID | 3rd Aug 2026 |
| 160.236.208.0/23 | 512 | APNIC |  MV | 31st Jul 2026 |
| 160.236.212.0/23 | 512 | APNIC | AU | 3rd Aug 2026 |
| 160.236.214.0/23 | 512 | APNIC |  HK | 3rd Aug 2026 |
| 160.236.216.0/24 | 256 | APNIC | ID | 3rd Aug 2026 |
| 160.236.217.0/24 | 256 | APNIC | AU | 4th Aug 2026 |
| 160.236.218.0/23 | 512 | APNIC | ID | 3rd Aug 2026 |
| 160.236.222.0/23 | 512 | APNIC |  NZ | 4th Aug 2026 |
| 160.236.224.0/23 | 512 | APNIC |  TH | 4th Aug 2026 |
| 160.236.226.0/23 | 512 | APNIC | IN | 4th Aug 2026 |
| 160.236.228.0/24 | 256 | APNIC | ID | 5th Aug 2026 |
| 160.236.229.0/24 | 256 | APNIC | ID | 5th Aug 2026 |
| 160.236.230.0/24 | 256 | APNIC |  BD | 5th Aug 2026 |