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.108.98.0/23 | 512 | RIPE NCC |  NL | 25th Apr 2001 |
| 193.109.116.0/24 | 256 | RIPE NCC |  ES | 18th Sept 2001 |
| 193.109.117.0/24 | 256 | RIPE NCC |  FR | 19th Sept 2001 |
| 193.109.12.0/22 | 1k | RIPE NCC |  GB | 4th May 2018 |
| 193.109.127.0/24 | 256 | RIPE NCC |  PL | 4th Oct 2001 |
| 193.109.148.0/22 | 1k | RIPE NCC |  AT | 27th Sept 2001 |
| 193.109.160.0/22 | 1k | RIPE NCC |  RU | 3rd Oct 2001 |
| 193.109.168.0/22 | 1k | RIPE NCC |  UA | 4th May 2018 |
| 193.109.210.0/24 | 256 | RIPE NCC |  NO | 5th Oct 2001 |
| 193.109.211.0/24 | 256 | RIPE NCC |  LV | 5th Oct 2001 |
| 193.109.221.0/24 | 256 | RIPE NCC |  SC | 15th Nov 2019 |
| 193.109.223.0/24 | 256 | RIPE NCC |  DE | 13th Jan 2009 |
| 193.109.233.0/24 | 256 | RIPE NCC |  IT | 23rd Nov 2001 |
| 193.109.236.0/24 | 256 | RIPE NCC | DE | 26th Nov 2001 |
| 193.109.254.0/23 | 512 | RIPE NCC | GB | 5th Nov 2001 |
| 193.109.50.0/23 | 512 | RIPE NCC | GB | 25th Jul 2001 |
| 193.109.56.0/24 | 256 | RIPE NCC |  IR | 5th Jun 2023 |
| 193.109.64.0/23 | 512 | RIPE NCC | NL | 10th Oct 2019 |
| 193.109.83.0/24 | 256 | RIPE NCC | FR | 17th Aug 2001 |
| 193.110.0.0/22 | 1k | RIPE NCC | RU | 4th May 2018 |
| 193.110.108.0/23 | 512 | RIPE NCC |  FI | 14th Dec 2001 |
| 193.110.116.0/22 | 1k | RIPE NCC | DE | 21st Dec 2001 |
| 193.110.12.0/23 | 512 | RIPE NCC |  SE | 27th Nov 2001 |
| 193.110.124.0/22 | 1k | RIPE NCC | UA | 8th Jan 2002 |
| 193.110.138.0/24 | 256 | RIPE NCC |  US | 14th Jan 2002 |
| 193.110.148.0/24 | 256 | RIPE NCC | NL | 15th Nov 2019 |
| 193.110.158.0/24 | 256 | RIPE NCC | NL | 15th Nov 2019 |
| 193.110.166.0/23 | 512 | RIPE NCC |  DK | 14th Jan 2002 |
| 193.110.170.0/23 | 512 | RIPE NCC |  TR | 15th Jan 2002 |
| 193.110.176.0/23 | 512 | RIPE NCC | UA | 8th Jan 2002 |
| 193.110.20.0/22 | 1k | RIPE NCC |  CH | 9th Nov 2001 |
| 193.110.224.0/22 | 1k | RIPE NCC | FI | 1st Feb 2002 |
| 193.110.64.0/22 | 1k | RIPE NCC | FI | 23rd Nov 2001 |
| 193.110.81.0/24 | 256 | RIPE NCC | US | 11th Oct 2021 |
| 193.110.88.0/24 | 256 | RIPE NCC | GB | 13th Dec 2001 |
| 193.111.14.0/23 | 512 | RIPE NCC | FR | 19th Feb 2002 |
| 193.111.164.0/24 | 256 | RIPE NCC |  HR | 24th Apr 2002 |
| 193.111.192.0/23 | 512 | RIPE NCC |  SI | 26th Apr 2002 |
| 193.111.206.0/23 | 512 | RIPE NCC | DE | 5th Jun 2002 |
| 193.111.232.0/24 | 256 | RIPE NCC |  RO | 15th May 2002 |
| 193.111.239.0/24 | 256 | RIPE NCC | UA | 22nd May 2002 |
| 193.111.36.0/24 | 256 | RIPE NCC | PL | 5th Mar 2002 |
| 193.111.4.0/23 | 512 | RIPE NCC | SC | 11th Oct 2019 |
| 193.111.41.0/24 | 256 | RIPE NCC | PL | 8th Mar 2002 |
| 193.111.44.0/24 | 256 | RIPE NCC | DE | 12th Mar 2002 |
| 193.111.68.0/23 | 512 | RIPE NCC | RO | 24th Nov 2005 |
| 193.111.81.0/24 | 256 | RIPE NCC | NL | 22nd Mar 2002 |
| 193.111.84.0/24 | 256 | RIPE NCC | ES | 3rd Apr 2002 |
| 193.114.160.0/19 | 8.2k | RIPE NCC | GB | 10th Feb 1994 |
| 193.118.176.0/21 | 2k | RIPE NCC | GB | 10th Feb 1994 |