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.234.97.0/24 | 256 | RIPE NCC |  RU | 23rd Feb 2009 |
| 195.238.172.0/22 | 1k | RIPE NCC |  DE | 21st Jun 2006 |
| 195.238.225.0/24 | 256 | RIPE NCC |  GB | 8th Jan 2025 |
| 195.238.237.0/24 | 256 | RIPE NCC | GB | 9th Mar 2005 |
| 195.238.239.0/24 | 256 | RIPE NCC | RU | 10th Mar 2005 |
| 195.238.248.0/24 | 256 | RIPE NCC |  BG | 25th Nov 2019 |
| 195.238.249.0/24 | 256 | RIPE NCC | GB | 18th Mar 2005 |
| 195.238.66.0/23 | 512 | RIPE NCC |  PL | 13th Jan 2006 |
| 195.238.68.0/23 | 512 | RIPE NCC |  NL | 6th Nov 2019 |
| 195.238.70.0/23 | 512 | RIPE NCC | PL | 13th Jan 2006 |
| 195.238.78.0/23 | 512 | RIPE NCC | NL | 6th Nov 2019 |
| 195.24.230.0/23 | 512 | RIPE NCC | GB | 4th Apr 2008 |
| 195.24.238.0/23 | 512 | RIPE NCC |  RO | 14th Apr 2008 |
| 195.24.250.0/23 | 512 | RIPE NCC | GB | 21st Apr 2008 |
| 195.24.252.0/23 | 512 | RIPE NCC |  UA | 22nd Apr 2008 |
| 195.242.120.0/23 | 512 | RIPE NCC |  DK | 23rd Dec 2004 |
| 195.242.136.0/23 | 512 | RIPE NCC |  ES | 6th Dec 2006 |
| 195.242.154.0/23 | 512 | RIPE NCC | GB | 12th Dec 2006 |
| 195.242.158.0/23 | 512 | RIPE NCC | RO | 12th Dec 2006 |
| 195.242.160.0/24 | 256 | RIPE NCC | DK | 17th Jun 2008 |
| 195.242.161.0/24 | 256 | RIPE NCC | UA | 17th Jun 2008 |
| 195.242.168.0/24 | 256 | RIPE NCC |  AT | 19th Jun 2008 |
| 195.242.170.0/24 | 256 | RIPE NCC |  IT | 10th Jan 2024 |
| 195.242.172.0/24 | 256 | RIPE NCC |  BE | 20th Jun 2008 |
| 195.242.189.0/24 | 256 | RIPE NCC |  HK | 11th Mar 2026 |
| 195.242.208.0/22 | 1k | RIPE NCC | RO | 8th Jun 2018 |
| 195.242.221.0/24 | 256 | RIPE NCC |  FR | 14th Sept 2004 |
| 195.242.222.0/24 | 256 | RIPE NCC | FR | 14th Sept 2004 |
| 195.242.223.0/24 | 256 | RIPE NCC | GB | 14th Sept 2004 |
| 195.242.224.0/23 | 512 | RIPE NCC | DE | 14th Sept 2004 |
| 195.242.248.0/22 | 1k | RIPE NCC |  LI | 21st Sept 2004 |
| 195.242.70.0/23 | 512 | RIPE NCC | GB | 29th Nov 2004 |
| 195.242.76.0/23 | 512 | RIPE NCC |  RS | 1st Dec 2004 |
| 195.242.96.0/23 | 512 | RIPE NCC | NL | 15th Dec 2004 |
| 195.244.16.0/23 | 512 | RIPE NCC | GB | 20th Mar 2006 |
| 195.244.26.0/23 | 512 | RIPE NCC | PL | 21st Mar 2006 |
| 195.244.30.0/23 | 512 | RIPE NCC | FR | 22nd Mar 2006 |
| 195.244.8.0/23 | 512 | RIPE NCC | UA | 16th Mar 2006 |
| 195.245.192.0/24 | 256 | RIPE NCC | DE | 26th Nov 2002 |
| 195.245.193.0/24 | 256 | RIPE NCC |  SE | 26th Nov 2002 |
| 195.245.194.0/24 | 256 | RIPE NCC |  LV | 15th Oct 2007 |
| 195.245.195.0/24 | 256 | RIPE NCC |  SK | 25th Nov 2019 |
| 195.245.198.0/24 | 256 | RIPE NCC | GB | 7th Jun 2023 |
| 195.245.199.0/24 | 256 | RIPE NCC | DE | 27th Nov 2002 |
| 195.245.207.0/24 | 256 | RIPE NCC | SK | 25th Nov 2019 |
| 195.245.210.0/24 | 256 | RIPE NCC | DK | 11th Dec 2002 |
| 195.245.212.0/24 | 256 | RIPE NCC | ES | 11th Dec 2002 |
| 195.245.221.0/24 | 256 | RIPE NCC |  KZ | 30th Dec 2002 |
| 195.245.223.0/24 | 256 | RIPE NCC | GB | 9th Jan 2003 |
| 195.245.228.0/24 | 256 | RIPE NCC |  CH | 13th Jan 2003 |