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 unannounced space registered through APNIC, largest first.
Unannounced blocks registered through APNIC
22,593 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 103.180.249.0/24 | 256 | APNIC |  IN | 1st Feb 2022 |
| 103.180.66.0/24 | 256 | APNIC | IN | 24th Jan 2022 |
| 103.180.92.0/23 | 512 | APNIC | IN | 24th Jan 2022 |
| 103.181.12.0/23 | 512 | APNIC |  HK | 2nd Feb 2022 |
| 103.181.130.0/23 | 512 | APNIC |  AU | 11th Feb 2022 |
| 103.181.18.0/24 | 256 | APNIC |  NZ | 3rd Feb 2022 |
| 103.181.195.0/24 | 256 | APNIC |  ID | 15th Feb 2022 |
| 103.181.236.0/23 | 512 | APNIC | IN | 16th Feb 2022 |
| 103.181.38.0/23 | 512 | APNIC | IN | 3rd Feb 2022 |
| 103.181.82.0/23 | 512 | APNIC | ID | 7th Feb 2022 |
| 103.181.94.0/23 | 512 | APNIC | IN | 8th Feb 2022 |
| 103.182.108.0/23 | 512 | APNIC | IN | 22nd Feb 2022 |
| 103.182.136.0/23 | 512 | APNIC | ID | 23rd Feb 2022 |
| 103.182.172.0/24 | 256 | APNIC |  MV | 25th Feb 2022 |
| 103.182.178.0/23 | 512 | APNIC | IN | 25th Feb 2022 |
| 103.182.198.0/23 | 512 | APNIC | IN | 28th Feb 2022 |
| 103.182.99.0/24 | 256 | APNIC | ID | 22nd Feb 2022 |
| 103.183.111.0/24 | 256 | APNIC | AU | 10th Mar 2022 |
| 103.183.154.0/23 | 512 | APNIC |  TW | 11th Mar 2022 |
| 103.183.208.0/23 | 512 | APNIC | IN | 14th Mar 2022 |
| 103.183.252.0/24 | 256 | APNIC | ID | 16th Mar 2022 |
| 103.183.26.0/23 | 512 | APNIC |  CN | 3rd Mar 2022 |
| 103.183.36.0/23 | 512 | APNIC | IN | 3rd Mar 2022 |
| 103.183.41.0/24 | 256 | APNIC | AU | 7th Mar 2022 |
| 103.183.76.0/23 | 512 | APNIC |  JP | 8th Mar 2022 |
| 103.183.88.0/23 | 512 | APNIC | IN | 8th Mar 2022 |
| 103.184.118.0/23 | 512 | APNIC | IN | 23rd Mar 2022 |
| 103.184.130.0/23 | 512 | APNIC | IN | 23rd Mar 2022 |
| 103.184.192.0/23 | 512 | APNIC | IN | 25th Mar 2022 |
| 103.184.204.0/24 | 256 | APNIC | IN | 25th Mar 2022 |
| 103.184.253.0/24 | 256 | APNIC | AU | 27th Mar 2022 |
| 103.184.30.0/23 | 512 | APNIC | ID | 18th Mar 2022 |
| 103.184.36.0/23 | 512 | APNIC | IN | 21st Mar 2022 |
| 103.184.48.0/23 | 512 | APNIC | ID | 22nd Mar 2022 |
| 103.184.58.0/23 | 512 | APNIC |  PK | 22nd Mar 2022 |
| 103.184.60.0/23 | 512 | APNIC | CN | 22nd Mar 2022 |
| 103.184.76.0/23 | 512 | APNIC | IN | 22nd Mar 2022 |
| 103.185.196.0/24 | 256 | APNIC | ID | 31st Mar 2022 |
| 103.185.198.0/23 | 512 | APNIC | IN | 31st Mar 2022 |
| 103.185.200.0/23 | 512 | APNIC | IN | 31st Mar 2022 |
| 103.185.208.0/23 | 512 | APNIC | IN | 31st Mar 2022 |
| 103.185.213.0/24 | 256 | APNIC | IN | 31st Mar 2022 |
| 103.185.252.0/23 | 512 | APNIC | ID | 6th Apr 2022 |
| 103.185.48.0/23 | 512 | APNIC | ID | 28th Mar 2022 |
| 103.185.78.0/23 | 512 | APNIC | CN | 28th Mar 2022 |
| 103.185.80.0/23 | 512 | APNIC | CN | 29th Mar 2022 |
| 103.186.111.0/24 | 256 | APNIC | IN | 19th Apr 2022 |
| 103.186.13.0/24 | 256 | APNIC | AU | 8th Apr 2022 |
| 103.186.130.0/23 | 512 | APNIC | IN | 19th Apr 2022 |
| 103.186.140.0/23 | 512 | APNIC | ID | 20th Apr 2022 |