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.194.192.0/23 | 512 | RIPE NCC |  FI | 4th Jan 2005 |
| 85.194.232.0/24 | 256 | RIPE NCC | FI | 4th Jan 2005 |
| 85.194.234.0/23 | 512 | RIPE NCC | FI | 4th Jan 2005 |
| 85.194.252.0/23 | 512 | RIPE NCC |  AM | 4th Jan 2005 |
| 85.194.254.0/23 | 512 | RIPE NCC |  NO | 4th Jan 2005 |
| 85.197.192.0/18 | 16.4k | RIPE NCC |  IS | 25th Jan 2005 |
| 85.198.48.0/20 | 4.1k | RIPE NCC |  IR | 31st Jan 2005 |
| 85.198.92.0/22 | 1k | RIPE NCC |  RU | 31st Jan 2005 |
| 85.199.248.0/24 | 256 | RIPE NCC |  RO | 8th Feb 2005 |
| 85.202.200.0/24 | 256 | RIPE NCC |  DE | 12th Feb 2020 |
| 85.202.204.0/22 | 1k | RIPE NCC | DE | 22nd Aug 2018 |
| 85.202.208.0/20 | 4.1k | RIPE NCC |  PL | 6th Feb 2008 |
| 85.204.119.0/24 | 256 | RIPE NCC |  IT | 13th Jan 2005 |
| 85.204.132.0/23 | 512 | RIPE NCC |  DK | 13th Jan 2005 |
| 85.204.136.0/23 | 512 | RIPE NCC | DK | 13th Jan 2005 |
| 85.204.147.0/24 | 256 | RIPE NCC | IT | 13th Jan 2005 |
| 85.204.194.0/23 | 512 | RIPE NCC | DK | 13th Jan 2005 |
| 85.204.198.0/24 | 256 | RIPE NCC | PL | 13th Jan 2005 |
| 85.204.39.0/24 | 256 | RIPE NCC | DE | 13th Jan 2005 |
| 85.204.41.0/24 | 256 | RIPE NCC | RO | 13th Jan 2005 |
| 85.208.100.0/22 | 1k | RIPE NCC |  GB | 21st Feb 2019 |
| 85.208.120.0/22 | 1k | RIPE NCC | RO | 21st Feb 2019 |
| 85.208.132.0/22 | 1k | RIPE NCC |  NL | 21st Feb 2019 |
| 85.208.152.0/22 | 1k | RIPE NCC |  AT | 21st Feb 2019 |
| 85.208.156.0/22 | 1k | RIPE NCC | DE | 21st Feb 2019 |
| 85.208.164.0/22 | 1k | RIPE NCC |  SE | 22nd Feb 2019 |
| 85.208.232.0/22 | 1k | RIPE NCC | IT | 22nd Feb 2019 |
| 85.208.88.0/22 | 1k | RIPE NCC | NO | 21st Feb 2019 |
| 85.209.136.0/22 | 1k | RIPE NCC |  BZ | 27th Feb 2019 |
| 85.209.232.0/22 | 1k | RIPE NCC |  LU | 1st Mar 2019 |
| 85.209.252.0/22 | 1k | RIPE NCC | AT | 1st Mar 2019 |
| 85.209.36.0/22 | 1k | RIPE NCC | PL | 25th Feb 2019 |
| 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.222.236.0/22 | 1k | RIPE NCC | NL | 22nd Mar 2005 |
| 85.233.80.0/20 | 4.1k | RIPE NCC | RU | 21st Apr 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 |