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,318 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 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.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.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 |
| 217.22.2.0/24 | 256 | RIPE NCC | NO | 26th Jun 2026 |
| 217.22.3.0/24 | 256 | RIPE NCC |  NL | 26th Jun 2026 |
| 217.22.4.0/24 | 256 | RIPE NCC |  FR | 26th Jun 2026 |
| 217.22.6.0/24 | 256 | RIPE NCC |  UA | 26th Jun 2026 |
| 217.22.64.0/20 | 4.1k | RIPE NCC |  SE | 2nd Oct 2000 |
| 217.22.8.0/24 | 256 | RIPE NCC | GB | 26th Jun 2026 |
| 217.22.9.0/24 | 256 | RIPE NCC | RU | 26th Jun 2026 |
| 217.23.209.0/24 | 256 | RIPE NCC |  ES | 10th Mar 2003 |
| 217.23.210.0/23 | 512 | RIPE NCC | ES | 10th Mar 2003 |
| 217.23.212.0/22 | 1k | RIPE NCC | ES | 10th Mar 2003 |
| 217.23.216.0/21 | 2k | RIPE NCC | ES | 10th Mar 2003 |
| 217.23.96.0/20 | 4.1k | RIPE NCC | DK | 5th Oct 2000 |
| 217.26.220.0/24 | 256 | RIPE NCC |  CY | 22nd Jan 2024 |
| 217.28.135.0/24 | 256 | RIPE NCC | NL | 13th Apr 2022 |
| 217.28.138.0/24 | 256 | RIPE NCC | NL | 13th Apr 2022 |
| 217.28.142.0/24 | 256 | RIPE NCC | PL | 13th Apr 2022 |
| 217.29.196.0/22 | 1k | RIPE NCC | GB | 23rd Oct 2000 |
| 217.29.200.0/21 | 2k | RIPE NCC | GB | 23rd Oct 2000 |
| 217.64.240.0/20 | 4.1k | RIPE NCC | BE | 17th Jun 2003 |
| 217.65.130.0/24 | 256 | RIPE NCC | FR | 26th Jan 2026 |
| 217.65.65.0/24 | 256 | RIPE NCC |  IT | 1st May 2025 |
| 217.65.69.0/24 | 256 | RIPE NCC |  CZ | 12th May 2025 |
| 217.65.71.0/24 | 256 | RIPE NCC | PL | 26th May 2025 |
| 217.65.74.0/24 | 256 | RIPE NCC | GB | 11th Jun 2025 |
| 217.67.32.0/20 | 4.1k | RIPE NCC | DE | 8th Nov 2000 |
| 217.70.0.0/24 | 256 | RIPE NCC | DE | 30th Jul 2025 |