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,960 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 103.83.112.0/22 | 1k | APNIC |  CN | 16th Jan 2017 |
| 103.83.150.0/24 | 256 | APNIC |  IN | 17th Jan 2017 |
| 103.83.160.0/24 | 256 | APNIC |  SG | 18th Jan 2017 |
| 103.83.199.0/24 | 256 | APNIC | IN | 20th Jan 2017 |
| 103.83.48.0/22 | 1k | APNIC |  ID | 11th Jan 2017 |
| 103.83.52.0/22 | 1k | APNIC | CN | 11th Jan 2017 |
| 103.83.60.0/22 | 1k | APNIC | CN | 12th Jan 2017 |
| 103.83.68.0/22 | 1k | APNIC | IN | 12th Jan 2017 |
| 103.83.81.0/24 | 256 | APNIC | IN | 12th Jan 2017 |
| 103.84.0.0/22 | 1k | APNIC | CN | 20th Jan 2017 |
| 103.84.102.0/23 | 512 | APNIC |  VN | 10th Feb 2023 |
| 103.84.118.0/24 | 256 | APNIC | ID | 26th Jan 2017 |
| 103.84.12.0/22 | 1k | APNIC | CN | 22nd Jan 2017 |
| 103.84.16.0/22 | 1k | APNIC | CN | 22nd Jan 2017 |
| 103.84.167.0/24 | 256 | APNIC |  JP | 31st Jan 2017 |
| 103.84.170.0/23 | 512 | APNIC | CN | 12th Feb 2023 |
| 103.84.180.0/22 | 1k | APNIC |  AU | 31st Jan 2017 |
| 103.84.196.0/23 | 512 | APNIC | IN | 13th Feb 2023 |
| 103.84.20.0/22 | 1k | APNIC | CN | 22nd Jan 2017 |
| 103.84.24.0/22 | 1k | APNIC | CN | 22nd Jan 2017 |
| 103.84.248.0/24 | 256 | APNIC | AU | 3rd Apr 2017 |
| 103.84.28.0/22 | 1k | APNIC | CN | 22nd Jan 2017 |
| 103.84.48.0/22 | 1k | APNIC | CN | 23rd Jan 2017 |
| 103.84.64.0/22 | 1k | APNIC | CN | 23rd Jan 2017 |
| 103.84.72.0/22 | 1k | APNIC | CN | 23rd Jan 2017 |
| 103.84.98.0/24 | 256 | APNIC | AU | 24th Jan 2017 |
| 103.85.136.0/22 | 1k | APNIC | CN | 10th Feb 2017 |
| 103.85.154.0/24 | 256 | APNIC | IN | 14th Feb 2017 |
| 103.85.186.0/23 | 512 | APNIC | CN | 15th Feb 2023 |
| 103.85.200.0/22 | 1k | APNIC |  HK | 14th Feb 2017 |
| 103.85.214.0/23 | 512 | APNIC | AU | 16th Feb 2017 |
| 103.85.44.0/22 | 1k | APNIC | CN | 6th Feb 2017 |
| 103.85.48.0/22 | 1k | APNIC | CN | 6th Feb 2017 |
| 103.86.140.0/22 | 1k | APNIC | ID | 24th Feb 2017 |
| 103.86.164.0/22 | 1k | APNIC | IN | 27th Feb 2017 |
| 103.86.168.0/22 | 1k | APNIC | AU | 28th Feb 2017 |
| 103.86.20.0/22 | 1k | APNIC | IN | 16th Feb 2017 |
| 103.86.204.0/22 | 1k | APNIC | CN | 2nd Mar 2017 |
| 103.86.208.0/22 | 1k | APNIC | CN | 2nd Mar 2017 |
| 103.86.212.0/22 | 1k | APNIC | CN | 2nd Mar 2017 |
| 103.86.216.0/22 | 1k | APNIC | CN | 2nd Mar 2017 |
| 103.86.220.0/22 | 1k | APNIC | CN | 2nd Mar 2017 |
| 103.86.224.0/22 | 1k | APNIC | CN | 2nd Mar 2017 |
| 103.86.228.0/22 | 1k | APNIC | CN | 2nd Mar 2017 |
| 103.86.232.0/22 | 1k | APNIC | CN | 2nd Mar 2017 |
| 103.86.236.0/22 | 1k | APNIC | CN | 2nd Mar 2017 |
| 103.86.240.0/22 | 1k | APNIC | CN | 2nd Mar 2017 |
| 103.86.244.0/22 | 1k | APNIC | CN | 2nd Mar 2017 |
| 103.86.248.0/22 | 1k | APNIC | CN | 2nd Mar 2017 |
| 103.86.252.0/22 | 1k | APNIC | CN | 2nd Mar 2017 |