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 RIPE NCC, largest first.
Unannounced blocks registered through RIPE NCC
24,902 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 178.236.17.0/24 | 256 | RIPE NCC |  RU | 26th May 2010 |
| 178.236.20.0/23 | 512 | RIPE NCC | RU | 26th May 2010 |
| 178.236.28.0/24 | 256 | RIPE NCC | RU | 26th May 2010 |
| 178.236.30.0/23 | 512 | RIPE NCC | RU | 26th May 2010 |
| 178.239.39.0/24 | 256 | RIPE NCC |  DE | 2nd Aug 2010 |
| 178.239.48.0/20 | 4.1k | RIPE NCC |  SE | 3rd Aug 2010 |
| 178.248.168.0/21 | 2k | RIPE NCC |  NL | 10th May 2010 |
| 178.248.184.0/21 | 2k | RIPE NCC |  FR | 11th May 2010 |
| 178.248.64.0/21 | 2k | RIPE NCC | RU | 3rd May 2010 |
| 178.249.104.0/21 | 2k | RIPE NCC |  US | 25th May 2010 |
| 178.249.112.0/21 | 2k | RIPE NCC |  MK | 25th May 2010 |
| 178.249.40.0/21 | 2k | RIPE NCC |  GB | 19th May 2010 |
| 178.250.24.0/21 | 2k | RIPE NCC |  CH | 31st May 2010 |
| 178.250.72.0/21 | 2k | RIPE NCC | GB | 2nd Jun 2010 |
| 178.252.0.0/18 | 16.4k | RIPE NCC |  PL | 19th May 2010 |
| 178.255.223.0/24 | 256 | RIPE NCC | NL | 7th Sept 2021 |
| 178.255.244.0/22 | 1k | RIPE NCC | US | 15th Jul 2010 |
| 178.36.0.0/15 | 131k | RIPE NCC | PL | 28th Jan 2010 |
| 178.72.24.0/21 | 2k | RIPE NCC | SE | 10th Feb 2010 |
| 178.73.128.0/18 | 16.4k | RIPE NCC | FR | 22nd Mar 2010 |
| 178.76.16.0/20 | 4.1k | RIPE NCC |  AZ | 31st Mar 2010 |
| 178.76.32.0/19 | 8.2k | RIPE NCC | AZ | 31st Mar 2010 |
| 178.76.8.0/21 | 2k | RIPE NCC | AZ | 31st Mar 2010 |
| 178.77.124.0/24 | 256 | RIPE NCC | DE | 15th Apr 2010 |
| 178.79.192.0/18 | 16.4k | RIPE NCC | US | 12th May 2010 |
| 179.198.80.0/20 | 4.1k | RIPE NCC |  LT | 13th Mar 2025 |
| 179.236.0.0/19 | 8.2k | RIPE NCC |  CN | 6th Mar 2025 |
| 179.67.224.0/20 | 4.1k | RIPE NCC | LT | 13th Mar 2025 |
| 180.149.40.0/22 | 1k | RIPE NCC |  AT | 31st Aug 2009 |
| 185.0.0.0/24 | 256 | RIPE NCC |  RO | 8th Sept 2022 |
| 185.0.10.0/24 | 256 | RIPE NCC | NL | 29th Nov 2022 |
| 185.0.11.0/24 | 256 | RIPE NCC | NL | 13th Dec 2022 |
| 185.0.16.0/24 | 256 | RIPE NCC | PL | 19th Dec 2022 |
| 185.0.17.0/24 | 256 | RIPE NCC | DE | 11th Jan 2023 |
| 185.0.18.0/24 | 256 | RIPE NCC |  IT | 20th Jan 2023 |
| 185.0.19.0/24 | 256 | RIPE NCC | FR | 8th May 2026 |
| 185.0.2.0/24 | 256 | RIPE NCC | PL | 30th Apr 2026 |
| 185.0.20.0/23 | 512 | RIPE NCC |  CZ | 20th Jan 2023 |
| 185.0.22.0/24 | 256 | RIPE NCC |  KZ | 20th Feb 2023 |
| 185.0.23.0/24 | 256 | RIPE NCC |  UZ | 24th Feb 2023 |
| 185.0.24.0/24 | 256 | RIPE NCC | GB | 9th Sept 2026 |
| 185.0.25.0/24 | 256 | RIPE NCC |  PT | 22nd May 2023 |
| 185.0.26.0/24 | 256 | RIPE NCC | NL | 5th Oct 2026 |
| 185.0.27.0/24 | 256 | RIPE NCC | NL | 18th Feb 2025 |
| 185.0.28.0/24 | 256 | RIPE NCC |  BG | 26th May 2023 |
| 185.0.29.0/24 | 256 | RIPE NCC |  UA | 11th Mar 2025 |
| 185.0.3.0/24 | 256 | RIPE NCC | DE | 27th Oct 2022 |
| 185.0.30.0/24 | 256 | RIPE NCC | CH | 5th Jun 2023 |
| 185.0.31.0/24 | 256 | RIPE NCC | CH | 9th Jun 2023 |
| 185.0.32.0/24 | 256 | RIPE NCC | GB | 12th Jun 2023 |