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.155.2.0/23 | 512 | RIPE NCC |  IE | 5th Nov 2004 |
| 85.155.216.0/21 | 2k | RIPE NCC |  ES | 5th Nov 2004 |
| 85.155.4.0/22 | 1k | RIPE NCC | ES | 5th Nov 2004 |
| 85.155.8.0/24 | 256 | RIPE NCC |  IS | 5th Nov 2004 |
| 85.155.9.0/24 | 256 | RIPE NCC | ES | 5th Nov 2004 |
| 85.159.112.0/24 | 256 | RIPE NCC |  GB | 30th Dec 2019 |
| 85.159.113.0/24 | 256 | RIPE NCC |  IR | 30th Dec 2019 |
| 85.159.120.0/21 | 2k | RIPE NCC |  GI | 15th Mar 2005 |
| 85.159.136.0/21 | 2k | RIPE NCC | GB | 21st Mar 2005 |
| 85.159.16.0/22 | 1k | RIPE NCC | IE | 3rd Feb 2005 |
| 85.159.184.0/21 | 2k | RIPE NCC |  FR | 30th Mar 2005 |
| 85.159.20.0/23 | 512 | RIPE NCC | IE | 3rd Feb 2005 |
| 85.159.22.0/24 | 256 | RIPE NCC | IE | 3rd Feb 2005 |
| 85.159.56.0/21 | 2k | RIPE NCC |  DE | 24th Feb 2005 |
| 85.184.200.0/21 | 2k | RIPE NCC |  IM | 19th Nov 2004 |
| 85.184.208.0/20 | 4.1k | RIPE NCC | IM | 19th Nov 2004 |
| 85.188.192.0/18 | 16.4k | RIPE NCC | GB | 13th Apr 2006 |
| 85.193.78.0/24 | 256 | RIPE NCC |  US | 7th Mar 2023 |
| 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.198.100.0/22 | 1k | RIPE NCC |  RU | 31st Jan 2005 |
| 85.198.84.0/22 | 1k | RIPE NCC | RU | 31st Jan 2005 |
| 85.198.92.0/22 | 1k | RIPE NCC | RU | 31st Jan 2005 |
| 85.198.96.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.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.36.0/24 | 256 | RIPE NCC | GB | 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.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 | RO | 27th Feb 2019 |
| 85.209.196.0/22 | 1k | RIPE NCC | RU | 27th Feb 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 |