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.218.207.16/28 | 16 | RIPE NCC |  CH | 26th Jan 2011 |
| 193.218.207.32/27 | 32 | RIPE NCC | CH | 26th Jan 2011 |
| 193.218.207.80/28 | 16 | RIPE NCC |  CY | 14th Sept 2012 |
| 193.218.207.96/27 | 32 | RIPE NCC | CY | 14th Sept 2012 |
| 193.218.4.0/24 | 256 | RIPE NCC |  GR | 1st Dec 1994 |
| 193.218.41.0/24 | 256 | RIPE NCC | GR | 1st Dec 1994 |
| 193.218.42.0/24 | 256 | RIPE NCC | GR | 1st Dec 1994 |
| 193.218.43.0/24 | 256 | RIPE NCC |  TR | 18th Nov 2019 |
| 193.218.5.0/24 | 256 | RIPE NCC | GR | 6th Mar 1998 |
| 193.218.6.0/24 | 256 | RIPE NCC | GR | 6th Mar 1998 |
| 193.218.72.0/24 | 256 | RIPE NCC | GR | 1st Dec 1994 |
| 193.218.73.0/24 | 256 | RIPE NCC |  DE | 1st Dec 1994 |
| 193.218.74.0/23 | 512 | RIPE NCC | GR | 1st Dec 1994 |
| 193.218.76.0/22 | 1k | RIPE NCC | GR | 1st Dec 1994 |
| 193.218.82.0/23 | 512 | RIPE NCC |  FR | 16th Oct 2019 |
| 193.219.101.0/24 | 256 | RIPE NCC |  GB | 19th Nov 2019 |
| 193.219.103.0/24 | 256 | RIPE NCC |  ES | 27th Sept 2006 |
| 193.219.108.0/24 | 256 | RIPE NCC | GB | 27th Sept 2006 |
| 193.219.113.0/24 | 256 | RIPE NCC | DE | 29th Sept 2006 |
| 193.219.116.0/24 | 256 | RIPE NCC |  NL | 29th Sept 2006 |
| 193.219.122.0/24 | 256 | RIPE NCC |  IT | 16th Dec 2024 |
| 193.219.126.0/24 | 256 | RIPE NCC |  PL | 2nd Oct 2006 |
| 193.219.16.0/21 | 2k | RIPE NCC |  DK | 5th Jan 1998 |
| 193.219.24.0/22 | 1k | RIPE NCC | DK | 5th Jan 1998 |
| 193.219.29.0/24 | 256 | RIPE NCC | IT | 2nd Jun 2005 |
| 193.22.1.0/24 | 256 | RIPE NCC | GB | 13th Nov 2019 |
| 193.22.102.0/24 | 256 | RIPE NCC | NL | 17th Nov 2003 |
| 193.22.106.0/24 | 256 | RIPE NCC | GB | 13th Nov 2019 |
| 193.22.107.0/24 | 256 | RIPE NCC | FR | 10th Nov 2003 |
| 193.22.109.0/24 | 256 | RIPE NCC | DE | 29th Jul 1992 |
| 193.22.116.0/23 | 512 | RIPE NCC | DE | 29th Jul 1992 |
| 193.22.118.0/24 | 256 | RIPE NCC | DE | 29th Jul 1992 |
| 193.22.156.0/22 | 1k | RIPE NCC |  AT | 7th Sept 2018 |
| 193.22.160.0/24 | 256 | RIPE NCC | DE | 24th Oct 2025 |
| 193.22.163.0/24 | 256 | RIPE NCC | TR | 24th Oct 2025 |
| 193.22.168.0/24 | 256 | RIPE NCC |  SE | 13th Nov 2019 |
| 193.22.169.0/24 | 256 | RIPE NCC | PL | 6th Apr 2004 |
| 193.22.170.0/24 | 256 | RIPE NCC | SE | 13th Nov 2019 |
| 193.22.176.0/22 | 1k | RIPE NCC | DE | 29th Jul 1992 |
| 193.22.184.0/21 | 2k | RIPE NCC | DE | 29th Jul 1992 |
| 193.22.226.0/23 | 512 | RIPE NCC | FR | 7th Sept 2018 |
| 193.22.232.0/22 | 1k | RIPE NCC | DE | 7th Sept 2018 |
| 193.22.236.0/22 | 1k | RIPE NCC | DE | 7th Sept 2018 |
| 193.22.24.0/22 | 1k | RIPE NCC | DE | 25th Apr 2018 |
| 193.22.243.0/24 | 256 | RIPE NCC | GB | 25th Nov 2003 |
| 193.22.244.0/24 | 256 | RIPE NCC |  RU | 13th Nov 2019 |
| 193.22.30.0/24 | 256 | RIPE NCC | CY | 16th Dec 2003 |
| 193.22.5.0/24 | 256 | RIPE NCC |  FI | 18th Nov 2003 |
| 193.22.80.0/24 | 256 | RIPE NCC | GB | 13th Nov 2019 |
| 193.22.82.0/24 | 256 | RIPE NCC | AT | 16th Jun 2004 |