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.187.140.0/22 | 1k | RIPE NCC |  CZ | 27th Jan 2017 |
| 185.187.148.0/22 | 1k | RIPE NCC |  CY | 27th Jan 2017 |
| 185.187.188.0/22 | 1k | RIPE NCC |  RU | 30th Jan 2017 |
| 185.187.20.0/22 | 1k | RIPE NCC |  NL | 24th Jan 2017 |
| 185.187.200.0/22 | 1k | RIPE NCC | CZ | 30th Jan 2017 |
| 185.187.24.0/22 | 1k | RIPE NCC |  NO | 24th Jan 2017 |
| 185.187.36.0/22 | 1k | RIPE NCC |  IL | 24th Jan 2017 |
| 185.187.8.0/22 | 1k | RIPE NCC |  SI | 24th Jan 2017 |
| 185.187.89.0/24 | 256 | RIPE NCC | RU | 25th Jan 2017 |
| 185.188.14.0/24 | 256 | RIPE NCC |  KZ | 17th Jan 2025 |
| 185.188.184.0/22 | 1k | RIPE NCC | CZ | 23rd Feb 2018 |
| 185.188.204.0/22 | 1k | RIPE NCC |  DE | 6th Sept 2018 |
| 185.188.209.0/24 | 256 | RIPE NCC |  ES | 6th Feb 2017 |
| 185.188.220.0/22 | 1k | RIPE NCC |  GB | 7th Feb 2017 |
| 185.188.224.0/22 | 1k | RIPE NCC |  SE | 7th Feb 2017 |
| 185.188.228.0/22 | 1k | RIPE NCC |  BG | 7th Feb 2017 |
| 185.188.240.0/22 | 1k | RIPE NCC | DE | 7th Feb 2017 |
| 185.188.28.0/24 | 256 | RIPE NCC |  FR | 26th Jan 2026 |
| 185.188.43.0/24 | 256 | RIPE NCC |  PL | 29th Jun 2021 |
| 185.188.80.0/22 | 1k | RIPE NCC |  IT | 7th Jan 2019 |
| 185.189.116.0/22 | 1k | RIPE NCC |  UA | 9th Feb 2017 |
| 185.189.232.0/22 | 1k | RIPE NCC | GB | 13th Feb 2017 |
| 185.189.76.0/22 | 1k | RIPE NCC | IT | 9th Feb 2017 |
| 185.189.8.0/22 | 1k | RIPE NCC | NL | 8th Feb 2017 |
| 185.189.96.0/22 | 1k | RIPE NCC | DE | 9th Feb 2017 |
| 185.19.108.0/22 | 1k | RIPE NCC | GB | 21st Feb 2013 |
| 185.19.128.0/22 | 1k | RIPE NCC | IT | 21st Feb 2013 |
| 185.19.144.0/22 | 1k | RIPE NCC | GB | 21st Feb 2013 |
| 185.19.244.0/22 | 1k | RIPE NCC | UA | 26th Feb 2013 |
| 185.19.35.0/24 | 256 | RIPE NCC |  LI | 14th Jan 2025 |
| 185.19.36.0/22 | 1k | RIPE NCC | DE | 19th Feb 2013 |
| 185.19.40.0/24 | 256 | RIPE NCC | NL | 27th Oct 2025 |
| 185.19.41.0/24 | 256 | RIPE NCC | SE | 27th Oct 2025 |
| 185.19.43.0/24 | 256 | RIPE NCC |  TR | 27th Oct 2025 |
| 185.19.60.0/22 | 1k | RIPE NCC | DE | 11th Dec 2014 |
| 185.19.72.0/22 | 1k | RIPE NCC |  SK | 20th Feb 2013 |
| 185.190.12.0/22 | 1k | RIPE NCC | GB | 14th Feb 2017 |
| 185.190.128.0/22 | 1k | RIPE NCC | GB | 17th Feb 2017 |
| 185.190.16.0/24 | 256 | RIPE NCC | TR | 14th Feb 2017 |
| 185.190.19.0/24 | 256 | RIPE NCC | TR | 14th Feb 2017 |
| 185.190.200.0/22 | 1k | RIPE NCC |  IE | 20th Feb 2017 |
| 185.190.27.0/24 | 256 | RIPE NCC | PL | 30th Jun 2021 |
| 185.190.32.0/22 | 1k | RIPE NCC |  CH | 15th Feb 2017 |
| 185.190.60.0/22 | 1k | RIPE NCC | GB | 15th Feb 2017 |
| 185.190.89.0/24 | 256 | RIPE NCC | CZ | 16th Sept 2020 |
| 185.191.112.0/22 | 1k | RIPE NCC | UA | 22nd Feb 2017 |
| 185.191.128.0/22 | 1k | ARIN |  CA | 30th Jul 2019 |
| 185.191.146.0/24 | 256 | RIPE NCC | DE | 23rd Feb 2017 |
| 185.191.147.0/24 | 256 | RIPE NCC | FR | 23rd Feb 2017 |
| 185.191.152.0/22 | 1k | RIPE NCC | FR | 23rd Feb 2017 |