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 |
|---|---|---|---|---|
| 176.117.111.0/24 | 256 | RIPE NCC |  US | 24th Jul 2025 |
| 176.117.56.0/24 | 256 | RIPE NCC |  BE | 15th May 2012 |
| 176.118.176.0/24 | 256 | RIPE NCC |  ES | 29th Sept 2025 |
| 176.118.178.0/24 | 256 | RIPE NCC |  JP | 30th Sept 2025 |
| 176.118.194.0/24 | 256 | RIPE NCC |  NL | 7th Jul 2020 |
| 176.119.144.0/24 | 256 | RIPE NCC |  DE | 4th Feb 2020 |
| 176.119.194.0/24 | 256 | RIPE NCC |  HU | 6th Jan 2020 |
| 176.119.203.0/24 | 256 | RIPE NCC |  LU | 6th Jan 2020 |
| 176.119.204.0/24 | 256 | RIPE NCC |  SE | 6th Jan 2020 |
| 176.119.208.0/24 | 256 | RIPE NCC |  LB | 6th Jan 2020 |
| 176.119.211.0/24 | 256 | RIPE NCC | NL | 6th Jan 2020 |
| 176.119.219.0/24 | 256 | RIPE NCC | LU | 6th Jan 2020 |
| 176.119.221.0/24 | 256 | RIPE NCC |  PL | 7th Jan 2020 |
| 176.120.20.0/24 | 256 | RIPE NCC |  CA | 20th Aug 2024 |
| 176.120.23.0/24 | 256 | RIPE NCC | DE | 27th Aug 2024 |
| 176.120.64.0/22 | 1k | RIPE NCC |  MD | 20th Jun 2012 |
| 176.120.72.0/22 | 1k | RIPE NCC | MD | 20th Jun 2012 |
| 176.120.76.0/22 | 1k | RIPE NCC |  RU | 20th Jun 2012 |
| 176.120.80.0/22 | 1k | RIPE NCC | RU | 20th Jun 2012 |
| 176.120.88.0/21 | 2k | RIPE NCC | RU | 20th Jun 2012 |
| 176.121.10.0/24 | 256 | RIPE NCC |  PT | 28th Jun 2012 |
| 176.122.17.0/24 | 256 | RIPE NCC | RU | 9th Jul 2012 |
| 176.122.192.0/23 | 512 | RIPE NCC |  GB | 26th Jul 2012 |
| 176.122.199.0/24 | 256 | RIPE NCC | PL | 26th Jul 2012 |
| 176.122.208.0/23 | 512 | RIPE NCC |  RS | 4th Oct 2019 |
| 176.122.216.0/21 | 2k | RIPE NCC | PL | 26th Jul 2012 |
| 176.122.31.0/24 | 256 | RIPE NCC | RU | 9th Jul 2012 |
| 176.123.184.0/22 | 1k | RIPE NCC |  CZ | 30th Jul 2012 |
| 176.123.188.0/22 | 1k | RIPE NCC | RU | 30th Jul 2012 |
| 176.123.48.0/24 | 256 | RIPE NCC | DE | 27th Jul 2012 |
| 176.124.0.0/20 | 4.1k | RIPE NCC | RU | 3rd Sept 2012 |
| 176.124.246.0/24 | 256 | RIPE NCC |  IE | 13th Sept 2012 |
| 176.124.249.0/24 | 256 | RIPE NCC | GB | 24th Jul 2023 |
| 176.124.64.0/22 | 1k | RIPE NCC |  IR | 6th Sept 2012 |
| 176.125.250.0/23 | 512 | RIPE NCC | ES | 17th Oct 2018 |
| 176.126.106.0/24 | 256 | RIPE NCC |  LT | 26th Oct 2021 |
| 176.126.110.0/24 | 256 | RIPE NCC | ES | 26th Oct 2021 |
| 176.126.113.0/24 | 256 | RIPE NCC | MD | 26th Oct 2021 |
| 176.126.116.0/24 | 256 | RIPE NCC | GB | 26th Oct 2021 |
| 176.126.117.0/24 | 256 | RIPE NCC | GB | 26th Oct 2021 |
| 176.126.123.0/24 | 256 | RIPE NCC |  UA | 27th Oct 2021 |
| 176.126.160.0/24 | 256 | RIPE NCC | SE | 14th Sept 2012 |
| 176.126.176.0/20 | 4.1k | RIPE NCC | ES | 14th Sept 2012 |
| 176.126.38.0/24 | 256 | RIPE NCC |  GR | 13th Sept 2012 |
| 176.126.74.0/24 | 256 | RIPE NCC | DE | 14th Sept 2012 |
| 176.126.97.0/24 | 256 | RIPE NCC | US | 27th Jan 2026 |
| 176.22.128.0/19 | 8.2k | RIPE NCC | NL | 19th May 2011 |
| 176.223.119.0/24 | 256 | RIPE NCC |  CH | 29th Nov 2011 |
| 176.223.163.0/24 | 256 | RIPE NCC | NL | 29th Nov 2011 |
| 176.223.181.0/24 | 256 | RIPE NCC | US | 29th Nov 2011 |