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.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.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 |
| 185.191.172.0/22 | 1k | RIPE NCC | UA | 10th Sept 2019 |
| 185.191.72.0/22 | 1k | RIPE NCC |  SA | 21st Feb 2017 |
| 185.191.80.0/22 | 1k | RIPE NCC | UA | 22nd Feb 2017 |
| 185.192.128.0/22 | 1k | RIPE NCC |  IS | 1st Mar 2017 |
| 185.192.132.0/22 | 1k | RIPE NCC | NL | 1st Mar 2017 |
| 185.192.164.0/22 | 1k | RIPE NCC | GB | 2nd Mar 2017 |
| 185.192.200.0/22 | 1k | RIPE NCC | DE | 2nd Mar 2017 |
| 185.192.32.0/22 | 1k | RIPE NCC |  BE | 28th Feb 2017 |
| 185.192.4.0/22 | 1k | RIPE NCC |  GI | 27th Feb 2017 |
| 185.192.60.0/22 | 1k | RIPE NCC | IT | 28th Feb 2017 |
| 185.192.92.0/22 | 1k | RIPE NCC | GB | 1st Mar 2017 |
| 185.193.132.0/22 | 1k | RIPE NCC |  AZ | 8th Mar 2017 |
| 185.193.192.0/22 | 1k | RIPE NCC |  AT | 9th Mar 2017 |
| 185.193.36.0/22 | 1k | RIPE NCC | AT | 6th Mar 2017 |
| 185.193.45.0/24 | 256 | RIPE NCC |  ES | 30th Jun 2021 |
| 185.193.46.0/24 | 256 | RIPE NCC |  RU | 30th Jun 2021 |
| 185.193.96.0/22 | 1k | RIPE NCC | GB | 7th Mar 2017 |
| 185.194.12.0/24 | 256 | RIPE NCC | CZ | 28th Sept 2020 |
| 185.194.13.0/24 | 256 | RIPE NCC | DE | 28th Sept 2020 |
| 185.194.132.0/22 | 1k | RIPE NCC | SA | 15th Mar 2017 |
| 185.194.149.0/24 | 256 | RIPE NCC | DE | 15th Mar 2017 |
| 185.194.16.0/22 | 1k | RIPE NCC | NL | 13th Mar 2017 |
| 185.194.180.0/22 | 1k | RIPE NCC | CH | 15th Mar 2017 |
| 185.194.196.0/23 | 512 | RIPE NCC |  TJ | 16th Mar 2017 |