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,283 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 193.238.40.0/22 | 1k | RIPE NCC |  PL | 17th Feb 2005 |
| 193.238.45.0/24 | 256 | RIPE NCC |  RU | 11th May 2018 |
| 193.238.96.0/22 | 1k | RIPE NCC |  UA | 4th Mar 2005 |
| 193.239.112.0/22 | 1k | RIPE NCC |  GB | 4th Jul 2005 |
| 193.239.116.0/22 | 1k | RIPE NCC |  NL | 11th Jul 2005 |
| 193.239.138.0/23 | 512 | RIPE NCC |  RO | 8th Apr 2008 |
| 193.239.148.0/23 | 512 | RIPE NCC |  HU | 8th Jun 2005 |
| 193.239.156.0/23 | 512 | RIPE NCC |  DE | 10th Jun 2005 |
| 193.239.196.0/24 | 256 | RIPE NCC |  ES | 17th Oct 2019 |
| 193.239.224.0/23 | 512 | RIPE NCC | PL | 13th Jul 2005 |
| 193.239.229.0/24 | 256 | RIPE NCC | RU | 27th Nov 2024 |
| 193.239.250.0/23 | 512 | RIPE NCC | UA | 2nd Aug 2005 |
| 193.24.103.0/24 | 256 | RIPE NCC |  IR | 2nd Jul 2024 |
| 193.24.104.0/24 | 256 | RIPE NCC |  GR | 2nd Jul 2024 |
| 193.24.112.0/24 | 256 | RIPE NCC | NL | 2nd Jul 2024 |
| 193.24.113.0/24 | 256 | RIPE NCC | GB | 2nd Jul 2024 |
| 193.24.115.0/24 | 256 | RIPE NCC |  SE | 2nd Jul 2024 |
| 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 |  CY | 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 |