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,755 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 103.126.132.0/22 | 1k | APNIC |  CN | 2nd Dec 2018 |
| 103.126.16.0/22 | 1k | APNIC | CN | 26th Nov 2018 |
| 103.126.186.0/24 | 256 | APNIC |  AU | 5th Dec 2018 |
| 103.126.195.0/24 | 256 | APNIC |  ID | 28th Dec 2022 |
| 103.126.26.0/24 | 256 | APNIC | ID | 28th Dec 2022 |
| 103.126.44.0/22 | 1k | APNIC | CN | 27th Nov 2018 |
| 103.127.129.0/24 | 256 | APNIC | ID | 20th Dec 2018 |
| 103.127.148.0/22 | 1k | APNIC |  TW | 21st Dec 2018 |
| 103.127.16.0/23 | 512 | APNIC | ID | 11th Dec 2018 |
| 103.127.200.0/22 | 1k | APNIC |  VN | 24th Dec 2018 |
| 103.127.253.0/24 | 256 | APNIC |  IN | 27th Dec 2018 |
| 103.127.34.0/24 | 256 | APNIC | IN | 12th Dec 2018 |
| 103.127.78.0/23 | 512 | APNIC | IN | 17th Dec 2018 |
| 103.127.80.0/22 | 1k | APNIC |  HK | 14th Dec 2018 |
| 103.127.88.0/23 | 512 | APNIC |  TH | 17th Dec 2018 |
| 103.127.91.0/24 | 256 | APNIC | IN | 18th Dec 2018 |
| 103.129.153.0/24 | 256 | APNIC |  BD | 6th Sept 2018 |
| 103.129.192.0/23 | 512 | APNIC | IN | 6th Sept 2018 |
| 103.129.232.0/22 | 1k | APNIC | IN | 11th Sept 2018 |
| 103.129.240.0/22 | 1k | APNIC | TW | 12th Sept 2018 |
| 103.129.8.0/22 | 1k | APNIC | IN | 31st Aug 2018 |
| 103.13.0.0/24 | 256 | APNIC | IN | 11th Nov 2015 |
| 103.13.108.0/22 | 1k | APNIC | IN | 2nd Jul 2012 |
| 103.13.12.0/22 | 1k | APNIC | CN | 29th Oct 2015 |
| 103.13.124.0/22 | 1k | APNIC | CN | 3rd Jul 2012 |
| 103.13.160.0/22 | 1k | APNIC |  KR | 25th Jul 2012 |
| 103.13.180.0/24 | 256 | APNIC | IN | 26th Jul 2012 |
| 103.13.182.0/24 | 256 | APNIC |  PH | 29th Jul 2022 |
| 103.13.183.0/24 | 256 | APNIC | IN | 31st Jul 2012 |
| 103.13.191.0/24 | 256 | APNIC | HK | 26th Jul 2012 |
| 103.13.196.0/22 | 1k | APNIC | CN | 27th Jul 2012 |
| 103.13.20.0/22 | 1k | APNIC |  JP | 30th May 2012 |
| 103.13.200.0/22 | 1k | APNIC | ID | 27th Jul 2012 |
| 103.13.216.0/23 | 512 | APNIC | AU | 31st Jul 2012 |
| 103.13.218.0/24 | 256 | RIPE NCC |  BE | 2nd Aug 2012 |
| 103.13.219.0/24 | 256 | APNIC | IN | 3rd Aug 2012 |
| 103.13.232.0/23 | 512 | APNIC | ID | 27th Sept 2022 |
| 103.13.24.0/23 | 512 | APNIC | JP | 30th May 2012 |
| 103.13.26.0/24 | 256 | APNIC | JP | 30th May 2012 |
| 103.13.37.0/24 | 256 | APNIC | ID | 12th Jun 2012 |
| 103.13.38.0/24 | 256 | APNIC | ID | 12th Jun 2012 |
| 103.130.111.0/24 | 256 | APNIC | AU | 8th Oct 2018 |
| 103.130.120.0/22 | 1k | APNIC | TW | 8th Oct 2018 |
| 103.130.132.0/22 | 1k | APNIC | CN | 8th Oct 2018 |
| 103.130.20.0/22 | 1k | APNIC | TW | 3rd Oct 2018 |
| 103.130.220.0/22 | 1k | APNIC | VN | 11th Oct 2018 |
| 103.130.228.0/22 | 1k | APNIC | CN | 11th Oct 2018 |
| 103.130.24.0/22 | 1k | APNIC | TW | 3rd Oct 2018 |
| 103.130.32.0/20 | 4.1k | APNIC | TW | 3rd Oct 2018 |
| 103.130.52.0/22 | 1k | APNIC | VN | 4th Oct 2018 |