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 |
|---|---|---|---|---|
| 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.25.0/24 | 256 | RIPE NCC |  PT | 22nd May 2023 |
| 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 |
| 185.0.33.0/24 | 256 | RIPE NCC | DE | 16th Jun 2023 |
| 185.0.35.0/24 | 256 | RIPE NCC | DE | 13th Jul 2023 |
| 185.0.36.0/24 | 256 | RIPE NCC | UZ | 4th Aug 2023 |
| 185.0.37.0/24 | 256 | RIPE NCC |  SA | 16th Aug 2023 |
| 185.0.38.0/24 | 256 | RIPE NCC |  SI | 31st Aug 2023 |
| 185.0.4.0/24 | 256 | RIPE NCC | DE | 8th Nov 2022 |
| 185.0.40.0/26 | 64 | RIPE NCC | CH | 17th Jul 2025 |
| 185.0.42.0/23 | 512 | RIPE NCC | PL | 18th Aug 2025 |
| 185.0.44.0/22 | 1k | RIPE NCC |  RU | 2nd Jun 2026 |
| 185.0.48.0/22 | 1k | RIPE NCC | UA | 29th Jul 2026 |
| 185.0.5.0/24 | 256 | RIPE NCC | DE | 8th Nov 2022 |
| 185.0.6.0/24 | 256 | RIPE NCC | DE | 8th Nov 2022 |
| 185.0.7.0/24 | 256 | RIPE NCC | DE | 8th Nov 2022 |
| 185.0.8.0/24 | 256 | RIPE NCC | DE | 11th Nov 2022 |
| 185.0.9.0/24 | 256 | RIPE NCC |  IT | 23rd Nov 2022 |
| 185.1.0.0/24 | 256 | RIPE NCC | RU | 3rd Oct 2012 |
| 185.1.1.0/24 | 256 | RIPE NCC |  PS | 17th Oct 2012 |
| 185.1.10.0/23 | 512 | RIPE NCC | PL | 3rd Apr 2013 |
| 185.1.100.0/24 | 256 | RIPE NCC |  AL | 31st Oct 2017 |
| 185.1.101.0/24 | 256 | RIPE NCC | GB | 2nd Nov 2017 |
| 185.1.102.0/24 | 256 | RIPE NCC | DE | 14th Nov 2017 |
| 185.1.103.0/24 | 256 | RIPE NCC |  RO | 15th Nov 2017 |
| 185.1.104.0/24 | 256 | RIPE NCC | GB | 17th Nov 2017 |
| 185.1.105.0/24 | 256 | RIPE NCC | CH | 22nd Nov 2017 |
| 185.1.106.0/24 | 256 | RIPE NCC | IT | 29th Nov 2017 |
| 185.1.107.0/24 | 256 | RIPE NCC |  SE | 4th Dec 2017 |
| 185.1.108.0/24 | 256 | RIPE NCC |  LB | 4th Dec 2017 |
| 185.1.109.0/24 | 256 | RIPE NCC |  IE | 6th Dec 2017 |
| 185.1.110.0/24 | 256 | RIPE NCC |  KG | 11th Dec 2017 |
| 185.1.111.0/24 | 256 | RIPE NCC | UA | 15th Dec 2017 |
| 185.1.112.0/24 | 256 | RIPE NCC | NL | 30th Jan 2018 |
| 185.1.113.0/24 | 256 | RIPE NCC |  LT | 31st Jan 2018 |
| 185.1.114.0/24 | 256 | RIPE NCC | IT | 9th Feb 2018 |
| 185.1.115.0/24 | 256 | RIPE NCC | IT | 9th Feb 2018 |
| 185.1.116.0/24 | 256 | RIPE NCC | PT | 13th Apr 2018 |
| 185.1.117.0/24 | 256 | RIPE NCC | RU | 14th May 2018 |
| 185.1.118.0/24 | 256 | RIPE NCC | RU | 25th May 2018 |
| 185.1.119.0/24 | 256 | RIPE NCC | DE | 12th Feb 2021 |