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 |
|---|---|---|---|---|
| 85.25.168.0/22 | 1k | RIPE NCC |  DE | 5th Dec 2005 |
| 85.25.175.0/24 | 256 | RIPE NCC | DE | 5th Dec 2005 |
| 85.25.2.0/23 | 512 | RIPE NCC | DE | 1st Mar 2005 |
| 85.25.204.0/23 | 512 | RIPE NCC | DE | 5th Dec 2005 |
| 85.25.212.0/24 | 256 | RIPE NCC | DE | 5th Dec 2005 |
| 85.25.221.0/24 | 256 | RIPE NCC | DE | 5th Dec 2005 |
| 85.25.228.0/22 | 1k | RIPE NCC | DE | 5th Dec 2005 |
| 85.25.232.0/23 | 512 | RIPE NCC | DE | 5th Dec 2005 |
| 85.25.234.0/24 | 256 | RIPE NCC | DE | 5th Dec 2005 |
| 85.25.24.0/23 | 512 | RIPE NCC | DE | 1st Mar 2005 |
| 85.25.244.0/24 | 256 | RIPE NCC | DE | 5th Dec 2005 |
| 85.25.247.0/24 | 256 | RIPE NCC | DE | 5th Dec 2005 |
| 85.25.4.0/22 | 1k | RIPE NCC | DE | 1st Mar 2005 |
| 85.25.71.0/24 | 256 | RIPE NCC | DE | 1st Mar 2005 |
| 85.255.128.0/20 | 4.1k | RIPE NCC |  BG | 22nd Jun 2005 |
| 85.255.184.0/21 | 2k | RIPE NCC |  RU | 9th Sept 2011 |
| 85.255.80.0/22 | 1k | RIPE NCC | DE | 22nd Aug 2018 |
| 85.31.144.0/22 | 1k | RIPE NCC |  FR | 11th Jul 2005 |
| 85.31.148.0/22 | 1k | RIPE NCC |  NL | 11th Jul 2005 |
| 85.8.153.0/24 | 256 | RIPE NCC |  IT | 11th Jan 2024 |
| 85.8.193.0/24 | 256 | RIPE NCC |  DK | 26th Jun 2026 |
| 85.8.195.0/24 | 256 | RIPE NCC |  IE | 26th Jun 2026 |
| 85.8.197.0/24 | 256 | RIPE NCC |  CZ | 26th Jun 2026 |
| 85.8.199.0/24 | 256 | RIPE NCC | DE | 26th Jun 2026 |
| 85.8.200.0/24 | 256 | RIPE NCC | FR | 26th Jun 2026 |
| 85.8.202.0/24 | 256 | RIPE NCC | FR | 26th Jun 2026 |
| 85.8.204.0/24 | 256 | RIPE NCC |  GB | 26th Jun 2026 |
| 85.8.205.0/24 | 256 | RIPE NCC | BG | 26th Jun 2026 |
| 85.8.206.0/24 | 256 | RIPE NCC |  LT | 26th Jun 2026 |
| 85.8.207.0/24 | 256 | RIPE NCC | IT | 26th Jun 2026 |
| 85.8.209.0/24 | 256 | RIPE NCC |  TR | 26th Jun 2026 |
| 85.8.210.0/24 | 256 | RIPE NCC | GB | 26th Jun 2026 |
| 85.8.211.0/24 | 256 | RIPE NCC |  HU | 26th Jun 2026 |
| 85.8.212.0/24 | 256 | RIPE NCC | TR | 26th Jun 2026 |
| 85.8.213.0/24 | 256 | RIPE NCC |  GE | 26th Jun 2026 |
| 85.8.215.0/24 | 256 | RIPE NCC | RU | 26th Jun 2026 |
| 85.8.216.0/24 | 256 | RIPE NCC | IT | 26th Jun 2026 |
| 85.8.217.0/24 | 256 | RIPE NCC | TR | 26th Jun 2026 |
| 85.8.218.0/24 | 256 | RIPE NCC | TR | 26th Jun 2026 |
| 85.8.219.0/24 | 256 | RIPE NCC | FR | 26th Jun 2026 |
| 85.8.220.0/24 | 256 | RIPE NCC |  ES | 26th Jun 2026 |
| 85.8.222.0/24 | 256 | RIPE NCC |  AD | 26th Jun 2026 |
| 85.8.223.0/24 | 256 | RIPE NCC |  AE | 26th Jun 2026 |
| 85.8.224.0/24 | 256 | RIPE NCC |  CA | 29th Jun 2026 |
| 85.8.227.0/24 | 256 | RIPE NCC |  BA | 29th Jun 2026 |
| 85.8.228.0/24 | 256 | RIPE NCC |  BE | 29th Jun 2026 |
| 85.8.229.0/24 | 256 | RIPE NCC |  KZ | 29th Jun 2026 |
| 85.8.231.0/24 | 256 | RIPE NCC |  IR | 29th Jun 2026 |
| 85.8.233.0/24 | 256 | RIPE NCC |  AT | 30th Jun 2026 |
| 85.8.234.0/24 | 256 | RIPE NCC | GB | 30th Jun 2026 |