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
24,902 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 91.212.207.0/24 | 256 | RIPE NCC |  SE | 13th May 2009 |
| 91.212.210.0/24 | 256 | RIPE NCC |  GB | 15th May 2009 |
| 91.212.222.0/24 | 256 | RIPE NCC |  NL | 27th May 2009 |
| 91.212.235.0/24 | 256 | RIPE NCC |  BG | 3rd Jun 2009 |
| 91.212.239.0/24 | 256 | RIPE NCC |  RU | 4th Jun 2009 |
| 91.212.247.0/24 | 256 | RIPE NCC |  HR | 5th Jun 2009 |
| 91.212.28.0/24 | 256 | RIPE NCC |  DK | 2nd Feb 2009 |
| 91.212.49.0/24 | 256 | RIPE NCC |  AE | 8th Nov 2019 |
| 91.212.51.0/24 | 256 | RIPE NCC | AE | 8th Nov 2019 |
| 91.212.56.0/24 | 256 | RIPE NCC |  UA | 12th Feb 2009 |
| 91.212.57.0/24 | 256 | RIPE NCC | RU | 12th Feb 2009 |
| 91.212.58.0/24 | 256 | RIPE NCC |  FR | 12th Feb 2009 |
| 91.212.59.0/24 | 256 | RIPE NCC |  PT | 16th Sept 2024 |
| 91.212.62.0/24 | 256 | RIPE NCC |  RO | 16th Feb 2009 |
| 91.212.65.0/24 | 256 | RIPE NCC | AE | 8th Nov 2019 |
| 91.212.7.0/24 | 256 | RIPE NCC | RU | 27th Jan 2009 |
| 91.212.74.0/24 | 256 | RIPE NCC | RO | 18th Feb 2009 |
| 91.212.88.0/24 | 256 | RIPE NCC |  AG | 10th Jun 2020 |
| 91.212.9.0/24 | 256 | RIPE NCC |  PL | 27th Jan 2009 |
| 91.212.97.0/24 | 256 | RIPE NCC | RU | 25th Mar 2009 |
| 91.213.0.0/24 | 256 | RIPE NCC | SE | 9th Jun 2009 |
| 91.213.105.0/24 | 256 | RIPE NCC |  LV | 30th Jul 2009 |
| 91.213.111.0/24 | 256 | RIPE NCC | NL | 8th Nov 2019 |
| 91.213.118.0/24 | 256 | RIPE NCC |  TR | 21st Aug 2024 |
| 91.213.12.0/24 | 256 | RIPE NCC | BG | 16th Jun 2009 |
| 91.213.128.0/24 | 256 | RIPE NCC |  CH | 6th Aug 2009 |
| 91.213.129.0/24 | 256 | RIPE NCC |  IT | 6th Aug 2009 |
| 91.213.134.0/24 | 256 | RIPE NCC |  US | 30th May 2025 |
| 91.213.147.0/24 | 256 | RIPE NCC |  SI | 11th Aug 2009 |
| 91.213.154.0/24 | 256 | RIPE NCC | UA | 13th Aug 2009 |
| 91.213.155.0/24 | 256 | RIPE NCC |  HK | 9th Aug 2021 |
| 91.213.159.0/24 | 256 | RIPE NCC | CH | 17th Aug 2009 |
| 91.213.17.0/24 | 256 | RIPE NCC |  DE | 23rd Aug 2021 |
| 91.213.171.0/24 | 256 | RIPE NCC | CH | 19th Aug 2009 |
| 91.213.183.0/24 | 256 | RIPE NCC | GB | 25th Aug 2009 |
| 91.213.206.0/24 | 256 | RIPE NCC | PL | 7th Sept 2009 |
| 91.213.209.0/24 | 256 | RIPE NCC | UA | 10th Aug 2012 |
| 91.213.211.0/26 | 64 | RIPE NCC | AE | 9th Apr 2026 |
| 91.213.211.128/26 | 64 | RIPE NCC | NL | 3rd Jun 2026 |
| 91.213.211.192/26 | 64 | RIPE NCC |  OM | 6th Jul 2026 |
| 91.213.211.64/26 | 64 | RIPE NCC |  IL | 28th May 2026 |
| 91.213.214.0/24 | 256 | RIPE NCC | US | 9th Sept 2009 |
| 91.213.216.0/24 | 256 | RIPE NCC | GB | 14th Sept 2009 |
| 91.213.228.0/24 | 256 | RIPE NCC |  GR | 17th Sept 2009 |
| 91.213.236.0/24 | 256 | RIPE NCC | FR | 22nd Sept 2009 |
| 91.213.250.0/24 | 256 | RIPE NCC | SE | 25th Sept 2009 |
| 91.213.255.0/24 | 256 | RIPE NCC | PL | 28th Sept 2009 |
| 91.213.3.0/24 | 256 | RIPE NCC | US | 10th Jun 2009 |
| 91.213.42.0/24 | 256 | RIPE NCC | GB | 2nd Jul 2009 |
| 91.213.45.0/24 | 256 | RIPE NCC | GB | 6th Jul 2009 |