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
85,075 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 175.179.64.0/19 | 8.2k | APNIC |  JP | 27th Jan 2010 |
| 175.184.200.0/21 | 2k | APNIC |  AU | 29th Jan 2010 |
| 175.184.208.0/21 | 2k | APNIC | AU | 29th Jan 2010 |
| 175.26.0.0/16 | 65.5k | APNIC |  CN | 4th Dec 2009 |
| 175.28.63.0/24 | 256 | APNIC | JP | 11th Dec 2009 |
| 175.40.0.0/16 | 65.5k | APNIC |  IN | 11th Dec 2009 |
| 175.45.240.0/20 | 4.1k | APNIC |  KR | 21st Dec 2009 |
| 175.48.0.0/12 | 1M | APNIC | CN | 14th Dec 2009 |
| 175.64.0.0/11 | 2.1M | APNIC | CN | 14th Dec 2009 |
| 176.10.89.0/24 | 256 | RIPE NCC |  US | 23rd Jan 2025 |
| 176.10.90.0/24 | 256 | RIPE NCC |  CA | 23rd Jan 2025 |
| 176.10.94.0/24 | 256 | RIPE NCC |  GB | 29th Jan 2025 |
| 176.100.200.0/21 | 2k | RIPE NCC |  ES | 31st Oct 2011 |
| 176.100.248.0/23 | 512 | RIPE NCC |  RU | 30th Jan 2012 |
| 176.100.250.0/24 | 256 | RIPE NCC | RU | 30th Jan 2012 |
| 176.100.251.0/24 | 256 | RIPE NCC | RU | 30th Jan 2012 |
| 176.100.41.0/24 | 256 | RIPE NCC |  BE | 1st Sept 2021 |
| 176.101.168.0/24 | 256 | RIPE NCC |  DE | 24th Jun 2020 |
| 176.101.170.0/24 | 256 | RIPE NCC |  NO | 25th Jun 2020 |
| 176.101.171.0/24 | 256 | RIPE NCC |  IT | 25th Jun 2020 |
| 176.101.80.0/22 | 1k | RIPE NCC |  PL | 9th Nov 2011 |
| 176.102.188.0/24 | 256 | RIPE NCC | PL | 29th Nov 2011 |
| 176.102.190.0/23 | 512 | RIPE NCC | PL | 29th Nov 2011 |
| 176.103.112.0/24 | 256 | RIPE NCC |  UA | 14th Dec 2011 |
| 176.103.116.0/22 | 1k | RIPE NCC | UA | 14th Dec 2011 |
| 176.103.212.0/22 | 1k | RIPE NCC | UA | 20th Dec 2011 |
| 176.103.248.0/21 | 2k | RIPE NCC | IT | 23rd Dec 2011 |
| 176.104.168.0/21 | 2k | RIPE NCC | RU | 29th Dec 2011 |
| 176.105.244.0/24 | 256 | RIPE NCC |  RO | 15th Aug 2022 |
| 176.105.245.0/24 | 256 | RIPE NCC |  IR | 15th Aug 2022 |
| 176.106.136.0/21 | 2k | RIPE NCC |  CZ | 19th Apr 2012 |
| 176.106.40.0/21 | 2k | RIPE NCC |  PS | 11th Jan 2012 |
| 176.107.120.0/21 | 2k | RIPE NCC | CZ | 31st Jan 2012 |
| 176.109.112.0/20 | 4.1k | RIPE NCC | RU | 21st Feb 2012 |
| 176.109.56.0/21 | 2k | RIPE NCC |  SK | 23rd Feb 2012 |
| 176.110.100.0/24 | 256 | RIPE NCC |  SA | 25th Jul 2012 |
| 176.110.109.0/24 | 256 | RIPE NCC | DE | 21st Apr 2021 |
| 176.111.33.0/24 | 256 | RIPE NCC | UA | 5th Mar 2012 |
| 176.111.45.0/24 | 256 | RIPE NCC | UA | 5th Mar 2012 |
| 176.111.50.0/24 | 256 | RIPE NCC | UA | 5th Mar 2012 |
| 176.113.160.0/22 | 1k | RIPE NCC | UA | 4th Apr 2012 |
| 176.113.45.0/24 | 256 | RIPE NCC | GB | 3rd Jul 2020 |
| 176.113.46.0/24 | 256 | RIPE NCC |  GR | 6th Jul 2020 |
| 176.113.76.0/22 | 1k | RIPE NCC | DE | 15th Oct 2018 |
| 176.115.112.0/22 | 1k | RIPE NCC | RU | 24th Apr 2012 |
| 176.115.116.0/22 | 1k | RIPE NCC | RU | 24th Apr 2012 |
| 176.115.224.0/21 | 2k | RIPE NCC | DE | 4th May 2012 |
| 176.116.6.0/24 | 256 | RIPE NCC |  IE | 25th Oct 2021 |
| 176.117.0.0/21 | 2k | RIPE NCC | RU | 11th May 2012 |
| 176.117.109.0/24 | 256 | RIPE NCC |  CY | 23rd Jul 2025 |