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.8.48.0/22 | 1k | APNIC |  JP | 12th Apr 2012 |
| 103.8.60.0/24 | 256 | APNIC |  MN | 13th Apr 2012 |
| 103.8.74.0/23 | 512 | APNIC |  ID | 16th Apr 2012 |
| 103.8.78.0/23 | 512 | APNIC | ID | 16th Apr 2012 |
| 103.8.8.0/22 | 1k | APNIC |  CN | 10th Apr 2012 |
| 103.80.104.0/22 | 1k | APNIC | JP | 29th Nov 2016 |
| 103.80.130.0/24 | 256 | APNIC |  IN | 30th Nov 2016 |
| 103.80.164.0/24 | 256 | APNIC |  AU | 1st Dec 2016 |
| 103.80.176.0/22 | 1k | APNIC | CN | 2nd Dec 2016 |
| 103.80.180.0/22 | 1k | APNIC | CN | 2nd Dec 2016 |
| 103.80.184.0/22 | 1k | APNIC | CN | 2nd Dec 2016 |
| 103.80.192.0/22 | 1k | APNIC | CN | 2nd Dec 2016 |
| 103.80.200.0/22 | 1k | APNIC | CN | 2nd Dec 2016 |
| 103.80.204.0/22 | 1k | APNIC | JP | 5th Dec 2016 |
| 103.80.209.0/24 | 256 | APNIC | AU | 6th Dec 2016 |
| 103.80.212.0/23 | 512 | APNIC | ID | 2nd Feb 2023 |
| 103.80.232.0/22 | 1k | APNIC | CN | 5th Dec 2016 |
| 103.80.250.0/24 | 256 | APNIC | IN | 6th Dec 2016 |
| 103.80.252.0/23 | 512 | APNIC |  HK | 6th Dec 2016 |
| 103.80.44.0/22 | 1k | APNIC | CN | 24th Nov 2016 |
| 103.80.72.0/22 | 1k | APNIC | CN | 28th Nov 2016 |
| 103.81.136.0/24 | 256 | APNIC |  NP | 13th Dec 2016 |
| 103.81.148.0/22 | 1k | APNIC | CN | 13th Dec 2016 |
| 103.81.16.0/22 | 1k | APNIC | CN | 6th Dec 2016 |
| 103.81.161.0/24 | 256 | APNIC | IN | 14th Dec 2022 |
| 103.81.164.0/22 | 1k | APNIC | CN | 14th Dec 2016 |
| 103.81.180.0/24 | 256 | APNIC |  LA | 15th Dec 2016 |
| 103.81.20.0/22 | 1k | APNIC | CN | 6th Dec 2016 |
| 103.81.218.0/24 | 256 | APNIC | ID | 27th Jan 2017 |
| 103.81.232.0/22 | 1k | APNIC | CN | 19th Dec 2016 |
| 103.81.252.0/23 | 512 | APNIC | ID | 5th Feb 2023 |
| 103.81.44.0/22 | 1k | APNIC | CN | 7th Dec 2016 |
| 103.81.52.0/24 | 256 | APNIC | AU | 7th Dec 2016 |
| 103.81.8.0/22 | 1k | APNIC | CN | 6th Dec 2016 |
| 103.81.80.0/22 | 1k | APNIC |  VN | 8th Dec 2016 |
| 103.81.96.0/22 | 1k | APNIC | CN | 9th Dec 2016 |
| 103.82.104.0/22 | 1k | APNIC | CN | 27th Dec 2016 |
| 103.82.112.0/22 | 1k | APNIC | JP | 28th Dec 2016 |
| 103.82.144.0/22 | 1k | APNIC | IN | 28th Dec 2016 |
| 103.82.16.0/22 | 1k | APNIC | HK | 22nd Dec 2016 |
| 103.82.160.0/22 | 1k | RIPE NCC |  AT | 29th Dec 2016 |
| 103.82.206.0/23 | 512 | APNIC | IN | 3rd Jan 2017 |
| 103.82.233.0/24 | 256 | APNIC | ID | 6th Jan 2017 |
| 103.82.236.0/22 | 1k | APNIC | CN | 5th Jan 2017 |
| 103.82.244.0/23 | 512 | APNIC | ID | 6th Jan 2017 |
| 103.82.44.0/23 | 512 | APNIC | IN | 22nd Dec 2016 |
| 103.82.60.0/22 | 1k | APNIC | CN | 23rd Dec 2016 |
| 103.82.66.0/23 | 512 | APNIC | IN | 23rd Dec 2016 |
| 103.82.68.0/22 | 1k | APNIC | CN | 23rd Dec 2016 |
| 103.82.84.0/22 | 1k | APNIC | CN | 26th Dec 2016 |