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.208.1.0/24 | 256 | RIPE NCC |  GB | 25th Jun 2008 |
| 91.208.10.0/24 | 256 | RIPE NCC |  PL | 1st Jul 2008 |
| 91.208.105.0/24 | 256 | RIPE NCC | GB | 4th Aug 2008 |
| 91.208.106.0/24 | 256 | RIPE NCC | PL | 4th Aug 2008 |
| 91.208.110.0/24 | 256 | RIPE NCC |  NL | 7th Aug 2008 |
| 91.208.112.0/24 | 256 | RIPE NCC |  CZ | 26th Sept 2022 |
| 91.208.117.0/24 | 256 | RIPE NCC | GB | 8th Aug 2008 |
| 91.208.118.0/24 | 256 | RIPE NCC |  IL | 8th Aug 2008 |
| 91.208.119.0/24 | 256 | RIPE NCC |  RU | 8th Aug 2008 |
| 91.208.12.0/24 | 256 | RIPE NCC |  BE | 1st Jul 2008 |
| 91.208.124.0/24 | 256 | RIPE NCC | GB | 11th Aug 2008 |
| 91.208.128.0/24 | 256 | RIPE NCC |  HR | 7th Nov 2019 |
| 91.208.132.0/24 | 256 | RIPE NCC | RU | 13th Aug 2008 |
| 91.208.137.0/24 | 256 | RIPE NCC | HR | 7th Nov 2019 |
| 91.208.14.0/24 | 256 | RIPE NCC |  IT | 2nd Jul 2008 |
| 91.208.140.0/24 | 256 | RIPE NCC | IL | 14th Aug 2008 |
| 91.208.146.0/24 | 256 | RIPE NCC | HR | 17th Aug 2026 |
| 91.208.147.0/24 | 256 | RIPE NCC | IL | 18th Aug 2008 |
| 91.208.151.0/24 | 256 | RIPE NCC | HR | 7th Nov 2019 |
| 91.208.152.0/24 | 256 | RIPE NCC | IT | 19th Aug 2008 |
| 91.208.153.0/24 | 256 | RIPE NCC |  UA | 19th Aug 2008 |
| 91.208.156.0/24 | 256 | RIPE NCC |  SA | 20th Aug 2008 |
| 91.208.169.0/24 | 256 | RIPE NCC |  AT | 27th Aug 2008 |
| 91.208.176.0/23 | 512 | RIPE NCC | PL | 3rd Oct 2019 |
| 91.208.180.0/24 | 256 | RIPE NCC |  CH | 1st Sept 2008 |
| 91.208.190.0/24 | 256 | RIPE NCC | GB | 13th Apr 2026 |
| 91.208.196.0/24 | 256 | RIPE NCC | NL | 9th Sept 2008 |
| 91.208.203.0/24 | 256 | RIPE NCC |  KW | 11th Sept 2008 |
| 91.208.212.0/24 | 256 | RIPE NCC |  LU | 17th Dec 2025 |
| 91.208.218.0/24 | 256 | RIPE NCC | IL | 22nd Sept 2008 |
| 91.208.220.0/24 | 256 | RIPE NCC | BE | 29th Sept 2008 |
| 91.208.234.0/24 | 256 | RIPE NCC |  RO | 25th Sept 2008 |
| 91.208.236.0/24 | 256 | RIPE NCC |  US | 7th Nov 2019 |
| 91.208.240.0/24 | 256 | RIPE NCC | US | 7th Nov 2019 |
| 91.208.241.0/24 | 256 | RIPE NCC | NL | 26th Sept 2008 |
| 91.208.245.0/24 | 256 | RIPE NCC | US | 7th Nov 2019 |
| 91.208.246.0/24 | 256 | RIPE NCC | US | 7th Nov 2019 |
| 91.208.30.0/24 | 256 | RIPE NCC | CH | 7th Jul 2008 |
| 91.208.46.0/24 | 256 | RIPE NCC |  DE | 7th Nov 2019 |
| 91.208.48.0/24 | 256 | RIPE NCC | DE | 7th Nov 2019 |
| 91.208.49.0/24 | 256 | RIPE NCC | NL | 11th Jul 2008 |
| 91.208.63.0/24 | 256 | RIPE NCC |  BG | 16th May 2012 |
| 91.208.64.0/24 | 256 | RIPE NCC | DE | 7th Nov 2019 |
| 91.208.67.0/24 | 256 | RIPE NCC | NL | 27th Sept 2023 |
| 91.208.69.0/24 | 256 | RIPE NCC | US | 7th Nov 2019 |
| 91.208.70.0/24 | 256 | RIPE NCC |  TR | 21st Jul 2008 |
| 91.208.77.0/24 | 256 | RIPE NCC | NL | 15th May 2023 |
| 91.208.90.0/24 | 256 | RIPE NCC | RO | 30th Jul 2008 |
| 91.208.91.0/24 | 256 | RIPE NCC | US | 30th Jul 2008 |
| 91.208.99.0/24 | 256 | RIPE NCC | DE | 1st Aug 2008 |