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
85,356 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 217.16.48.0/20 | 4.1k | RIPE NCC |  GB | 22nd Nov 2002 |
| 217.170.160.0/20 | 4.1k | RIPE NCC |  PL | 14th May 2009 |
| 217.171.160.0/20 | 4.1k | RIPE NCC |  IT | 2nd Apr 2001 |
| 217.172.160.0/23 | 512 | RIPE NCC |  DE | 6th Apr 2001 |
| 217.172.162.0/24 | 256 | RIPE NCC | DE | 6th Apr 2001 |
| 217.172.164.0/24 | 256 | RIPE NCC | DE | 6th Apr 2001 |
| 217.172.168.0/23 | 512 | RIPE NCC | DE | 6th Apr 2001 |
| 217.172.191.0/24 | 256 | RIPE NCC | DE | 27th Jul 2001 |
| 217.177.13.0/24 | 256 | RIPE NCC | GB | 2nd Mar 2001 |
| 217.177.96.0/19 | 8.2k | RIPE NCC | GB | 2nd Mar 2001 |
| 217.179.56.0/22 | 1k | RIPE NCC |  CH | 2nd Mar 2001 |
| 217.179.72.0/23 | 512 | RIPE NCC |  AZ | 2nd Mar 2001 |
| 217.18.51.0/24 | 256 | RIPE NCC |  UA | 6th May 2026 |
| 217.18.83.0/24 | 256 | RIPE NCC |  NL | 8th Mar 2023 |
| 217.18.84.0/24 | 256 | RIPE NCC | GB | 8th Mar 2023 |
| 217.18.87.0/24 | 256 | RIPE NCC |  FR | 8th Mar 2023 |
| 217.18.91.0/24 | 256 | RIPE NCC | GB | 26th Jan 2026 |
| 217.18.93.0/24 | 256 | RIPE NCC |  LV | 9th Mar 2023 |
| 217.180.0.0/21 | 2k | RIPE NCC | GB | 2nd Mar 2001 |
| 217.180.18.0/23 | 512 | RIPE NCC |  KZ | 2nd Mar 2001 |
| 217.180.36.0/23 | 512 | RIPE NCC | GB | 2nd Mar 2001 |
| 217.180.38.0/24 | 256 | RIPE NCC |  IM | 2nd Mar 2001 |
| 217.180.60.0/24 | 256 | RIPE NCC | GB | 2nd Mar 2001 |
| 217.180.61.0/24 | 256 | RIPE NCC | IT | 2nd Mar 2001 |
| 217.180.8.0/22 | 1k | RIPE NCC | GB | 2nd Mar 2001 |
| 217.19.9.0/24 | 256 | RIPE NCC |  RO | 19th Sept 2000 |
| 217.194.140.0/22 | 1k | APNIC |  HK | 19th Apr 2001 |
| 217.195.194.0/24 | 256 | RIPE NCC |  LU | 24th Apr 2001 |
| 217.196.192.0/20 | 4.1k | RIPE NCC |  MK | 22nd Mar 2012 |
| 217.196.32.0/20 | 4.1k | RIPE NCC |  BE | 25th Apr 2001 |
| 217.196.96.0/21 | 2k | RIPE NCC |  RU | 12th May 2010 |
| 217.197.101.0/24 | 256 | RIPE NCC | CH | 15th May 2023 |
| 217.197.107.0/24 | 256 | RIPE NCC | RU | 16th May 2023 |
| 217.197.208.0/20 | 4.1k | RIPE NCC | CH | 27th Oct 2004 |
| 217.197.64.0/20 | 4.1k | RIPE NCC | PL | 9th Mar 2004 |
| 217.197.96.0/24 | 256 | RIPE NCC | GB | 15th May 2023 |
| 217.197.99.0/24 | 256 | RIPE NCC | RO | 15th May 2023 |
| 217.198.188.0/24 | 256 | RIPE NCC |  JE | 8th Feb 2022 |
| 217.198.32.0/20 | 4.1k | RIPE NCC | GB | 3rd May 2001 |
| 217.198.48.0/21 | 2k | RIPE NCC | GB | 5th Nov 2004 |
| 217.199.213.0/24 | 256 | RIPE NCC | RU | 22nd Nov 2004 |
| 217.199.222.0/24 | 256 | RIPE NCC | RU | 22nd Nov 2004 |
| 217.20.224.0/20 | 4.1k | AFRINIC |  EG | 25th Sept 2000 |
| 217.22.0.0/24 | 256 | RIPE NCC |  DK | 26th Jun 2026 |
| 217.22.1.0/24 | 256 | RIPE NCC |  NO | 26th Jun 2026 |
| 217.22.10.0/24 | 256 | RIPE NCC |  FI | 26th Jun 2026 |
| 217.22.13.0/24 | 256 | RIPE NCC | RO | 26th Jun 2026 |
| 217.22.15.0/24 | 256 | RIPE NCC | DE | 26th Jun 2026 |
| 217.22.161.0/24 | 256 | RIPE NCC | RU | 2nd Oct 2000 |
| 217.22.166.0/24 | 256 | RIPE NCC | RU | 2nd Oct 2000 |