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
25,269 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 185.233.218.0/24 | 256 | RIPE NCC |  BE | 27th Dec 2019 |
| 185.233.240.0/22 | 1k | RIPE NCC |  DE | 24th Nov 2017 |
| 185.233.252.0/22 | 1k | RIPE NCC |  DK | 27th Nov 2017 |
| 185.233.28.0/22 | 1k | RIPE NCC |  NL | 21st Nov 2017 |
| 185.233.56.0/22 | 1k | RIPE NCC | DK | 22nd Nov 2017 |
| 185.233.60.0/22 | 1k | RIPE NCC | NL | 22nd Nov 2017 |
| 185.233.64.0/24 | 256 | RIPE NCC |  UA | 15th Jan 2021 |
| 185.234.103.0/24 | 256 | RIPE NCC | DE | 4th Mar 2026 |
| 185.234.16.0/22 | 1k | RIPE NCC |  CH | 27th Nov 2017 |
| 185.234.160.0/22 | 1k | RIPE NCC |  SI | 29th Nov 2017 |
| 185.234.216.0/24 | 256 | RIPE NCC |  RU | 22nd Nov 2021 |
| 185.234.218.0/24 | 256 | RIPE NCC |  TR | 23rd Nov 2021 |
| 185.234.246.0/24 | 256 | RIPE NCC |  ES | 21st Jan 2021 |
| 185.234.248.0/22 | 1k | RIPE NCC |  SK | 1st Dec 2017 |
| 185.234.4.0/22 | 1k | RIPE NCC |  RO | 27th Nov 2017 |
| 185.234.44.0/22 | 1k | RIPE NCC | DE | 28th Nov 2017 |
| 185.234.76.0/22 | 1k | RIPE NCC |  FR | 28th Nov 2017 |
| 185.235.108.0/22 | 1k | RIPE NCC | BE | 5th Dec 2017 |
| 185.235.152.0/22 | 1k | RIPE NCC |  AT | 5th Dec 2017 |
| 185.235.180.0/22 | 1k | RIPE NCC |  US | 6th Dec 2017 |
| 185.235.244.0/24 | 256 | RIPE NCC |  JE | 9th Jul 2021 |
| 185.235.252.0/22 | 1k | RIPE NCC |  CY | 7th Dec 2017 |
| 185.235.70.0/24 | 256 | RIPE NCC | RO | 4th Dec 2017 |
| 185.235.76.0/24 | 256 | RIPE NCC |  PL | 28th Jan 2021 |
| 185.236.124.0/22 | 1k | RIPE NCC |  GB | 12th Dec 2017 |
| 185.236.232.0/22 | 1k | RIPE NCC |  MD | 14th Dec 2017 |
| 185.236.236.0/22 | 1k | RIPE NCC |  BG | 14th Dec 2017 |
| 185.236.44.0/24 | 256 | RIPE NCC |  IE | 8th Feb 2021 |
| 185.236.45.0/24 | 256 | RIPE NCC |  IR | 9th Feb 2021 |
| 185.236.80.0/22 | 1k | RIPE NCC | AT | 11th Dec 2017 |
| 185.237.108.0/22 | 1k | RIPE NCC | CH | 18th Dec 2017 |
| 185.237.112.0/22 | 1k | RIPE NCC | CH | 18th Dec 2017 |
| 185.237.116.0/22 | 1k | RIPE NCC | CH | 18th Dec 2017 |
| 185.237.120.0/22 | 1k | RIPE NCC | CH | 18th Dec 2017 |
| 185.237.188.0/22 | 1k | RIPE NCC | TR | 19th Dec 2017 |
| 185.237.196.0/22 | 1k | RIPE NCC | GB | 20th Dec 2017 |
| 185.237.240.0/22 | 1k | RIPE NCC |  RS | 20th Dec 2017 |
| 185.237.44.0/22 | 1k | RIPE NCC | BE | 15th Dec 2017 |
| 185.237.52.0/22 | 1k | RIPE NCC | IE | 15th Dec 2017 |
| 185.237.92.0/24 | 256 | RIPE NCC | DE | 12th Jan 2024 |
| 185.238.117.0/24 | 256 | RIPE NCC | GB | 22nd Dec 2017 |
| 185.238.137.0/24 | 256 | RIPE NCC | PL | 18th Aug 2023 |
| 185.238.184.0/22 | 1k | RIPE NCC |  FI | 28th Dec 2017 |
| 185.238.20.0/22 | 1k | RIPE NCC | IR | 20th Dec 2017 |
| 185.238.24.0/22 | 1k | RIPE NCC | DE | 20th Dec 2017 |
| 185.239.168.0/23 | 512 | RIPE NCC | NL | 4th Jan 2018 |
| 185.239.172.0/24 | 256 | RIPE NCC | US | 4th Jan 2018 |
| 185.239.173.0/24 | 256 | RIPE NCC | IE | 4th Jan 2018 |
| 185.239.174.0/24 | 256 | RIPE NCC |  IT | 4th Jan 2018 |
| 185.239.200.0/22 | 1k | RIPE NCC | ES | 5th Jan 2018 |