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.191.54.0/23 | 512 | RIPE NCC |  GB | 6th Nov 2019 |
| 195.191.56.0/23 | 512 | RIPE NCC | GB | 6th Nov 2019 |
| 195.191.6.0/24 | 256 | RIPE NCC |  UA | 3rd Aug 2026 |
| 195.191.62.0/24 | 256 | RIPE NCC |  PL | 31st Dec 2009 |
| 195.191.70.0/23 | 512 | RIPE NCC | GB | 13th Jan 2010 |
| 195.191.78.0/23 | 512 | RIPE NCC |  RU | 5th Jan 2011 |
| 195.191.97.0/24 | 256 | RIPE NCC |  HU | 5th Sept 2012 |
| 195.192.248.0/23 | 512 | RIPE NCC |  DK | 3rd Apr 1996 |
| 195.192.253.0/24 | 256 | RIPE NCC |  DE | 3rd Apr 1996 |
| 195.2.194.0/23 | 512 | RIPE NCC | RU | 8th Dec 2008 |
| 195.2.230.0/23 | 512 | RIPE NCC |  KZ | 1st Nov 2007 |
| 195.2.234.0/24 | 256 | RIPE NCC |  IR | 26th Jul 2022 |
| 195.2.249.0/24 | 256 | RIPE NCC |  NL | 25th Apr 2022 |
| 195.20.101.0/24 | 256 | RIPE NCC |  FR | 3rd Mar 2021 |
| 195.20.107.0/24 | 256 | RIPE NCC |  RO | 30th Oct 2002 |
| 195.20.110.0/23 | 512 | RIPE NCC | PL | 1st Nov 2002 |
| 195.20.143.0/24 | 256 | RIPE NCC | NL | 22nd Nov 2019 |
| 195.20.214.0/23 | 512 | RIPE NCC | GB | 23rd Jun 2010 |
| 195.20.216.0/24 | 256 | RIPE NCC |  JO | 26th Jan 2026 |
| 195.20.217.0/24 | 256 | RIPE NCC | PL | 26th Jan 2026 |
| 195.200.192.0/24 | 256 | RIPE NCC | PL | 16th Jun 2025 |
| 195.200.193.0/24 | 256 | RIPE NCC |  GR | 2nd Aug 2006 |
| 195.200.195.0/24 | 256 | RIPE NCC | FR | 2nd Aug 2006 |
| 195.200.196.0/24 | 256 | RIPE NCC | UA | 2nd Aug 2006 |
| 195.200.197.0/24 | 256 | RIPE NCC |  AT | 2nd Aug 2006 |
| 195.200.203.0/24 | 256 | RIPE NCC | RU | 7th Aug 2006 |
| 195.200.218.0/24 | 256 | RIPE NCC |  CH | 14th Aug 2006 |
| 195.200.27.0/24 | 256 | RIPE NCC | GB | 9th May 1996 |
| 195.200.76.0/24 | 256 | RIPE NCC | IR | 17th Jul 2024 |
| 195.206.128.0/20 | 4.1k | RIPE NCC | DE | 20th Dec 1996 |
| 195.206.242.0/24 | 256 | RIPE NCC |  LV | 12th Sept 2022 |
| 195.206.243.0/24 | 256 | RIPE NCC |  HK | 12th Sept 2022 |
| 195.208.20.0/23 | 512 | RIPE NCC | RU | 19th Apr 1996 |
| 195.208.220.0/23 | 512 | RIPE NCC | RU | 19th Apr 1996 |
| 195.209.137.0/24 | 256 | RIPE NCC | RU | 19th Jul 1996 |
| 195.209.152.0/21 | 2k | RIPE NCC | RU | 19th Jul 1996 |
| 195.210.30.0/23 | 512 | RIPE NCC | RU | 14th May 2010 |
| 195.210.34.0/23 | 512 | RIPE NCC | PL | 6th Mar 2006 |
| 195.210.54.0/23 | 512 | RIPE NCC | GB | 14th Mar 2006 |
| 195.210.58.0/23 | 512 | RIPE NCC | DE | 14th Mar 2006 |
| 195.210.62.0/23 | 512 | RIPE NCC |  SE | 14th Mar 2006 |
| 195.211.127.0/24 | 256 | RIPE NCC | RO | 4th Dec 2023 |
| 195.211.132.0/22 | 1k | RIPE NCC | SE | 13th Oct 2009 |
| 195.211.160.0/22 | 1k | RIPE NCC | RU | 20th Oct 2009 |
| 195.211.32.0/22 | 1k | RIPE NCC |  LI | 11th Sept 2009 |
| 195.211.42.0/24 | 256 | RIPE NCC | RU | 14th Sept 2009 |
| 195.211.70.0/24 | 256 | RIPE NCC | FR | 26th Jun 2025 |
| 195.214.213.0/24 | 256 | RIPE NCC |  US | 28th Oct 2003 |
| 195.214.214.0/24 | 256 | RIPE NCC | US | 28th Oct 2003 |
| 195.214.232.0/24 | 256 | RIPE NCC | CH | 3rd Feb 2005 |