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.220.140.0/22 | 1k | RIPE NCC |  US | 13th Sept 2017 |
| 185.220.28.0/22 | 1k | RIPE NCC |  CZ | 8th Sept 2017 |
| 185.220.94.0/23 | 512 | RIPE NCC |  LV | 12th Sept 2017 |
| 185.220.96.0/22 | 1k | RIPE NCC |  DE | 12th Sept 2017 |
| 185.221.112.0/22 | 1k | RIPE NCC |  IR | 18th Sept 2017 |
| 185.221.116.0/22 | 1k | RIPE NCC |  RU | 18th Sept 2017 |
| 185.221.120.0/22 | 1k | RIPE NCC | RU | 18th Sept 2017 |
| 185.221.136.0/22 | 1k | RIPE NCC | DE | 18th Sept 2017 |
| 185.221.232.0/22 | 1k | RIPE NCC |  IS | 21st Sept 2017 |
| 185.221.24.0/22 | 1k | RIPE NCC |  ES | 14th Sept 2017 |
| 185.221.240.0/22 | 1k | RIPE NCC |  IT | 21st Sept 2017 |
| 185.221.4.0/22 | 1k | RIPE NCC |  GB | 14th Sept 2017 |
| 185.221.48.0/22 | 1k | RIPE NCC | DE | 15th Sept 2017 |
| 185.221.60.0/24 | 256 | RIPE NCC | GB | 8th Mar 2023 |
| 185.221.92.0/22 | 1k | RIPE NCC | GB | 18th Sept 2017 |
| 185.222.107.0/24 | 256 | RIPE NCC | GB | 20th Jan 2025 |
| 185.222.132.0/22 | 1k | RIPE NCC |  RO | 25th Sept 2017 |
| 185.222.136.0/23 | 512 | RIPE NCC | DE | 25th Sept 2017 |
| 185.222.176.0/22 | 1k | RIPE NCC |  SE | 26th Sept 2017 |
| 185.222.209.0/24 | 256 | RIPE NCC |  CH | 30th Nov 2020 |
| 185.222.43.0/24 | 256 | RIPE NCC | DE | 6th Jul 2021 |
| 185.222.52.0/22 | 1k | RIPE NCC | RU | 22nd Sept 2017 |
| 185.222.61.0/24 | 256 | RIPE NCC | DE | 15th Jan 2025 |
| 185.222.62.0/24 | 256 | RIPE NCC |  NL | 15th Jan 2025 |
| 185.222.63.0/24 | 256 | RIPE NCC |  FR | 15th Jan 2025 |
| 185.222.76.0/22 | 1k | RIPE NCC |  MT | 22nd Sept 2017 |
| 185.223.100.0/22 | 1k | RIPE NCC |  NO | 2nd Oct 2017 |
| 185.223.162.0/24 | 256 | RIPE NCC | GB | 7th Dec 2020 |
| 185.223.164.0/22 | 1k | RIPE NCC |  AT | 26th Aug 2019 |
| 185.223.212.0/24 | 256 | RIPE NCC | RU | 10th Dec 2020 |
| 185.223.8.0/22 | 1k | RIPE NCC | SE | 28th Sept 2017 |
| 185.224.144.0/22 | 1k | RIPE NCC | AT | 9th Oct 2017 |
| 185.224.148.0/22 | 1k | RIPE NCC | DE | 9th Oct 2017 |
| 185.224.20.0/22 | 1k | RIPE NCC |  IE | 5th Oct 2017 |
| 185.224.208.0/22 | 1k | RIPE NCC | GB | 10th Oct 2017 |
| 185.224.224.0/22 | 1k | RIPE NCC | DE | 29th May 2019 |
| 185.224.232.0/22 | 1k | RIPE NCC | GB | 11th Oct 2017 |
| 185.224.244.0/22 | 1k | RIPE NCC | CH | 11th Oct 2017 |
| 185.224.29.0/24 | 256 | RIPE NCC | DE | 7th Mar 2023 |
| 185.224.68.0/22 | 1k | RIPE NCC | GB | 6th Oct 2017 |
| 185.224.84.0/22 | 1k | RIPE NCC | FR | 6th Oct 2017 |
| 185.225.108.0/22 | 1k | RIPE NCC |  PL | 12th Oct 2017 |
| 185.225.124.0/24 | 256 | RIPE NCC | GB | 15th Dec 2020 |
| 185.225.125.0/24 | 256 | RIPE NCC | CH | 16th Dec 2020 |
| 185.225.127.0/24 | 256 | RIPE NCC | DE | 16th Dec 2020 |
| 185.225.136.0/22 | 1k | RIPE NCC | DE | 13th Oct 2017 |
| 185.225.228.0/22 | 1k | RIPE NCC | PL | 16th Oct 2017 |
| 185.225.25.0/24 | 256 | RIPE NCC | DE | 23rd May 2019 |
| 185.225.73.0/24 | 256 | RIPE NCC | IT | 12th Oct 2017 |
| 185.226.12.0/22 | 1k | RIPE NCC | FR | 16th Oct 2017 |