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.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 |
| 185.163.130.0/24 | 256 | RIPE NCC |  DK | 22nd Jan 2026 |
| 185.163.131.0/24 | 256 | RIPE NCC |  AZ | 22nd Jan 2026 |
| 185.163.176.0/22 | 1k | RIPE NCC | RU | 16th Aug 2016 |
| 185.163.206.0/24 | 256 | RIPE NCC |  NL | 15th Oct 2020 |
| 185.163.224.0/22 | 1k | RIPE NCC |  ME | 17th Aug 2016 |
| 185.163.50.0/24 | 256 | RIPE NCC |  AT | 17th Apr 2020 |
| 185.163.88.0/22 | 1k | RIPE NCC |  UA | 15th Aug 2016 |
| 185.164.128.0/22 | 1k | RIPE NCC |  LT | 19th Aug 2016 |
| 185.164.160.0/24 | 256 | RIPE NCC |  IT | 13th Mar 2023 |
| 185.164.161.0/24 | 256 | RIPE NCC | DE | 13th Mar 2023 |
| 185.164.168.0/22 | 1k | RIPE NCC | US | 22nd Aug 2016 |
| 185.164.196.0/22 | 1k | RIPE NCC | GB | 22nd Aug 2016 |
| 185.164.220.0/22 | 1k | RIPE NCC | GB | 23rd Aug 2016 |
| 185.165.100.0/22 | 1k | RIPE NCC | UA | 25th Aug 2016 |
| 185.165.16.0/22 | 1k | RIPE NCC | DE | 24th Aug 2016 |
| 185.165.180.0/22 | 1k | RIPE NCC | GB | 29th Aug 2016 |
| 185.165.32.0/22 | 1k | RIPE NCC |  RE | 24th Aug 2016 |
| 185.165.40.0/22 | 1k | RIPE NCC | IR | 24th Aug 2016 |
| 185.165.47.0/24 | 256 | RIPE NCC | GE | 24th Aug 2016 |
| 185.165.78.0/24 | 256 | RIPE NCC | TR | 25th Aug 2016 |
| 185.165.84.0/22 | 1k | RIPE NCC | DE | 25th Aug 2016 |
| 185.165.95.0/24 | 256 | RIPE NCC |  PL | 2nd Jun 2025 |
| 185.166.0.0/24 | 256 | RIPE NCC | TR | 30th Jun 2026 |
| 185.166.1.0/24 | 256 | RIPE NCC | NL | 30th Jun 2026 |
| 185.166.120.0/22 | 1k | RIPE NCC | DK | 6th Sept 2016 |
| 185.166.152.0/22 | 1k | RIPE NCC | CY | 6th Sept 2016 |
| 185.166.2.0/24 | 256 | RIPE NCC | RU | 30th Jun 2026 |
| 185.166.93.0/24 | 256 | RIPE NCC |  CH | 22nd Jan 2026 |
| 185.166.94.0/24 | 256 | RIPE NCC | GB | 22nd Jan 2026 |