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.204.112.0/22 | 1k | RIPE NCC |  UA | 12th Aug 2011 |
| 91.204.12.0/22 | 1k | RIPE NCC | UA | 26th May 2008 |
| 91.204.236.0/22 | 1k | RIPE NCC |  UZ | 17th Jul 2008 |
| 91.204.40.0/22 | 1k | RIPE NCC |  GB | 26th Jun 2018 |
| 91.204.83.0/24 | 256 | RIPE NCC |  NL | 4th Jun 2008 |
| 91.205.100.0/22 | 1k | RIPE NCC |  US | 29th Aug 2008 |
| 91.205.159.0/24 | 256 | RIPE NCC |  NO | 2nd Mar 2020 |
| 91.205.228.0/24 | 256 | RIPE NCC | GB | 27th May 2020 |
| 91.205.252.0/22 | 1k | RIPE NCC |  RU | 3rd Oct 2008 |
| 91.206.122.0/24 | 256 | RIPE NCC |  DE | 25th Jan 2022 |
| 91.206.130.0/23 | 512 | RIPE NCC |  GE | 21st Jul 2008 |
| 91.206.144.0/23 | 512 | RIPE NCC |  IM | 25th Jul 2008 |
| 91.206.170.0/24 | 256 | RIPE NCC |  DK | 2nd Sept 2024 |
| 91.206.172.0/23 | 512 | RIPE NCC |  PL | 4th Aug 2008 |
| 91.206.186.0/23 | 512 | RIPE NCC | UA | 7th Aug 2008 |
| 91.206.202.0/23 | 512 | RIPE NCC |  AT | 3rd Oct 2019 |
| 91.206.204.0/23 | 512 | RIPE NCC | AT | 3rd Oct 2019 |
| 91.206.208.0/23 | 512 | RIPE NCC |  IE | 3rd Oct 2019 |
| 91.206.230.0/24 | 256 | RIPE NCC | DK | 9th Jan 2020 |
| 91.206.232.0/23 | 512 | RIPE NCC | NL | 28th Aug 2008 |
| 91.206.238.0/23 | 512 | RIPE NCC | AT | 29th Aug 2008 |
| 91.206.29.0/24 | 256 | RIPE NCC | DE | 26th Jun 2023 |
| 91.206.42.0/23 | 512 | RIPE NCC |  RO | 11th Jun 2008 |
| 91.206.52.0/23 | 512 | RIPE NCC |  CH | 17th Jun 2008 |
| 91.206.74.0/24 | 256 | RIPE NCC | DE | 22nd Apr 2026 |
| 91.206.75.0/24 | 256 | RIPE NCC |  BE | 28th Apr 2026 |
| 91.206.90.0/24 | 256 | RIPE NCC | PL | 24th Oct 2011 |
| 91.206.94.0/24 | 256 | RIPE NCC | NL | 13th Mar 2023 |
| 91.207.117.0/24 | 256 | RIPE NCC | DK | 21st Nov 2022 |
| 91.207.12.0/24 | 256 | RIPE NCC | CH | 14th Jan 2025 |
| 91.207.144.0/23 | 512 | RIPE NCC |  LT | 3rd Oct 2019 |
| 91.207.158.0/23 | 512 | RIPE NCC | NO | 24th Oct 2008 |
| 91.207.182.0/24 | 256 | RIPE NCC | NL | 23rd Jan 2023 |
| 91.207.196.0/23 | 512 | RIPE NCC | NO | 3rd Oct 2019 |
| 91.207.204.0/24 | 256 | RIPE NCC | GB | 1st Jun 2021 |
| 91.207.206.0/24 | 256 | RIPE NCC | GB | 12th Sept 2022 |
| 91.207.208.0/24 | 256 | RIPE NCC |  AE | 17th Dec 2025 |
| 91.207.209.0/24 | 256 | RIPE NCC |  CY | 18th Dec 2025 |
| 91.207.222.0/23 | 512 | RIPE NCC | NO | 3rd Oct 2019 |
| 91.207.230.0/23 | 512 | RIPE NCC |  CZ | 3rd Oct 2019 |
| 91.207.234.0/23 | 512 | RIPE NCC | CZ | 3rd Oct 2019 |
| 91.207.38.0/23 | 512 | RIPE NCC | GB | 23rd Sept 2008 |
| 91.207.4.0/24 | 256 | RIPE NCC | RU | 11th Sept 2008 |
| 91.207.40.0/23 | 512 | RIPE NCC | RU | 23rd Sept 2008 |
| 91.207.46.0/23 | 512 | RIPE NCC | UA | 25th Sept 2008 |
| 91.207.70.0/24 | 256 | RIPE NCC | PL | 16th Jan 2025 |
| 91.207.71.0/24 | 256 | RIPE NCC | RU | 16th Jan 2025 |
| 91.207.72.0/23 | 512 | RIPE NCC | DE | 3rd Oct 2019 |
| 91.207.9.0/24 | 256 | RIPE NCC | RU | 11th Sept 2008 |
| 91.207.94.0/23 | 512 | RIPE NCC | DE | 3rd Oct 2019 |