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.163.197.0/24 | 256 | RIPE NCC |  RU | 28th Sept 2021 |
| 193.163.216.0/22 | 1k | RIPE NCC |  DK | 10th Aug 1994 |
| 193.163.33.0/24 | 256 | RIPE NCC | DK | 10th Aug 1994 |
| 193.163.50.0/23 | 512 | RIPE NCC | DK | 10th Aug 1994 |
| 193.163.64.0/22 | 1k | RIPE NCC | DK | 10th Aug 1994 |
| 193.163.68.0/24 | 256 | RIPE NCC | DK | 10th Aug 1994 |
| 193.163.69.0/24 | 256 | RIPE NCC | DK | 10th Aug 1994 |
| 193.163.73.0/24 | 256 | RIPE NCC |  IR | 16th Jun 2026 |
| 193.163.75.0/24 | 256 | RIPE NCC |  IL | 20th Aug 2020 |
| 193.163.9.0/24 | 256 | RIPE NCC | DK | 10th Aug 1994 |
| 193.163.94.0/24 | 256 | RIPE NCC | RU | 16th Sept 2021 |
| 193.164.1.0/24 | 256 | RIPE NCC |  LT | 18th Nov 2019 |
| 193.164.11.0/24 | 256 | RIPE NCC |  GB | 18th Apr 2005 |
| 193.164.129.0/24 | 256 | RIPE NCC |  PL | 15th Aug 2006 |
| 193.164.192.0/23 | 512 | RIPE NCC |  NL | 20th Aug 2009 |
| 193.164.194.0/23 | 512 | RIPE NCC | RU | 20th Aug 2009 |
| 193.164.199.0/24 | 256 | RIPE NCC |  SC | 10th Dec 2019 |
| 193.164.220.0/23 | 512 | RIPE NCC |  IE | 26th Aug 2009 |
| 193.164.226.0/23 | 512 | RIPE NCC |  ES | 8th Jun 2000 |
| 193.164.232.0/26 | 64 | RIPE NCC |  FR | 26th Jun 2000 |
| 193.164.232.160/27 | 32 | RIPE NCC |  CY | 14th Sept 2012 |
| 193.164.232.192/27 | 32 | RIPE NCC | FR | 9th Mar 2006 |
| 193.164.232.64/27 | 32 | RIPE NCC | FR | 26th Jun 2000 |
| 193.164.233.0/24 | 256 | RIPE NCC | GB | 27th Jun 2000 |
| 193.164.234.0/23 | 512 | RIPE NCC |  AT | 6th Jul 2000 |
| 193.164.240.0/23 | 512 | RIPE NCC | AT | 6th Jul 2000 |
| 193.164.244.0/23 | 512 | RIPE NCC |  CH | 14th Jul 2000 |
| 193.164.32.0/19 | 8.2k | RIPE NCC |  CZ | 14th Mar 1996 |
| 193.164.64.0/20 | 4.1k | RIPE NCC | CZ | 14th Mar 1996 |
| 193.168.132.0/22 | 1k | RIPE NCC |  IT | 11th Dec 2018 |
| 193.168.16.0/20 | 4.1k | RIPE NCC |  LU | 26th Nov 1992 |
| 193.168.165.0/24 | 256 | RIPE NCC | CH | 5th May 2026 |
| 193.168.167.0/24 | 256 | RIPE NCC | GB | 5th May 2026 |
| 193.168.180.0/22 | 1k | RIPE NCC |  BZ | 11th Dec 2018 |
| 193.168.2.0/24 | 256 | RIPE NCC | LU | 11th Nov 1994 |
| 193.168.217.0/24 | 256 | RIPE NCC | RU | 6th May 2021 |
| 193.168.244.0/22 | 1k | RIPE NCC | CZ | 12th Dec 2018 |
| 193.169.10.0/23 | 512 | RIPE NCC |  DE | 8th May 2009 |
| 193.169.120.0/23 | 512 | RIPE NCC | GB | 1st Jul 2009 |
| 193.169.140.0/23 | 512 | RIPE NCC | GB | 14th Jul 2009 |
| 193.169.152.0/23 | 512 | RIPE NCC | CH | 20th Jul 2009 |
| 193.169.194.0/23 | 512 | RIPE NCC |  LV | 28th Jul 2009 |
| 193.169.198.0/23 | 512 | RIPE NCC |  BG | 30th Jul 2009 |
| 193.169.234.0/23 | 512 | RIPE NCC | NL | 31st Mar 2011 |
| 193.169.236.0/23 | 512 | RIPE NCC | GB | 14th Jan 2011 |
| 193.169.242.0/23 | 512 | RIPE NCC | IT | 13th Aug 2009 |
| 193.169.252.0/22 | 1k | RIPE NCC | PL | 8th May 2018 |
| 193.169.31.0/24 | 256 | RIPE NCC | BG | 22nd May 2009 |
| 193.169.58.0/24 | 256 | RIPE NCC | IT | 12th Sept 2022 |
| 193.169.84.0/23 | 512 | RIPE NCC |  FI | 18th Jun 2009 |