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,312 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 195.47.231.0/24 | 256 | RIPE NCC |  CH | 7th May 2003 |
| 195.47.236.0/24 | 256 | RIPE NCC |  ES | 8th May 2003 |
| 195.47.240.0/24 | 256 | RIPE NCC |  GB | 14th May 2003 |
| 195.47.245.0/24 | 256 | RIPE NCC | CH | 19th May 2003 |
| 195.49.192.0/21 | 2k | RIPE NCC |  RU | 12th Dec 2002 |
| 195.5.105.0/24 | 256 | RIPE NCC | RU | 17th Oct 2023 |
| 195.5.162.0/24 | 256 | RIPE NCC |  KZ | 9th Apr 2008 |
| 195.5.169.0/24 | 256 | RIPE NCC | GB | 11th Apr 2008 |
| 195.5.175.0/24 | 256 | RIPE NCC | GB | 16th Apr 2008 |
| 195.5.178.0/24 | 256 | RIPE NCC | RU | 16th Apr 2008 |
| 195.5.183.0/24 | 256 | RIPE NCC |  NO | 18th Apr 2008 |
| 195.5.185.0/24 | 256 | RIPE NCC |  SE | 21st Apr 2008 |
| 195.5.188.0/24 | 256 | RIPE NCC |  AT | 21st Apr 2008 |
| 195.51.0.0/16 | 65.5k | RIPE NCC |  NL | 10th Dec 1996 |
| 195.54.180.0/23 | 512 | RIPE NCC |  KG | 10th Jun 2010 |
| 195.54.58.0/24 | 256 | RIPE NCC | AT | 20th Jul 2022 |
| 195.58.154.0/23 | 512 | RIPE NCC |  DE | 6th Nov 1996 |
| 195.58.224.0/19 | 8.2k | RIPE NCC |  UA | 27th Nov 1997 |
| 195.58.64.0/19 | 8.2k | RIPE NCC | GB | 13th Feb 1997 |
| 195.60.184.0/23 | 512 | RIPE NCC | UA | 13th Dec 2005 |
| 195.60.237.0/24 | 256 | RIPE NCC |  AE | 22nd Jul 2021 |
| 195.60.32.0/19 | 8.2k | RIPE NCC | DE | 17th Jun 1997 |
| 195.60.67.0/24 | 256 | RIPE NCC | AT | 18th Apr 2006 |
| 195.60.80.0/26 | 64 | RIPE NCC |  GR | 29th Feb 2024 |
| 195.60.80.128/27 | 32 | RIPE NCC |  AM | 14th Mar 2007 |
| 195.60.80.160/27 | 32 | RIPE NCC |  PL | 11th Apr 2007 |
| 195.60.80.192/27 | 32 | RIPE NCC | CH | 19th Nov 2007 |
| 195.60.80.224/27 | 32 | RIPE NCC |  PT | 11th Feb 2008 |
| 195.60.80.96/27 | 32 | RIPE NCC | PL | 21st Jun 2006 |
| 195.60.81.0/26 | 64 | RIPE NCC |  IQ | 3rd Sept 2025 |
| 195.60.81.192/26 | 64 | RIPE NCC |  CY | 14th Sept 2012 |
| 195.60.81.64/26 | 64 | RIPE NCC | ES | 19th Jul 2007 |
| 195.60.82.0/26 | 64 | RIPE NCC | CY | 14th Sept 2012 |
| 195.60.82.128/26 | 64 | RIPE NCC | NL | 5th Feb 2010 |
| 195.60.82.192/26 | 64 | RIPE NCC | GB | 2nd Mar 2010 |
| 195.60.82.64/26 | 64 | RIPE NCC |  IE | 10th Jun 2009 |
| 195.60.83.0/26 | 64 | RIPE NCC | DE | 26th Mar 2024 |
| 195.60.83.160/27 | 32 | RIPE NCC | CY | 14th Sept 2012 |
| 195.60.83.192/27 | 32 | RIPE NCC | GB | 18th Jan 2011 |
| 195.60.83.224/27 | 32 | RIPE NCC | NL | 16th Mar 2011 |
| 195.60.83.64/27 | 32 | RIPE NCC | CY | 14th Sept 2012 |
| 195.60.83.96/27 | 32 | RIPE NCC |  EE | 7th May 2010 |
| 195.60.84.0/25 | 128 | RIPE NCC | CY | 14th Sept 2012 |
| 195.60.84.128/26 | 64 | RIPE NCC |  IT | 23rd Feb 2026 |
| 195.60.84.192/26 | 64 | RIPE NCC |  LB | 9th Mar 2026 |
| 195.60.85.0/25 | 128 | RIPE NCC | GB | 14th Sept 2006 |
| 195.60.85.128/26 | 64 | RIPE NCC | NL | 18th Mar 2026 |
| 195.60.85.192/26 | 64 | RIPE NCC | AT | 20th Mar 2026 |
| 195.60.87.0/25 | 128 | RIPE NCC | NL | 26th Jun 2007 |
| 195.60.87.128/25 | 128 | RIPE NCC | CY | 14th Sept 2012 |