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.156.50.0/24 | 256 | RIPE NCC |  FR | 16th Jun 2026 |
| 185.156.88.0/22 | 1k | RIPE NCC |  ES | 15th Jun 2016 |
| 185.156.92.0/22 | 1k | RIPE NCC | ES | 15th Jun 2016 |
| 185.157.104.0/22 | 1k | RIPE NCC |  RS | 27th Jun 2016 |
| 185.157.122.0/24 | 256 | RIPE NCC |  CH | 1st Apr 2020 |
| 185.157.123.0/24 | 256 | RIPE NCC |  AT | 25th Jan 2022 |
| 185.157.218.0/23 | 512 | RIPE NCC |  TR | 30th Jun 2016 |
| 185.158.244.0/22 | 1k | RIPE NCC |  US | 8th Jul 2016 |
| 185.158.32.0/22 | 1k | RIPE NCC |  SY | 1st Jul 2016 |
| 185.158.68.0/22 | 1k | RIPE NCC |  RO | 7th Jan 2019 |
| 185.158.76.0/22 | 1k | RIPE NCC |  GB | 4th Jul 2016 |
| 185.158.88.0/22 | 1k | RIPE NCC |  IT | 4th Jul 2016 |
| 185.159.124.0/23 | 512 | RIPE NCC |  NL | 14th Jul 2016 |
| 185.159.126.0/24 | 256 | RIPE NCC | NL | 14th Jul 2016 |
| 185.159.132.0/22 | 1k | RIPE NCC |  CZ | 14th Jul 2016 |
| 185.159.148.0/22 | 1k | RIPE NCC |  RU | 14th Jul 2016 |
| 185.159.180.0/22 | 1k | RIPE NCC |  JO | 15th Jul 2016 |
| 185.159.188.0/24 | 256 | RIPE NCC |  PL | 18th Jan 2023 |
| 185.159.189.0/24 | 256 | RIPE NCC |  IR | 18th Jan 2023 |
| 185.159.24.0/22 | 1k | RIPE NCC |  EE | 11th Jul 2016 |
| 185.159.245.0/24 | 256 | RIPE NCC |  DE | 22nd Nov 2023 |
| 185.159.86.0/24 | 256 | RIPE NCC | DE | 23rd Jun 2021 |
| 185.16.128.0/22 | 1k | RIPE NCC | PL | 22nd Jan 2013 |
| 185.16.24.0/24 | 256 | RIPE NCC |  AE | 17th Jan 2013 |
| 185.16.249.0/24 | 256 | RIPE NCC |  LB | 12th Feb 2020 |
| 185.16.251.0/24 | 256 | RIPE NCC | RO | 20th Mar 2023 |
| 185.160.156.0/22 | 1k | RIPE NCC | NL | 22nd Jul 2016 |
| 185.160.172.0/22 | 1k | RIPE NCC | DE | 30th Jan 2019 |
| 185.160.200.0/22 | 1k | RIPE NCC | DE | 25th Jul 2016 |
| 185.160.204.0/24 | 256 | RIPE NCC |  CY | 7th Mar 2023 |
| 185.160.207.0/24 | 256 | RIPE NCC |  BE | 7th Mar 2023 |
| 185.160.232.0/22 | 1k | RIPE NCC | RS | 26th Jul 2016 |
| 185.160.240.0/22 | 1k | RIPE NCC | DE | 26th Jul 2016 |
| 185.160.62.0/24 | 256 | RIPE NCC | TR | 20th Jul 2016 |
| 185.160.63.0/24 | 256 | RIPE NCC |  LU | 20th Jul 2016 |
| 185.160.78.0/23 | 512 | RIPE NCC | DE | 20th Jul 2016 |
| 185.160.84.0/22 | 1k | RIPE NCC | DE | 20th Jul 2016 |
| 185.161.104.0/22 | 1k | RIPE NCC | US | 28th Jul 2016 |
| 185.161.186.0/24 | 256 | RIPE NCC |  KZ | 1st Aug 2016 |
| 185.161.250.0/24 | 256 | RIPE NCC | IR | 24th Feb 2023 |
| 185.161.252.0/22 | 1k | RIPE NCC | CZ | 3rd Aug 2016 |
| 185.161.69.0/24 | 256 | RIPE NCC | CY | 28th Jul 2016 |
| 185.162.100.0/22 | 1k | RIPE NCC | GB | 5th Aug 2016 |
| 185.162.182.0/24 | 256 | RIPE NCC |  PT | 9th Aug 2016 |
| 185.162.188.0/22 | 1k | RIPE NCC | RU | 9th Aug 2016 |
| 185.162.233.0/24 | 256 | RIPE NCC | RU | 10th Aug 2016 |
| 185.162.252.0/22 | 1k | RIPE NCC | GB | 11th Aug 2016 |
| 185.162.4.0/22 | 1k | RIPE NCC | CZ | 4th Aug 2016 |
| 185.162.72.0/23 | 512 | RIPE NCC |  GE | 5th Aug 2016 |
| 185.163.128.0/24 | 256 | RIPE NCC |  MD | 22nd Jan 2026 |