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,738 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 103.103.68.0/22 | 1k | APNIC |  HK | 1st Nov 2017 |
| 103.103.72.0/22 | 1k | APNIC |  CN | 2nd Nov 2017 |
| 103.103.84.0/22 | 1k | RIPE NCC |  SE | 2nd Nov 2017 |
| 103.104.0.0/21 | 2k | APNIC | CN | 14th Nov 2017 |
| 103.104.10.0/24 | 256 | APNIC |  ID | 15th Nov 2017 |
| 103.104.104.0/22 | 1k | APNIC | CN | 22nd Nov 2017 |
| 103.104.143.0/24 | 256 | APNIC |  BD | 27th Nov 2017 |
| 103.104.146.0/23 | 512 | APNIC |  AF | 28th Nov 2017 |
| 103.104.152.0/22 | 1k | APNIC | CN | 27th Nov 2017 |
| 103.104.166.0/23 | 512 | APNIC |  AU | 28th Nov 2017 |
| 103.104.188.0/22 | 1k | APNIC | CN | 29th Nov 2017 |
| 103.104.197.0/24 | 256 | APNIC |  NP | 29th Nov 2017 |
| 103.104.200.0/23 | 512 | APNIC | AU | 29th Nov 2017 |
| 103.104.229.0/24 | 256 | APNIC |  SG | 1st Dec 2017 |
| 103.104.36.0/22 | 1k | APNIC | CN | 16th Nov 2017 |
| 103.104.40.0/22 | 1k | APNIC | CN | 16th Nov 2017 |
| 103.104.64.0/22 | 1k | APNIC | CN | 17th Nov 2017 |
| 103.104.76.0/22 | 1k | APNIC |  IN | 17th Nov 2017 |
| 103.105.116.0/22 | 1k | APNIC | CN | 8th Dec 2017 |
| 103.105.120.0/23 | 512 | APNIC | IN | 6th Mar 2023 |
| 103.105.148.0/22 | 1k | RIPE NCC |  JE | 11th Jul 2017 |
| 103.105.16.0/22 | 1k | APNIC | CN | 4th Dec 2017 |
| 103.105.188.0/24 | 256 | APNIC | IN | 12th Dec 2017 |
| 103.105.189.0/24 | 256 | APNIC | ID | 13th Dec 2017 |
| 103.105.192.0/22 | 1k | APNIC | ID | 13th Dec 2017 |
| 103.105.199.0/24 | 256 | APNIC | ID | 14th Dec 2017 |
| 103.105.204.0/22 | 1k | APNIC | CN | 13th Dec 2017 |
| 103.105.240.0/22 | 1k | APNIC | IN | 14th Dec 2017 |
| 103.105.244.0/22 | 1k | APNIC | IN | 14th Dec 2017 |
| 103.105.4.0/22 | 1k | APNIC | CN | 4th Dec 2017 |
| 103.105.48.0/22 | 1k | RIPE NCC |  GB | 5th Dec 2017 |
| 103.105.8.0/23 | 512 | APNIC | ID | 6th Mar 2023 |
| 103.106.120.0/22 | 1k | APNIC | CN | 25th Dec 2017 |
| 103.106.128.0/22 | 1k | APNIC | CN | 26th Dec 2017 |
| 103.106.132.0/22 | 1k | APNIC | CN | 26th Dec 2017 |
| 103.106.16.0/22 | 1k | APNIC |  MY | 15th Dec 2017 |
| 103.106.160.0/22 | 1k | APNIC | CN | 28th Dec 2017 |
| 103.106.182.0/24 | 256 | APNIC | AF | 29th Dec 2017 |
| 103.106.196.0/22 | 1k | APNIC | CN | 2nd Jan 2018 |
| 103.106.208.0/22 | 1k | APNIC | HK | 3rd Jan 2018 |
| 103.106.212.0/22 | 1k | APNIC | CN | 4th Jan 2018 |
| 103.106.40.0/22 | 1k | APNIC | CN | 18th Dec 2017 |
| 103.106.44.0/22 | 1k | APNIC | CN | 18th Dec 2017 |
| 103.106.48.0/22 | 1k | APNIC |  JP | 18th Dec 2017 |
| 103.106.57.0/24 | 256 | APNIC | BD | 19th Dec 2017 |
| 103.106.60.0/22 | 1k | APNIC | CN | 19th Dec 2017 |
| 103.106.68.0/22 | 1k | APNIC | CN | 20th Dec 2017 |
| 103.106.74.0/23 | 512 | APNIC | ID | 20th Dec 2017 |
| 103.106.96.0/22 | 1k | APNIC | CN | 21st Dec 2017 |
| 103.107.10.0/23 | 512 | APNIC | HK | 5th Jan 2018 |