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.41.152.0/23 | 512 | RIPE NCC |  GB | 24th Nov 2000 |
| 193.41.158.0/23 | 512 | RIPE NCC |  BE | 6th Dec 2000 |
| 193.41.160.0/22 | 1k | RIPE NCC |  ES | 17th Mar 2010 |
| 193.41.182.0/23 | 512 | RIPE NCC |  BG | 17th Jan 2001 |
| 193.41.199.0/24 | 256 | RIPE NCC |  PL | 14th Nov 2019 |
| 193.41.2.0/23 | 512 | RIPE NCC |  TR | 11th Oct 2000 |
| 193.41.205.0/24 | 256 | RIPE NCC |  IT | 29th Dec 2000 |
| 193.41.229.0/24 | 256 | RIPE NCC |  GR | 11th Jan 2001 |
| 193.41.231.0/24 | 256 | RIPE NCC | PL | 16th Jan 2001 |
| 193.41.238.0/24 | 256 | RIPE NCC |  NO | 12th Jun 2023 |
| 193.41.248.0/24 | 256 | RIPE NCC |  US | 5th Jan 2001 |
| 193.41.249.0/24 | 256 | RIPE NCC |  DK | 5th Jan 2001 |
| 193.41.250.0/24 | 256 | RIPE NCC | US | 5th Jan 2001 |
| 193.41.33.0/24 | 256 | RIPE NCC |  LV | 12th Oct 2000 |
| 193.41.34.0/24 | 256 | RIPE NCC |  HU | 14th Nov 2019 |
| 193.41.46.0/24 | 256 | RIPE NCC |  SE | 20th Oct 2000 |
| 193.41.58.0/24 | 256 | RIPE NCC | DK | 6th Jan 2020 |
| 193.41.70.0/24 | 256 | RIPE NCC | HU | 14th Nov 2019 |
| 193.41.71.0/24 | 256 | RIPE NCC |  FR | 30th Oct 2000 |
| 193.41.80.0/24 | 256 | RIPE NCC |  UA | 2nd Nov 2000 |
| 193.41.81.0/24 | 256 | RIPE NCC |  LT | 7th Nov 2000 |
| 193.41.89.0/24 | 256 | RIPE NCC |  SI | 23rd Nov 2000 |
| 193.41.91.0/24 | 256 | RIPE NCC | PL | 14th Nov 2019 |
| 193.41.92.0/24 | 256 | RIPE NCC | PL | 14th Nov 2019 |
| 193.42.10.0/24 | 256 | RIPE NCC | FR | 9th Sept 1993 |
| 193.42.104.0/22 | 1k | RIPE NCC | UA | 23rd Oct 2018 |
| 193.42.13.0/24 | 256 | RIPE NCC | IT | 9th Dec 1993 |
| 193.42.133.0/24 | 256 | RIPE NCC | IT | 9th Mar 1994 |
| 193.42.140.0/23 | 512 | RIPE NCC | IT | 27th May 1994 |
| 193.42.143.0/24 | 256 | RIPE NCC | ES | 15th Sept 2008 |
| 193.42.144.0/24 | 256 | RIPE NCC | GB | 16th Sept 2008 |
| 193.42.147.0/24 | 256 | RIPE NCC | PL | 17th Sept 2008 |
| 193.42.155.0/24 | 256 | RIPE NCC |  DE | 18th Sept 2008 |
| 193.42.212.0/24 | 256 | RIPE NCC |  NL | 4th Jan 2005 |
| 193.42.216.0/24 | 256 | RIPE NCC | TR | 5th Jan 2005 |
| 193.42.28.0/22 | 1k | RIPE NCC | ES | 13th Sept 2018 |
| 193.42.8.0/23 | 512 | RIPE NCC | FR | 9th Sept 1993 |
| 193.43.0.0/26 | 64 | RIPE NCC | FR | 28th Aug 2012 |
| 193.43.0.128/25 | 128 | RIPE NCC | PL | 31st May 2012 |
| 193.43.0.64/27 | 32 | RIPE NCC |  CY | 14th Sept 2012 |
| 193.43.0.96/27 | 32 | RIPE NCC | GB | 11th May 2012 |
| 193.43.1.0/24 | 256 | RIPE NCC | IT | 3rd Feb 1995 |
| 193.43.111.0/24 | 256 | RIPE NCC |  CH | 15th Feb 1995 |
| 193.43.112.0/22 | 1k | RIPE NCC | CH | 15th Feb 1995 |
| 193.43.118.0/23 | 512 | RIPE NCC | DE | 9th Oct 2019 |
| 193.43.125.0/24 | 256 | RIPE NCC |  IE | 16th Dec 2004 |
| 193.43.137.0/24 | 256 | RIPE NCC | IT | 28th Mar 1994 |
| 193.43.142.0/23 | 512 | RIPE NCC |  AT | 9th Oct 2019 |
| 193.43.146.0/23 | 512 | RIPE NCC |  RU | 9th Oct 2019 |
| 193.43.181.0/24 | 256 | RIPE NCC | PL | 10th Dec 2004 |