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,906 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 103.204.236.0/22 | 1k | APNIC |  CN | 22nd Dec 2015 |
| 103.204.24.0/22 | 1k | APNIC | CN | 7th Dec 2015 |
| 103.204.244.0/22 | 1k | APNIC |  BD | 23rd Dec 2015 |
| 103.204.248.0/22 | 1k | APNIC |  NZ | 23rd Dec 2015 |
| 103.204.30.0/23 | 512 | APNIC | BD | 18th May 2023 |
| 103.204.56.0/22 | 1k | APNIC |  JP | 8th Dec 2015 |
| 103.204.88.0/22 | 1k | APNIC | CN | 14th Dec 2015 |
| 103.205.100.0/22 | 1k | APNIC |  VN | 29th Dec 2015 |
| 103.205.108.0/22 | 1k | APNIC | CN | 29th Dec 2015 |
| 103.205.116.0/22 | 1k | APNIC | CN | 30th Dec 2015 |
| 103.205.136.0/22 | 1k | APNIC | CN | 31st Dec 2015 |
| 103.205.144.0/22 | 1k | APNIC |  IN | 1st Jan 2016 |
| 103.205.162.0/24 | 256 | APNIC | CN | 4th Jan 2016 |
| 103.205.186.0/23 | 512 | APNIC |  SG | 6th Jan 2016 |
| 103.205.196.0/22 | 1k | APNIC | CN | 5th Jan 2016 |
| 103.205.20.0/22 | 1k | APNIC |  HK | 23rd Dec 2015 |
| 103.205.200.0/22 | 1k | APNIC | CN | 5th Jan 2016 |
| 103.205.224.0/22 | 1k | APNIC | IN | 7th Jan 2016 |
| 103.205.236.0/22 | 1k | APNIC | CN | 8th Jan 2016 |
| 103.205.248.0/22 | 1k | APNIC | CN | 8th Jan 2016 |
| 103.205.39.0/24 | 256 | APNIC | IN | 29th Dec 2015 |
| 103.205.40.0/22 | 1k | APNIC | CN | 25th Dec 2015 |
| 103.205.44.0/22 | 1k | APNIC | CN | 25th Dec 2015 |
| 103.205.52.0/22 | 1k | APNIC | CN | 28th Dec 2015 |
| 103.206.0.0/22 | 1k | APNIC | CN | 8th Jan 2016 |
| 103.206.120.0/22 | 1k | APNIC | HK | 13th Jan 2016 |
| 103.206.140.0/22 | 1k | APNIC | IN | 14th Jan 2016 |
| 103.206.148.0/22 | 1k | APNIC | CN | 14th Jan 2016 |
| 103.206.174.0/23 | 512 | APNIC | IN | 15th Jan 2016 |
| 103.206.220.0/22 | 1k | APNIC | IN | 19th Jan 2016 |
| 103.206.26.0/23 | 512 | APNIC | IN | 22nd May 2023 |
| 103.206.30.0/23 | 512 | APNIC | SG | 11th Jan 2016 |
| 103.206.44.0/22 | 1k | APNIC | CN | 12th Jan 2016 |
| 103.206.99.0/24 | 256 | APNIC | IN | 14th Jan 2016 |
| 103.207.104.0/22 | 1k | APNIC | CN | 26th Jan 2016 |
| 103.207.124.0/22 | 1k | APNIC | IN | 27th Jan 2016 |
| 103.207.144.0/22 | 1k | APNIC | IN | 27th Jan 2016 |
| 103.207.159.0/24 | 256 | APNIC | HK | 29th Jan 2016 |
| 103.207.184.0/22 | 1k | APNIC | CN | 29th Jan 2016 |
| 103.207.188.0/22 | 1k | APNIC | CN | 29th Jan 2016 |
| 103.207.19.0/24 | 256 | APNIC |  MY | 25th Jan 2016 |
| 103.207.192.0/22 | 1k | APNIC | CN | 29th Jan 2016 |
| 103.207.196.0/22 | 1k | APNIC | CN | 29th Jan 2016 |
| 103.207.20.0/22 | 1k | APNIC | JP | 22nd Jan 2016 |
| 103.207.200.0/22 | 1k | APNIC | CN | 29th Jan 2016 |
| 103.207.204.0/22 | 1k | APNIC | CN | 29th Jan 2016 |
| 103.207.208.0/22 | 1k | APNIC | CN | 29th Jan 2016 |
| 103.207.212.0/22 | 1k | APNIC | CN | 29th Jan 2016 |
| 103.207.216.0/22 | 1k | APNIC | JP | 29th Jan 2016 |
| 103.207.220.0/22 | 1k | APNIC | CN | 29th Jan 2016 |