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 |
|---|---|---|---|---|
| 89.46.56.0/22 | 1k | RIPE NCC |  ES | 29th Nov 2005 |
| 89.47.1.0/24 | 256 | RIPE NCC |  NL | 29th Nov 2005 |
| 89.47.11.0/24 | 256 | RIPE NCC |  DK | 29th Nov 2005 |
| 89.47.13.0/24 | 256 | RIPE NCC |  US | 29th Nov 2005 |
| 89.47.168.0/23 | 512 | RIPE NCC |  LT | 29th Nov 2005 |
| 89.47.170.0/24 | 256 | RIPE NCC | LT | 29th Nov 2005 |
| 89.47.2.0/24 | 256 | RIPE NCC | US | 29th Nov 2005 |
| 89.47.204.0/22 | 1k | RIPE NCC | ES | 29th Nov 2005 |
| 89.47.244.0/23 | 512 | RIPE NCC |  RO | 29th Nov 2005 |
| 89.47.35.0/24 | 256 | RIPE NCC |  TR | 29th Nov 2005 |
| 89.47.37.0/24 | 256 | RIPE NCC | LT | 29th Nov 2005 |
| 89.47.60.0/23 | 512 | RIPE NCC | RO | 29th Nov 2005 |
| 89.47.91.0/24 | 256 | RIPE NCC | RO | 29th Nov 2005 |
| 9.137.0.0/16 | 65.5k | RIPE NCC |  AE | 16th Dec 1988 |
| 9.153.0.0/16 | 65.5k | RIPE NCC | AE | 16th Dec 1988 |
| 9.162.0.0/16 | 65.5k | RIPE NCC |  SA | 16th Dec 1988 |
| 9.171.0.0/16 | 65.5k | RIPE NCC | AE | 16th Dec 1988 |
| 9.178.0.0/16 | 65.5k | RIPE NCC | AE | 16th Dec 1988 |
| 9.199.0.0/16 | 65.5k | RIPE NCC | AE | 16th Dec 1988 |
| 9.210.0.0/15 | 131k | RIPE NCC |  DE | 16th Dec 1988 |
| 9.212.0.0/16 | 65.5k | RIPE NCC | SA | 16th Dec 1988 |
| 9.236.0.0/16 | 65.5k | RIPE NCC | US | 16th Dec 1988 |
| 9.240.0.0/15 | 131k | RIPE NCC | US | 16th Dec 1988 |
| 9.250.0.0/15 | 131k | RIPE NCC | SA | 16th Dec 1988 |
| 90.156.176.0/20 | 4.1k | RIPE NCC |  RU | 17th Nov 2006 |
| 90.96.0.0/16 | 65.5k | RIPE NCC | US | 2nd Mar 2006 |
| 90.97.128.0/17 | 32.8k | RIPE NCC |  FR | 2nd Mar 2006 |
| 91.102.121.0/24 | 256 | RIPE NCC | DE | 31st Mar 2026 |
| 91.102.122.0/24 | 256 | RIPE NCC |  EE | 8th Apr 2026 |
| 91.102.123.0/24 | 256 | RIPE NCC | NL | 13th Apr 2026 |
| 91.102.124.0/24 | 256 | RIPE NCC |  AL | 13th Apr 2026 |
| 91.102.125.0/24 | 256 | RIPE NCC | ES | 13th Apr 2026 |
| 91.102.16.0/21 | 2k | RIPE NCC | SA | 10th Oct 2006 |
| 91.102.168.0/21 | 2k | RIPE NCC |  RS | 1st Nov 2006 |
| 91.103.108.0/23 | 512 | RIPE NCC | LT | 24th Nov 2006 |
| 91.103.136.0/24 | 256 | RIPE NCC |  GB | 12th Jan 2024 |
| 91.103.216.0/21 | 2k | RIPE NCC | DE | 6th Dec 2006 |
| 91.103.88.0/21 | 2k | RIPE NCC |  MT | 24th Nov 2006 |
| 91.105.194.0/23 | 512 | RIPE NCC | RU | 13th Aug 2012 |
| 91.105.208.0/21 | 2k | RIPE NCC |  UA | 13th Aug 2012 |
| 91.105.224.0/21 | 2k | RIPE NCC | GB | 20th Jun 2012 |
| 91.107.104.0/21 | 2k | RIPE NCC | RU | 21st Jun 2012 |
| 91.107.119.0/24 | 256 | RIPE NCC | RU | 21st Jun 2012 |
| 91.108.185.0/24 | 256 | RIPE NCC |  CZ | 12th Jan 2024 |
| 91.108.186.0/24 | 256 | RIPE NCC | LT | 12th Jan 2024 |
| 91.108.191.0/24 | 256 | RIPE NCC | NL | 7th Jan 2025 |
| 91.109.217.0/24 | 256 | RIPE NCC |  AF | 19th Jun 2012 |
| 91.109.219.0/24 | 256 | RIPE NCC | AF | 19th Jun 2012 |
| 91.109.220.0/22 | 1k | RIPE NCC | AF | 19th Jun 2012 |
| 91.109.96.0/21 | 2k | RIPE NCC | ES | 18th Jun 2012 |