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 |
|---|---|---|---|---|
| 91.209.1.0/24 | 256 | RIPE NCC |  SI | 7th Apr 2010 |
| 91.209.100.0/24 | 256 | RIPE NCC |  GB | 7th Nov 2019 |
| 91.209.117.0/24 | 256 | RIPE NCC |  NL | 25th Aug 2025 |
| 91.209.134.0/24 | 256 | RIPE NCC |  CH | 19th Nov 2008 |
| 91.209.138.0/24 | 256 | RIPE NCC |  UA | 20th Nov 2008 |
| 91.209.14.0/24 | 256 | RIPE NCC |  LV | 7th Nov 2019 |
| 91.209.142.0/24 | 256 | RIPE NCC | GB | 8th Aug 2012 |
| 91.209.144.0/24 | 256 | RIPE NCC | GB | 20th Nov 2008 |
| 91.209.15.0/24 | 256 | RIPE NCC |  FR | 13th Oct 2008 |
| 91.209.164.0/24 | 256 | RIPE NCC | NL | 1st Oct 2010 |
| 91.209.170.0/24 | 256 | RIPE NCC | CH | 2nd Dec 2008 |
| 91.209.176.0/24 | 256 | RIPE NCC | UA | 3rd Dec 2008 |
| 91.209.179.0/24 | 256 | RIPE NCC |  CA | 7th Nov 2019 |
| 91.209.187.0/24 | 256 | RIPE NCC | GB | 10th Dec 2008 |
| 91.209.195.0/24 | 256 | RIPE NCC |  RO | 15th Dec 2008 |
| 91.209.200.0/24 | 256 | RIPE NCC | GB | 15th Dec 2008 |
| 91.209.204.0/24 | 256 | RIPE NCC | CH | 16th Dec 2008 |
| 91.209.205.0/24 | 256 | RIPE NCC |  TR | 7th Nov 2019 |
| 91.209.208.0/24 | 256 | RIPE NCC |  RU | 6th Nov 2023 |
| 91.209.227.0/24 | 256 | RIPE NCC |  SE | 28th Jan 2026 |
| 91.209.241.0/24 | 256 | RIPE NCC | RO | 29th Dec 2008 |
| 91.209.252.0/24 | 256 | RIPE NCC | GB | 6th Jan 2009 |
| 91.209.41.0/24 | 256 | RIPE NCC | CH | 20th Oct 2008 |
| 91.209.43.0/24 | 256 | RIPE NCC | NL | 21st Aug 2024 |
| 91.209.44.0/24 | 256 | RIPE NCC | FR | 21st Oct 2008 |
| 91.209.47.0/24 | 256 | RIPE NCC |  GR | 21st Oct 2008 |
| 91.209.57.0/24 | 256 | RIPE NCC | FR | 6th Jul 2020 |
| 91.209.58.0/24 | 256 | RIPE NCC |  PL | 7th Nov 2019 |
| 91.209.62.0/23 | 512 | RIPE NCC | PL | 3rd Oct 2019 |
| 91.209.81.0/24 | 256 | RIPE NCC |  DE | 31st Oct 2008 |
| 91.209.96.0/24 | 256 | RIPE NCC |  IR | 1st Jun 2021 |
| 91.209.99.0/24 | 256 | RIPE NCC | GB | 7th Nov 2019 |
| 91.210.124.0/24 | 256 | RIPE NCC |  CY | 10th Mar 2025 |
| 91.210.208.0/22 | 1k | RIPE NCC | GR | 17th Nov 2008 |
| 91.210.40.0/24 | 256 | RIPE NCC | PL | 1st Jun 2026 |
| 91.210.42.0/24 | 256 | RIPE NCC | SE | 1st Jun 2026 |
| 91.210.60.0/22 | 1k | RIPE NCC | SE | 15th Oct 2008 |
| 91.211.112.0/24 | 256 | RIPE NCC | TR | 28th Jan 2026 |
| 91.211.146.0/24 | 256 | RIPE NCC | GB | 8th Jan 2025 |
| 91.211.147.0/24 | 256 | RIPE NCC | CY | 8th Jan 2025 |
| 91.211.16.0/22 | 1k | RIPE NCC | RU | 26th Nov 2008 |
| 91.211.162.0/23 | 512 | RIPE NCC | NL | 20th Apr 2018 |
| 91.211.2.0/24 | 256 | RIPE NCC | RU | 30th Jun 2020 |
| 91.211.72.0/22 | 1k | RIPE NCC | NL | 5th Dec 2008 |
| 91.211.76.0/22 | 1k | RIPE NCC | RU | 5th Dec 2008 |
| 91.212.100.0/24 | 256 | RIPE NCC |  SC | 8th Nov 2019 |
| 91.212.102.0/24 | 256 | RIPE NCC |  PS | 26th Mar 2009 |
| 91.212.108.0/24 | 256 | RIPE NCC | GB | 31st Mar 2009 |
| 91.212.112.0/24 | 256 | RIPE NCC |  SK | 13th Feb 2012 |
| 91.212.114.0/24 | 256 | RIPE NCC |  IL | 3rd Apr 2009 |