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.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 |
| 195.60.89.0/25 | 128 | RIPE NCC |  CZ | 12th May 2006 |
| 195.60.89.128/25 | 128 | RIPE NCC |  IT | 22nd May 2006 |
| 195.60.90.0/25 | 128 | RIPE NCC |  FI | 10th Dec 2008 |
| 195.60.90.128/25 | 128 | RIPE NCC |  DK | 9th Jun 2006 |
| 195.60.91.0/25 | 128 | RIPE NCC |  BE | 14th Jul 2006 |
| 195.60.91.128/26 | 64 | RIPE NCC |  CH | 30th Mar 2026 |
| 195.60.91.192/26 | 64 | RIPE NCC |  PL | 2nd Apr 2026 |
| 195.60.92.0/26 | 64 | RIPE NCC |  SE | 7th May 2008 |
| 195.60.92.128/26 | 64 | RIPE NCC | PL | 5th Dec 2006 |
| 195.60.92.192/26 | 64 | RIPE NCC |  DE | 26th Mar 2024 |
| 195.60.92.64/26 | 64 | RIPE NCC |  US | 10th Mar 2026 |
| 195.60.93.0/26 | 64 | RIPE NCC | CY | 14th Sept 2012 |
| 195.60.93.128/26 | 64 | RIPE NCC | CH | 17th Apr 2007 |
| 195.60.93.192/26 | 64 | RIPE NCC | CY | 14th Sept 2012 |
| 195.60.93.64/26 | 64 | RIPE NCC | DE | 26th Mar 2024 |
| 195.60.95.0/25 | 128 | RIPE NCC | CY | 14th Sept 2012 |
| 195.60.95.128/25 | 128 | RIPE NCC | GB | 4th Jul 2006 |
| 195.62.28.0/23 | 512 | RIPE NCC | DE | 28th Jul 2004 |
| 195.62.30.0/24 | 256 | RIPE NCC |  TR | 10th Nov 2025 |
| 195.62.8.0/23 | 512 | RIPE NCC | GB | 16th Jul 2004 |
| 195.62.89.0/24 | 256 | RIPE NCC | US | 16th Nov 2022 |
| 195.64.100.0/24 | 256 | RIPE NCC |  FR | 25th Jan 2022 |
| 195.64.114.0/24 | 256 | RIPE NCC | CH | 25th Jan 2022 |
| 195.64.128.0/23 | 512 | RIPE NCC | CH | 4th Nov 2019 |
| 195.64.146.0/23 | 512 | RIPE NCC | AT | 20th Dec 2006 |
| 195.64.152.0/23 | 512 | RIPE NCC |  RO | 4th Nov 2019 |
| 195.64.160.0/23 | 512 | RIPE NCC |  BG | 9th Jun 2006 |
| 195.64.168.0/23 | 512 | RIPE NCC | RO | 4th Nov 2019 |
| 195.64.170.0/23 | 512 | RIPE NCC |  RS | 8th Apr 2008 |
| 195.64.96.0/24 | 256 | RIPE NCC | AT | 25th Jan 2022 |
| 195.66.102.0/24 | 256 | RIPE NCC | GB | 10th May 2021 |
| 195.66.103.0/24 | 256 | RIPE NCC | PL | 17th Mar 2008 |
| 195.66.108.0/24 | 256 | RIPE NCC |  RU | 19th Mar 2008 |
| 195.66.110.0/24 | 256 | RIPE NCC |  UA | 26th Sept 2011 |
| 195.66.111.0/24 | 256 | RIPE NCC | DE | 20th Mar 2008 |
| 195.66.118.0/24 | 256 | RIPE NCC |  IL | 25th Mar 2008 |
| 195.66.121.0/24 | 256 | RIPE NCC | DE | 25th Mar 2008 |
| 195.66.122.0/24 | 256 | RIPE NCC | DE | 26th Mar 2008 |
| 195.66.123.0/24 | 256 | RIPE NCC | CH | 27th Mar 2008 |
| 195.66.154.0/23 | 512 | RIPE NCC | DE | 2nd Dec 2005 |
| 195.66.16.0/21 | 2k | RIPE NCC | PL | 13th Jan 2006 |
| 195.66.64.0/24 | 256 | RIPE NCC |  LV | 6th Dec 2005 |
| 195.66.66.0/24 | 256 | RIPE NCC | UA | 6th Dec 2005 |
| 195.66.71.0/24 | 256 | RIPE NCC | RU | 23rd Dec 2005 |