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 |
|---|---|---|---|---|
| 185.251.22.0/24 | 256 | RIPE NCC |  RU | 9th Sept 2021 |
| 185.251.24.0/24 | 256 | RIPE NCC |  IT | 10th Mar 2021 |
| 185.251.244.0/22 | 1k | RIPE NCC |  GB | 27th Mar 2018 |
| 185.251.52.0/22 | 1k | RIPE NCC |  DE | 22nd Mar 2018 |
| 185.251.68.0/24 | 256 | RIPE NCC |  FR | 11th Mar 2021 |
| 185.251.69.0/24 | 256 | RIPE NCC | DE | 11th Mar 2021 |
| 185.252.120.0/22 | 1k | RIPE NCC |  SE | 28th Mar 2018 |
| 185.252.148.0/22 | 1k | RIPE NCC | DE | 28th Mar 2018 |
| 185.252.208.0/24 | 256 | RIPE NCC |  SC | 9th Sept 2021 |
| 185.252.215.0/24 | 256 | RIPE NCC |  MD | 10th Sept 2021 |
| 185.252.32.0/22 | 1k | RIPE NCC | DE | 27th Mar 2018 |
| 185.252.64.0/22 | 1k | RIPE NCC | GB | 27th Mar 2018 |
| 185.253.1.0/24 | 256 | RIPE NCC |  US | 10th Sept 2021 |
| 185.253.109.0/24 | 256 | RIPE NCC | DE | 17th Mar 2021 |
| 185.253.129.0/24 | 256 | RIPE NCC |  ES | 10th Nov 2025 |
| 185.253.130.0/24 | 256 | RIPE NCC | FR | 10th Nov 2025 |
| 185.253.131.0/24 | 256 | RIPE NCC |  CH | 12th Nov 2025 |
| 185.253.2.0/24 | 256 | RIPE NCC | RU | 10th Sept 2021 |
| 185.253.248.0/22 | 1k | RIPE NCC |  AT | 5th Apr 2018 |
| 185.253.3.0/24 | 256 | RIPE NCC | RU | 10th Sept 2021 |
| 185.253.4.0/24 | 256 | RIPE NCC |  CA | 10th Sept 2021 |
| 185.253.5.0/24 | 256 | RIPE NCC | US | 10th Sept 2021 |
| 185.253.61.0/24 | 256 | RIPE NCC |  LV | 3rd Apr 2018 |
| 185.254.112.0/22 | 1k | RIPE NCC | DE | 10th Apr 2018 |
| 185.254.164.0/24 | 256 | RIPE NCC |  IE | 19th Mar 2021 |
| 185.254.166.0/24 | 256 | RIPE NCC |  IR | 19th Mar 2021 |
| 185.254.216.0/24 | 256 | RIPE NCC |  GR | 11th Apr 2018 |
| 185.254.4.0/22 | 1k | RIPE NCC |  PL | 6th Apr 2018 |
| 185.255.139.0/24 | 256 | RIPE NCC | FR | 23rd Mar 2021 |
| 185.255.180.0/22 | 1k | RIPE NCC | GB | 16th Apr 2018 |
| 185.255.20.0/22 | 1k | RIPE NCC | ES | 12th Apr 2018 |
| 185.255.232.0/22 | 1k | RIPE NCC | GB | 16th Apr 2018 |
| 185.255.240.0/22 | 1k | RIPE NCC |  CZ | 16th Apr 2018 |
| 185.255.4.0/22 | 1k | RIPE NCC | FR | 12th Apr 2018 |
| 185.255.60.0/22 | 1k | RIPE NCC | IT | 13th Apr 2018 |
| 185.26.108.0/22 | 1k | RIPE NCC |  NL | 17th May 2013 |
| 185.26.12.0/22 | 1k | RIPE NCC | GB | 13th May 2013 |
| 185.26.128.0/22 | 1k | RIPE NCC |  NO | 21st May 2013 |
| 185.26.20.0/22 | 1k | RIPE NCC | NL | 14th May 2013 |
| 185.26.214.0/24 | 256 | RIPE NCC | NL | 24th Feb 2025 |
| 185.26.215.0/24 | 256 | RIPE NCC |  FI | 24th Feb 2025 |
| 185.26.228.0/22 | 1k | RIPE NCC | GB | 27th May 2013 |
| 185.26.96.0/22 | 1k | RIPE NCC | DE | 17th May 2013 |
| 185.27.112.0/22 | 1k | RIPE NCC |  DK | 30th May 2013 |
| 185.27.64.0/22 | 1k | RIPE NCC |  LI | 29th May 2013 |
| 185.28.117.0/24 | 256 | RIPE NCC | ES | 7th Mar 2023 |
| 185.28.118.0/24 | 256 | RIPE NCC | ES | 7th Mar 2023 |
| 185.28.136.0/22 | 1k | RIPE NCC | SE | 13th Jun 2013 |
| 185.28.220.0/22 | 1k | RIPE NCC | NL | 18th Jun 2013 |
| 185.28.24.0/22 | 1k | RIPE NCC |  SK | 10th Jun 2013 |