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 the most unannounced blocks, largest first.
Unannounced blocks
85,244 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 195.245.223.0/24 | 256 | RIPE NCC |  GB | 9th Jan 2003 |
| 195.245.228.0/24 | 256 | RIPE NCC |  CH | 13th Jan 2003 |
| 195.245.240.0/24 | 256 | RIPE NCC |  SE | 22nd Jan 2003 |
| 195.245.243.0/24 | 256 | RIPE NCC |  DE | 23rd Jan 2003 |
| 195.245.246.0/24 | 256 | RIPE NCC |  NL | 25th Nov 2019 |
| 195.245.247.0/24 | 256 | RIPE NCC |  US | 24th Jan 2003 |
| 195.245.252.0/24 | 256 | RIPE NCC | GB | 4th Feb 2003 |
| 195.245.85.0/24 | 256 | RIPE NCC |  OM | 9th Dec 2020 |
| 195.246.113.0/24 | 256 | RIPE NCC |  UZ | 19th Jul 2024 |
| 195.246.160.0/19 | 8.2k | RIPE NCC | DE | 11th Nov 1997 |
| 195.246.192.0/24 | 256 | RIPE NCC |  TJ | 24th Feb 2025 |
| 195.246.193.0/24 | 256 | RIPE NCC | US | 25th Feb 2025 |
| 195.246.195.0/24 | 256 | RIPE NCC | DE | 25th Feb 2025 |
| 195.246.196.0/24 | 256 | RIPE NCC |  IL | 19th Feb 2025 |
| 195.246.197.0/24 | 256 | RIPE NCC | NL | 25th Nov 2019 |
| 195.246.248.0/23 | 512 | RIPE NCC |  RU | 7th Nov 2019 |
| 195.246.252.0/23 | 512 | RIPE NCC |  LV | 31st Mar 2006 |
| 195.248.192.0/19 | 8.2k | RIPE NCC | GB | 10th Apr 1997 |
| 195.248.66.0/24 | 256 | RIPE NCC | US | 23rd Jun 2006 |
| 195.248.81.0/24 | 256 | RIPE NCC | RU | 24th Aug 2022 |
| 195.248.84.0/24 | 256 | RIPE NCC | NL | 25th Nov 2019 |
| 195.248.92.0/24 | 256 | RIPE NCC | CH | 5th Jul 2006 |
| 195.248.94.0/24 | 256 | RIPE NCC | RU | 13th Jan 2009 |
| 195.250.216.0/21 | 2k | RIPE NCC |  SI | 14th May 1997 |
| 195.250.32.0/24 | 256 | RIPE NCC |  AT | 18th Jan 2006 |
| 195.250.35.0/24 | 256 | RIPE NCC | DE | 20th Jan 2006 |
| 195.250.36.0/24 | 256 | RIPE NCC |  UA | 20th Jan 2006 |
| 195.250.41.0/24 | 256 | RIPE NCC | CH | 20th Jan 2006 |
| 195.250.49.0/24 | 256 | RIPE NCC | SI | 29th Apr 2022 |
| 195.250.62.0/24 | 256 | RIPE NCC | UA | 31st Jan 2006 |
| 195.253.192.0/22 | 1k | RIPE NCC | DE | 9th Jan 1998 |
| 195.253.196.0/24 | 256 | RIPE NCC | DE | 9th Jan 1998 |
| 195.253.212.0/22 | 1k | RIPE NCC | DE | 9th Jan 1998 |
| 195.253.216.0/21 | 2k | RIPE NCC |  DK | 9th Jan 1998 |
| 195.253.224.0/22 | 1k | RIPE NCC | CH | 9th Jan 1998 |
| 195.253.228.0/22 | 1k | RIPE NCC | DE | 9th Jan 1998 |
| 195.253.232.0/22 | 1k | RIPE NCC | DE | 9th Jan 1998 |
| 195.253.236.0/22 | 1k | APNIC |  HK | 9th Jan 1998 |
| 195.253.252.0/22 | 1k | RIPE NCC | DE | 9th Jan 1998 |
| 195.254.150.0/24 | 256 | RIPE NCC | UA | 21st Nov 2005 |
| 195.254.152.0/23 | 512 | RIPE NCC |  RO | 21st Nov 2005 |
| 195.254.158.0/23 | 512 | RIPE NCC | DE | 24th Nov 2005 |
| 195.254.162.0/23 | 512 | RIPE NCC | DE | 17th May 2010 |
| 195.254.180.0/24 | 256 | RIPE NCC |  LB | 2nd Sept 2026 |
| 195.254.181.0/24 | 256 | RIPE NCC |  TR | 2nd Sept 2026 |
| 195.254.186.0/23 | 512 | RIPE NCC | CH | 7th Nov 2019 |
| 195.26.24.0/24 | 256 | RIPE NCC |  PL | 3rd Dec 2002 |
| 195.26.88.0/22 | 1k | RIPE NCC | GB | 19th Jul 2006 |
| 195.28.172.0/23 | 512 | RIPE NCC |  NO | 4th Aug 2004 |
| 195.28.174.0/23 | 512 | RIPE NCC |  BE | 5th Aug 2004 |