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.207.154.0/24 | 256 | RIPE NCC |  BE | 18th Sept 2023 |
| 89.207.156.0/24 | 256 | RIPE NCC |  DE | 7th Jan 2025 |
| 89.207.158.0/24 | 256 | RIPE NCC |  RU | 3rd Oct 2023 |
| 89.207.208.0/21 | 2k | RIPE NCC |  GB | 11th Jul 2006 |
| 89.207.32.0/21 | 2k | RIPE NCC | RU | 20th May 2009 |
| 89.207.40.0/21 | 2k | RIPE NCC | RU | 7th Jun 2006 |
| 89.207.96.0/21 | 2k | RIPE NCC | RU | 15th Jun 2006 |
| 89.208.123.0/24 | 256 | RIPE NCC |  KZ | 18th Apr 2006 |
| 89.219.4.0/22 | 1k | RIPE NCC | KZ | 5th Jul 2006 |
| 89.22.8.0/21 | 2k | RIPE NCC |  ES | 11th Jul 2011 |
| 89.221.144.0/20 | 4.1k | RIPE NCC |  IT | 6th Oct 2006 |
| 89.221.200.0/23 | 512 | RIPE NCC | RU | 9th Oct 2006 |
| 89.221.202.0/24 | 256 | RIPE NCC | RU | 9th Oct 2006 |
| 89.221.224.0/23 | 512 | RIPE NCC |  MD | 11th Oct 2006 |
| 89.221.72.0/21 | 2k | RIPE NCC |  EE | 26th Sept 2006 |
| 89.222.48.0/20 | 4.1k | RIPE NCC | GB | 7th Sept 2006 |
| 89.223.13.0/24 | 256 | RIPE NCC | RU | 19th Sept 2006 |
| 89.223.21.0/24 | 256 | RIPE NCC | RU | 19th Sept 2006 |
| 89.223.3.0/24 | 256 | RIPE NCC |  UZ | 19th Sept 2006 |
| 89.223.6.0/23 | 512 | RIPE NCC | RU | 19th Sept 2006 |
| 89.248.67.0/24 | 256 | RIPE NCC |  HR | 20th Aug 2021 |
| 89.248.69.0/24 | 256 | RIPE NCC |  SI | 20th Aug 2021 |
| 89.248.71.0/24 | 256 | RIPE NCC |  CY | 20th Aug 2021 |
| 89.249.144.0/20 | 4.1k | RIPE NCC | RU | 21st Jul 2006 |
| 89.249.32.0/21 | 2k | RIPE NCC |  CH | 18th Jul 2006 |
| 89.249.50.0/24 | 256 | RIPE NCC | RU | 19th Jul 2006 |
| 89.25.64.0/21 | 2k | RIPE NCC |  BG | 26th May 2006 |
| 89.25.72.0/22 | 1k | RIPE NCC | BG | 26th May 2006 |
| 89.251.4.0/22 | 1k | RIPE NCC | GB | 10th Sept 2019 |
| 89.254.0.0/21 | 2k | RIPE NCC |  NO | 30th Aug 2006 |
| 89.28.208.0/21 | 2k | RIPE NCC |  FI | 3rd Aug 2006 |
| 89.30.240.0/20 | 4.1k | RIPE NCC |  NL | 1st Sept 2006 |
| 89.31.208.0/22 | 1k | RIPE NCC | GB | 22nd Sept 2006 |
| 89.31.28.0/22 | 1k | RIPE NCC | GB | 21st Jun 2018 |
| 89.32.154.0/23 | 512 | RIPE NCC |  RO | 29th Nov 2005 |
| 89.32.168.0/23 | 512 | RIPE NCC | IT | 29th Nov 2005 |
| 89.32.172.0/22 | 1k | RIPE NCC | MD | 29th Nov 2005 |
| 89.32.198.0/23 | 512 | RIPE NCC | RO | 29th Nov 2005 |
| 89.32.201.0/24 | 256 | RIPE NCC |  TR | 29th Nov 2005 |
| 89.32.205.0/24 | 256 | RIPE NCC | TR | 29th Nov 2005 |
| 89.32.206.0/24 | 256 | RIPE NCC | RO | 29th Nov 2005 |
| 89.32.42.0/24 | 256 | RIPE NCC | NL | 29th Nov 2005 |
| 89.32.56.0/21 | 2k | RIPE NCC | MD | 29th Nov 2005 |
| 89.32.64.0/21 | 2k | RIPE NCC | ES | 29th Nov 2005 |
| 89.33.152.0/21 | 2k | RIPE NCC | RO | 29th Nov 2005 |
| 89.33.168.0/21 | 2k | RIPE NCC | RO | 29th Nov 2005 |
| 89.33.176.0/22 | 1k | RIPE NCC | RO | 29th Nov 2005 |
| 89.33.196.0/24 | 256 | RIPE NCC | RO | 29th Nov 2005 |
| 89.33.81.0/24 | 256 | RIPE NCC | NL | 29th Nov 2005 |
| 89.33.87.0/24 | 256 | RIPE NCC |  IR | 29th Nov 2005 |