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 the most unannounced blocks, largest first.
Unannounced blocks
85,239 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 193.24.117.0/24 | 256 | RIPE NCC |  TR | 2nd Jul 2024 |
| 193.24.118.0/24 | 256 | RIPE NCC |  IR | 2nd Jul 2024 |
| 193.24.224.0/22 | 1k | RIPE NCC |  DE | 16th Feb 2004 |
| 193.24.240.0/22 | 1k | RIPE NCC |  BG | 20th Feb 2004 |
| 193.24.26.0/24 | 256 | RIPE NCC |  CH | 9th Mar 2004 |
| 193.24.32.0/22 | 1k | RIPE NCC | DE | 22nd Jan 1993 |
| 193.24.4.0/23 | 512 | RIPE NCC |  LT | 7th Oct 2019 |
| 193.24.98.0/24 | 256 | RIPE NCC |  KZ | 2nd Jul 2024 |
| 193.24.99.0/24 | 256 | RIPE NCC | TR | 2nd Jul 2024 |
| 193.242.0.0/24 | 256 | RIPE NCC |  GB | 10th Apr 1997 |
| 193.242.1.0/24 | 256 | RIPE NCC |  FR | 26th Jul 1993 |
| 193.242.103.0/24 | 256 | RIPE NCC |  SE | 23rd Nov 2004 |
| 193.242.104.0/24 | 256 | RIPE NCC |  CZ | 30th Oct 2024 |
| 193.242.106.0/24 | 256 | RIPE NCC |  RU | 19th Nov 2019 |
| 193.242.109.0/24 | 256 | RIPE NCC | RU | 19th Nov 2019 |
| 193.242.110.0/24 | 256 | RIPE NCC | GB | 29th Nov 2004 |
| 193.242.119.0/24 | 256 | RIPE NCC |  NL | 22nd Dec 2004 |
| 193.242.126.0/24 | 256 | RIPE NCC |  FI | 29th Dec 2004 |
| 193.242.140.0/24 | 256 | RIPE NCC | GB | 20th Jun 2012 |
| 193.242.153.0/24 | 256 | RIPE NCC | RU | 19th Nov 2019 |
| 193.242.166.0/24 | 256 | RIPE NCC |  UA | 21st Jun 2012 |
| 193.242.180.0/24 | 256 | RIPE NCC |  AE | 25th Jan 2023 |
| 193.242.182.0/24 | 256 | RIPE NCC | SE | 21st Jun 2012 |
| 193.242.2.0/23 | 512 | RIPE NCC | FR | 26th Jul 1993 |
| 193.242.220.0/24 | 256 | RIPE NCC | CH | 15th Apr 2024 |
| 193.242.221.0/24 | 256 | RIPE NCC |  DK | 15th Apr 2024 |
| 193.242.64.0/20 | 4.1k | RIPE NCC | FR | 26th Jul 1993 |
| 193.242.98.0/24 | 256 | RIPE NCC |  ES | 17th Nov 2004 |
| 193.243.0.0/17 | 32.8k | RIPE NCC | GB | 16th Aug 1993 |
| 193.243.128.0/24 | 256 | RIPE NCC | SE | 7th Apr 2020 |
| 193.243.134.0/23 | 512 | RIPE NCC | DE | 17th Oct 2019 |
| 193.243.161.0/24 | 256 | RIPE NCC | RU | 19th Nov 2019 |
| 193.243.167.0/24 | 256 | RIPE NCC | GB | 7th May 2024 |
| 193.243.176.0/22 | 1k | RIPE NCC | GB | 19th Jun 1998 |
| 193.243.180.0/23 | 512 | RIPE NCC | GB | 19th Jun 1998 |
| 193.243.182.0/24 | 256 | RIPE NCC | RU | 19th Nov 2019 |
| 193.243.183.0/26 | 64 | RIPE NCC |  GE | 7th Feb 2024 |
| 193.243.183.128/26 | 64 | RIPE NCC | GB | 8th Feb 2024 |
| 193.243.183.192/26 | 64 | RIPE NCC | SE | 3rd Apr 2006 |
| 193.243.183.64/26 | 64 | RIPE NCC | SE | 3rd Feb 2006 |
| 193.246.101.0/24 | 256 | RIPE NCC | CH | 28th May 1997 |
| 193.246.108.0/23 | 512 | RIPE NCC | CH | 28th May 1997 |
| 193.246.120.0/24 | 256 | RIPE NCC | CH | 28th May 1997 |
| 193.246.123.0/24 | 256 | RIPE NCC | CH | 28th May 1997 |
| 193.246.126.0/24 | 256 | RIPE NCC |  AT | 28th May 1997 |
| 193.246.128.0/20 | 4.1k | RIPE NCC | CH | 28th May 1997 |
| 193.246.145.0/24 | 256 | RIPE NCC | CH | 28th May 1997 |
| 193.246.151.0/24 | 256 | RIPE NCC | CH | 28th May 1997 |
| 193.246.152.0/24 | 256 | RIPE NCC | CH | 28th May 1997 |
| 193.246.153.0/24 | 256 | RIPE NCC | RU | 19th Nov 2019 |