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.135.148.0/22 | 1k | APNIC |  CN | 27th Feb 2019 |
| 103.135.156.0/22 | 1k | APNIC | CN | 27th Feb 2019 |
| 103.135.16.0/22 | 1k | APNIC |  TW | 20th Feb 2019 |
| 103.135.176.0/22 | 1k | APNIC | CN | 28th Feb 2019 |
| 103.135.184.0/22 | 1k | APNIC | CN | 28th Feb 2019 |
| 103.135.200.0/22 | 1k | APNIC |  IN | 28th Feb 2019 |
| 103.135.236.0/22 | 1k | APNIC | CN | 4th Mar 2019 |
| 103.135.37.0/24 | 256 | APNIC |  MM | 21st Feb 2019 |
| 103.135.68.0/23 | 512 | APNIC |  ID | 21st Feb 2019 |
| 103.135.80.0/22 | 1k | APNIC | CN | 22nd Feb 2019 |
| 103.135.92.0/23 | 512 | APNIC | IN | 22nd Feb 2019 |
| 103.136.100.0/22 | 1k | APNIC |  AU | 7th Mar 2019 |
| 103.136.128.0/22 | 1k | APNIC | CN | 8th Mar 2019 |
| 103.136.132.0/22 | 1k | APNIC | MM | 8th Mar 2019 |
| 103.136.140.0/24 | 256 | APNIC | AU | 11th Mar 2019 |
| 103.136.152.0/22 | 1k | APNIC |  JP | 11th Mar 2019 |
| 103.136.188.0/24 | 256 | APNIC | IN | 12th Mar 2019 |
| 103.136.209.0/24 | 256 | APNIC | IN | 13th Mar 2019 |
| 103.136.219.0/24 | 256 | APNIC | ID | 14th Mar 2019 |
| 103.136.228.0/23 | 512 | APNIC |  VN | 14th Mar 2019 |
| 103.136.232.0/22 | 1k | APNIC | CN | 14th Mar 2019 |
| 103.136.81.0/24 | 256 | APNIC | ID | 6th Mar 2019 |
| 103.137.100.0/22 | 1k | APNIC | IN | 25th Mar 2019 |
| 103.137.104.0/23 | 512 | APNIC |  MY | 26th Mar 2019 |
| 103.137.118.0/24 | 256 | APNIC | AU | 27th Mar 2019 |
| 103.137.136.0/23 | 512 | APNIC | CN | 28th Mar 2019 |
| 103.137.138.0/24 | 256 | APNIC | IN | 28th Mar 2019 |
| 103.137.146.0/23 | 512 | APNIC | ID | 28th Mar 2019 |
| 103.137.166.0/23 | 512 | APNIC | ID | 11th Aug 2022 |
| 103.137.172.0/24 | 256 | APNIC | IN | 1st Apr 2019 |
| 103.137.180.0/22 | 1k | APNIC | CN | 2nd Apr 2019 |
| 103.137.219.0/24 | 256 | APNIC | IN | 5th Apr 2019 |
| 103.137.220.0/22 | 1k | APNIC |  PH | 5th Apr 2019 |
| 103.137.236.0/22 | 1k | APNIC | CN | 5th Apr 2019 |
| 103.137.244.0/24 | 256 | APNIC | IN | 8th Apr 2019 |
| 103.137.254.0/23 | 512 | APNIC | ID | 8th Apr 2019 |
| 103.137.3.0/24 | 256 | APNIC | IN | 19th Mar 2019 |
| 103.137.4.0/23 | 512 | APNIC | VN | 18th Mar 2019 |
| 103.137.42.0/23 | 512 | APNIC | ID | 21st Mar 2019 |
| 103.137.58.0/23 | 512 | APNIC | CN | 22nd Mar 2019 |
| 103.137.76.0/22 | 1k | APNIC | CN | 25th Mar 2019 |
| 103.138.11.0/24 | 256 | APNIC |  PK | 9th Apr 2019 |
| 103.138.110.0/23 | 512 | APNIC | VN | 19th Apr 2019 |
| 103.138.134.0/23 | 512 | APNIC | CN | 24th Apr 2019 |
| 103.138.2.0/23 | 512 | APNIC | CN | 8th Apr 2019 |
| 103.138.20.0/23 | 512 | APNIC | IN | 9th Apr 2019 |
| 103.138.208.0/23 | 512 | APNIC | CN | 6th May 2019 |
| 103.138.210.0/24 | 256 | APNIC | AU | 7th May 2019 |
| 103.138.220.0/23 | 512 | APNIC | CN | 7th May 2019 |
| 103.138.225.0/24 | 256 | APNIC |  KH | 8th May 2019 |