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.69.100.0/22 | 1k | RIPE NCC |  GB | 4th Jun 2018 |
| 195.69.116.0/22 | 1k | RIPE NCC |  SE | 26th Jun 2003 |
| 195.69.152.0/22 | 1k | RIPE NCC | GB | 17th Mar 2003 |
| 195.69.160.0/24 | 256 | RIPE NCC |  RU | 25th Apr 2022 |
| 195.69.227.0/24 | 256 | RIPE NCC |  CH | 1st Mar 2011 |
| 195.69.232.0/22 | 1k | RIPE NCC | CH | 8th May 2003 |
| 195.7.0.0/22 | 1k | RIPE NCC |  AT | 27th Sept 2018 |
| 195.72.116.0/23 | 512 | RIPE NCC | GB | 7th Aug 2000 |
| 195.72.156.0/22 | 1k | RIPE NCC |  UA | 23rd Jan 2006 |
| 195.72.40.0/22 | 1k | RIPE NCC | CH | 9th Jun 1997 |
| 195.74.36.0/22 | 1k | RIPE NCC | SE | 27th Dec 2006 |
| 195.74.56.0/22 | 1k | RIPE NCC |  PL | 8th Jan 2007 |
| 195.74.70.0/24 | 256 | RIPE NCC |  DE | 10th Jul 2006 |
| 195.74.77.0/24 | 256 | RIPE NCC |  NO | 9th Aug 2012 |
| 195.74.84.0/24 | 256 | RIPE NCC | RU | 12th Jul 2006 |
| 195.74.86.0/24 | 256 | RIPE NCC |  MD | 19th Oct 2022 |
| 195.78.102.0/23 | 512 | RIPE NCC | AT | 5th Oct 2009 |
| 195.78.110.0/23 | 512 | RIPE NCC | GB | 6th Oct 2009 |
| 195.78.114.0/24 | 256 | RIPE NCC |  ES | 14th Oct 2024 |
| 195.78.116.0/23 | 512 | RIPE NCC | RU | 8th Oct 2009 |
| 195.78.120.0/24 | 256 | RIPE NCC |  HK | 7th Aug 2026 |
| 195.78.121.0/24 | 256 | RIPE NCC |  IT | 19th Aug 2026 |
| 195.78.34.0/23 | 512 | RIPE NCC |  HR | 8th Aug 2007 |
| 195.78.40.0/23 | 512 | RIPE NCC | DE | 19th Feb 2003 |
| 195.78.76.0/23 | 512 | RIPE NCC | DE | 6th Sept 2006 |
| 195.78.84.0/23 | 512 | RIPE NCC |  NL | 8th Sept 2006 |
| 195.8.100.0/24 | 256 | RIPE NCC | GB | 12th Jan 2005 |
| 195.8.118.0/23 | 512 | RIPE NCC | ES | 1st Nov 2019 |
| 195.8.160.0/19 | 8.2k | RIPE NCC | GB | 11th Dec 1997 |
| 195.8.34.0/23 | 512 | RIPE NCC | RU | 18th Dec 2008 |
| 195.8.47.0/24 | 256 | RIPE NCC | NL | 18th May 2020 |
| 195.8.96.0/24 | 256 | RIPE NCC | GB | 12th Jan 2005 |
| 195.80.137.0/24 | 256 | RIPE NCC | SE | 31st Aug 2011 |
| 195.80.232.0/24 | 256 | RIPE NCC | UA | 30th Jun 2005 |
| 195.80.234.0/24 | 256 | RIPE NCC | AT | 28th Jun 2005 |
| 195.80.236.0/24 | 256 | RIPE NCC | PL | 28th Jun 2005 |
| 195.80.240.0/20 | 4.1k | RIPE NCC |  DK | 22nd Oct 2002 |
| 195.80.32.0/22 | 1k | RIPE NCC |  BZ | 25th Mar 2019 |
| 195.80.56.0/22 | 1k | RIPE NCC | RU | 25th Mar 2019 |
| 195.82.152.0/23 | 512 | RIPE NCC | DE | 28th Mar 2008 |
| 195.85.0.0/23 | 512 | RIPE NCC | DK | 6th Feb 1997 |
| 195.85.100.0/23 | 512 | RIPE NCC | DK | 6th Feb 1997 |
| 195.85.104.0/23 | 512 | RIPE NCC | DK | 6th Feb 1997 |
| 195.85.109.0/24 | 256 | RIPE NCC | DK | 6th Feb 1997 |
| 195.85.110.0/23 | 512 | RIPE NCC | DK | 6th Feb 1997 |
| 195.85.112.0/24 | 256 | RIPE NCC | DK | 6th Feb 1997 |
| 195.85.117.0/24 | 256 | RIPE NCC | DK | 6th Feb 1997 |
| 195.85.13.0/24 | 256 | RIPE NCC | DK | 6th Feb 1997 |
| 195.85.14.0/23 | 512 | RIPE NCC | DK | 6th Feb 1997 |
| 195.85.16.0/23 | 512 | RIPE NCC | DK | 6th Feb 1997 |