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
84,778 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 103.142.64.0/23 | 512 | APNIC |  IN | 19th Aug 2019 |
| 103.142.82.0/23 | 512 | APNIC |  CN | 21st Aug 2019 |
| 103.142.84.0/23 | 512 | APNIC |  HK | 21st Aug 2019 |
| 103.142.92.0/23 | 512 | APNIC |  ID | 21st Aug 2019 |
| 103.143.102.0/23 | 512 | APNIC | ID | 20th Sept 2019 |
| 103.143.110.0/23 | 512 | APNIC | ID | 23rd Sept 2019 |
| 103.143.114.0/23 | 512 | APNIC | ID | 23rd Sept 2019 |
| 103.143.116.0/23 | 512 | APNIC | ID | 23rd Sept 2019 |
| 103.143.124.0/23 | 512 | APNIC | CN | 24th Sept 2019 |
| 103.143.132.0/23 | 512 | APNIC | CN | 24th Sept 2019 |
| 103.143.134.0/23 | 512 | APNIC | CN | 25th Sept 2019 |
| 103.143.158.0/23 | 512 | APNIC | HK | 27th Sept 2019 |
| 103.143.174.0/23 | 512 | APNIC | CN | 30th Sept 2019 |
| 103.143.188.0/23 | 512 | APNIC | ID | 2nd Oct 2019 |
| 103.143.190.0/23 | 512 | APNIC | ID | 2nd Oct 2019 |
| 103.143.198.0/23 | 512 | APNIC | ID | 2nd Oct 2019 |
| 103.143.215.0/24 | 256 | APNIC | IN | 3rd Oct 2019 |
| 103.143.220.0/23 | 512 | APNIC | ID | 7th Oct 2019 |
| 103.143.24.0/23 | 512 | APNIC | ID | 12th Sept 2019 |
| 103.143.30.0/24 | 256 | APNIC |  US | 13th Sept 2019 |
| 103.143.36.0/23 | 512 | APNIC | IN | 13th Sept 2019 |
| 103.143.58.0/23 | 512 | APNIC | ID | 16th Sept 2019 |
| 103.143.60.0/23 | 512 | APNIC |  AU | 17th Sept 2019 |
| 103.143.64.0/23 | 512 | APNIC | ID | 17th Sept 2019 |
| 103.143.66.0/23 | 512 | APNIC | ID | 17th Sept 2019 |
| 103.143.74.0/23 | 512 | APNIC | CN | 18th Sept 2019 |
| 103.144.0.0/23 | 512 | APNIC |  PH | 10th Oct 2019 |
| 103.144.112.0/23 | 512 | APNIC | IN | 22nd Oct 2019 |
| 103.144.136.0/23 | 512 | APNIC | CN | 24th Oct 2019 |
| 103.144.138.0/24 | 256 | APNIC | ID | 24th Oct 2019 |
| 103.144.154.0/23 | 512 | APNIC |  VN | 28th Oct 2019 |
| 103.144.16.0/23 | 512 | APNIC | ID | 11th Oct 2019 |
| 103.144.224.0/23 | 512 | APNIC |  MM | 5th Nov 2019 |
| 103.144.24.0/23 | 512 | APNIC | IN | 11th Oct 2019 |
| 103.144.46.0/23 | 512 | APNIC | ID | 15th Oct 2019 |
| 103.144.62.0/23 | 512 | APNIC | IN | 17th Aug 2022 |
| 103.144.72.0/23 | 512 | APNIC | CN | 17th Oct 2019 |
| 103.145.102.0/23 | 512 | APNIC |  BD | 20th Nov 2019 |
| 103.145.124.0/24 | 256 | APNIC | ID | 23rd Nov 2019 |
| 103.145.157.0/24 | 256 | APNIC | AU | 26th Nov 2019 |
| 103.145.159.0/24 | 256 | APNIC | PH | 26th Nov 2019 |
| 103.145.170.0/23 | 512 | APNIC | IN | 26th Nov 2019 |
| 103.145.188.0/23 | 512 | APNIC | CN | 27th Nov 2019 |
| 103.145.200.0/23 | 512 | APNIC | ID | 28th Nov 2019 |
| 103.145.250.0/23 | 512 | APNIC | VN | 2nd Dec 2019 |
| 103.145.40.0/23 | 512 | RIPE NCC | HK | 9th Nov 2019 |
| 103.145.80.0/23 | 512 | RIPE NCC | HK | 15th Nov 2019 |
| 103.145.89.0/24 | 256 | APNIC | IN | 18th Nov 2019 |
| 103.145.98.0/23 | 512 | APNIC | CN | 18th Nov 2019 |
| 103.146.107.0/24 | 256 | APNIC | IN | 11th Dec 2019 |