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.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.233.0/24 | 256 | RIPE NCC |  AT | 30th Jun 2026 |
| 85.8.235.0/24 | 256 | RIPE NCC |  SA | 30th Jun 2026 |
| 85.8.238.0/24 | 256 | RIPE NCC |  FI | 9th Jul 2026 |
| 85.8.240.0/24 | 256 | RIPE NCC | SA | 17th Jul 2026 |
| 85.8.241.0/24 | 256 | RIPE NCC |  US | 17th Jul 2026 |
| 85.8.245.0/24 | 256 | RIPE NCC |  SG | 21st Aug 2026 |
| 85.8.247.0/24 | 256 | RIPE NCC |  PL | 26th Aug 2026 |
| 85.88.32.0/19 | 8.2k | RIPE NCC | BE | 22nd Oct 2004 |
| 85.9.225.0/24 | 256 | RIPE NCC | FR | 16th Feb 2005 |
| 85.9.226.0/23 | 512 | RIPE NCC |  GB | 16th Feb 2005 |
| 85.9.228.0/22 | 1k | RIPE NCC | GB | 16th Feb 2005 |
| 85.9.232.0/21 | 2k | RIPE NCC | GB | 16th Feb 2005 |
| 85.9.240.0/21 | 2k | RIPE NCC | FR | 16th Feb 2005 |
| 85.9.248.0/21 | 2k | RIPE NCC | GB | 16th Feb 2005 |
| 85.90.213.0/24 | 256 | RIPE NCC | ES | 11th Nov 2004 |
| 85.90.214.0/24 | 256 | RIPE NCC | ES | 11th Nov 2004 |
| 85.90.218.0/23 | 512 | RIPE NCC | ES | 11th Nov 2004 |
| 85.91.104.0/24 | 256 | RIPE NCC | RU | 22nd Nov 2004 |
| 85.91.106.0/24 | 256 | RIPE NCC | RU | 22nd Nov 2004 |
| 85.92.0.0/19 | 8.2k | RIPE NCC | RU | 2nd Dec 2004 |
| 85.93.64.0/20 | 4.1k | RIPE NCC |  DE | 8th Dec 2004 |
| 85.93.80.0/21 | 2k | RIPE NCC | DE | 8th Dec 2004 |
| 85.93.94.0/23 | 512 | RIPE NCC | DE | 8th Dec 2004 |
| 86.104.127.0/24 | 256 | RIPE NCC |  NL | 18th Apr 2005 |
| 86.104.2.0/24 | 256 | RIPE NCC | GB | 18th Apr 2005 |
| 86.104.210.0/24 | 256 | RIPE NCC | PL | 18th Apr 2005 |
| 86.104.216.0/22 | 1k | RIPE NCC | DE | 18th Apr 2005 |
| 86.104.221.0/24 | 256 | RIPE NCC |  RO | 18th Apr 2005 |
| 86.104.72.0/22 | 1k | RIPE NCC |  MD | 18th Apr 2005 |
| 86.105.120.0/21 | 2k | RIPE NCC | ES | 18th Apr 2005 |
| 86.105.15.0/24 | 256 | RIPE NCC | RO | 18th Apr 2005 |
| 86.105.177.0/24 | 256 | RIPE NCC | IT | 18th Apr 2005 |
| 86.105.179.0/24 | 256 | RIPE NCC | IT | 18th Apr 2005 |
| 86.105.187.0/24 | 256 | RIPE NCC | PL | 18th Apr 2005 |
| 86.105.192.0/24 | 256 | RIPE NCC | RO | 18th Apr 2005 |
| 86.105.194.0/24 | 256 | RIPE NCC | TR | 18th Apr 2005 |
| 86.105.197.0/24 | 256 | RIPE NCC | TR | 18th Apr 2005 |