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
84,650 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 85.209.41.0/24 | 256 | RIPE NCC |  IR | 2nd Feb 2026 |
| 85.217.130.0/23 | 512 | RIPE NCC |  BG | 18th Jan 2005 |
| 85.217.166.0/24 | 256 | RIPE NCC | BG | 18th Jan 2005 |
| 85.217.208.0/21 | 2k | RIPE NCC |  CH | 18th Jan 2005 |
| 85.234.184.0/21 | 2k | RIPE NCC |  LT | 2nd May 2005 |
| 85.236.64.0/19 | 8.2k | RIPE NCC |  DK | 18th May 2005 |
| 85.237.128.0/19 | 8.2k | RIPE NCC |  SA | 25th May 2005 |
| 85.239.88.0/22 | 1k | RIPE NCC |  CZ | 16th Jun 2005 |
| 85.25.0.0/24 | 256 | RIPE NCC |  DE | 1st Mar 2005 |
| 85.25.111.0/24 | 256 | RIPE NCC | DE | 1st Mar 2005 |
| 85.25.112.0/22 | 1k | RIPE NCC | DE | 1st Mar 2005 |
| 85.25.120.0/24 | 256 | RIPE NCC | DE | 1st Mar 2005 |
| 85.25.122.0/23 | 512 | RIPE NCC | DE | 1st Mar 2005 |
| 85.25.16.0/23 | 512 | RIPE NCC | DE | 1st Mar 2005 |
| 85.25.161.0/24 | 256 | RIPE NCC | DE | 5th Dec 2005 |
| 85.25.162.0/23 | 512 | RIPE NCC | DE | 5th Dec 2005 |
| 85.25.164.0/22 | 1k | RIPE NCC | DE | 5th Dec 2005 |
| 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.26.0/24 | 256 | RIPE NCC | DE | 1st Mar 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.8.144.0/22 | 1k | RIPE NCC |  TR | 16th Nov 2018 |
| 85.8.153.0/24 | 256 | RIPE NCC |  IT | 11th Jan 2024 |
| 85.8.156.0/22 | 1k | RIPE NCC | TR | 16th Nov 2018 |
| 85.8.160.0/22 | 1k | RIPE NCC | TR | 16th Nov 2018 |
| 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 |