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 |
|---|---|---|---|---|
| 83.221.165.0/24 | 256 | RIPE NCC |  UZ | 15th Apr 2004 |
| 83.221.166.0/23 | 512 | RIPE NCC | UZ | 15th Apr 2004 |
| 83.221.182.0/24 | 256 | RIPE NCC | UZ | 15th Apr 2004 |
| 83.221.183.0/24 | 256 | RIPE NCC | UZ | 15th Apr 2004 |
| 83.229.16.0/24 | 256 | RIPE NCC |  RS | 13th May 2004 |
| 83.229.31.0/24 | 256 | RIPE NCC |  IL | 13th May 2004 |
| 83.241.0.0/17 | 32.8k | RIPE NCC |  LV | 19th Mar 2004 |
| 83.242.101.0/24 | 256 | RIPE NCC |  DK | 6th Jan 2025 |
| 83.242.103.0/24 | 256 | RIPE NCC |  RU | 12th Mar 2012 |
| 83.242.106.0/24 | 256 | RIPE NCC | RU | 12th Mar 2012 |
| 83.68.0.0/19 | 8.2k | RIPE NCC |  NL | 29th Apr 2004 |
| 83.94.64.0/19 | 8.2k | RIPE NCC |  GB | 1st Dec 2003 |
| 83.97.40.0/21 | 2k | RIPE NCC |  DE | 9th Feb 2004 |
| 83.97.48.0/21 | 2k | RIPE NCC | DE | 11th Feb 2004 |
| 83.98.160.0/22 | 1k | RIPE NCC | NL | 14th Jan 2004 |
| 83.98.165.0/24 | 256 | RIPE NCC | NL | 14th Jan 2004 |
| 84.18.160.0/19 | 8.2k | RIPE NCC | GB | 12th Aug 2004 |
| 84.19.104.0/21 | 2k | RIPE NCC | GB | 25th Aug 2004 |
| 84.201.208.0/20 | 4.1k | RIPE NCC |  US | 5th Jan 2005 |
| 84.201.224.0/20 | 4.1k | RIPE NCC |  BG | 14th Jan 2005 |
| 84.205.161.0/24 | 256 | RIPE NCC | GB | 3rd Feb 2005 |
| 84.205.167.0/24 | 256 | RIPE NCC |  PL | 3rd Feb 2005 |
| 84.205.180.0/23 | 512 | RIPE NCC | PL | 3rd Feb 2005 |
| 84.234.0.0/20 | 4.1k | RIPE NCC | PL | 6th Jul 2004 |
| 84.234.117.0/24 | 256 | RIPE NCC | PL | 24th Nov 2004 |
| 84.234.32.0/20 | 4.1k | RIPE NCC | PL | 16th Aug 2004 |
| 84.234.56.0/22 | 1k | RIPE NCC |  AT | 2nd Jul 2009 |
| 84.234.80.0/20 | 4.1k | RIPE NCC | DK | 22nd Nov 2004 |
| 84.240.104.0/21 | 2k | RIPE NCC |  FI | 3rd Jun 2004 |
| 84.240.112.0/20 | 4.1k | RIPE NCC | FI | 3rd Jun 2004 |
| 84.246.107.0/24 | 256 | RIPE NCC |  UA | 17th Aug 2021 |
| 84.246.194.0/23 | 512 | RIPE NCC |  EE | 18th Oct 2004 |
| 84.246.85.0/24 | 256 | RIPE NCC |  MD | 13th Aug 2021 |
| 84.246.96.0/21 | 2k | RIPE NCC |  HR | 5th Nov 2010 |
| 84.247.46.0/23 | 512 | RIPE NCC |  RO | 8th Oct 2004 |
| 84.252.106.0/24 | 256 | RIPE NCC |  JO | 20th Jan 2020 |
| 84.252.107.0/24 | 256 | RIPE NCC | NL | 20th Jan 2020 |
| 84.252.80.0/22 | 1k | RIPE NCC |  TR | 16th Nov 2018 |
| 84.254.122.0/24 | 256 | RIPE NCC | DE | 6th Oct 2004 |
| 84.254.123.0/24 | 256 | RIPE NCC | DE | 6th Oct 2004 |
| 84.38.0.0/24 | 256 | RIPE NCC | RU | 31st May 2012 |
| 84.38.1.0/24 | 256 | RIPE NCC |  KZ | 31st May 2012 |
| 84.38.112.0/20 | 4.1k | RIPE NCC | AT | 23rd May 2006 |
| 84.38.240.0/24 | 256 | RIPE NCC |  SI | 31st May 2023 |
| 84.38.248.0/24 | 256 | RIPE NCC |  FR | 5th Jun 2023 |
| 84.38.254.0/24 | 256 | RIPE NCC | GB | 6th Jun 2023 |
| 84.38.32.0/20 | 4.1k | RIPE NCC | GB | 13th Apr 2006 |
| 84.38.6.0/23 | 512 | RIPE NCC | RU | 31st May 2012 |
| 84.38.96.0/20 | 4.1k | RIPE NCC | PL | 22nd May 2006 |
| 84.39.184.0/21 | 2k | RIPE NCC | AT | 3rd Sept 2012 |