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 in Spain
895 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 5.181.220.0/22 | 1k | RIPE NCC | 3rd Apr 2019 | |
| 5.183.150.0/24 | 256 | RIPE NCC | 11th Apr 2019 | |
| 66.45.120.0/21 | 2k | RIPE NCC | 15th Nov 2000 | |
| 77.243.192.0/20 | 4.1k | RIPE NCC | 16th Mar 2007 | |
| 77.72.24.0/21 | 2k | RIPE NCC | 17th Jan 2007 | |
| 77.73.118.0/24 | 256 | RIPE NCC | 19th Jan 2026 | |
| 77.81.8.0/21 | 2k | RIPE NCC | 15th Feb 2007 | |
| 79.108.0.0/18 | 16.4k | RIPE NCC | 3rd Dec 2007 | |
| 79.108.112.0/22 | 1k | RIPE NCC | 3rd Dec 2007 | |
| 79.108.116.0/23 | 512 | RIPE NCC | 3rd Dec 2007 | |
| 79.108.118.0/24 | 256 | RIPE NCC | 3rd Dec 2007 | |
| 79.108.120.0/21 | 2k | RIPE NCC | 3rd Dec 2007 | |
| 79.108.64.0/19 | 8.2k | RIPE NCC | 3rd Dec 2007 | |
| 79.108.96.0/20 | 4.1k | RIPE NCC | 3rd Dec 2007 | |
| 79.171.24.0/21 | 2k | RIPE NCC | 30th Jan 2008 | |
| 80.173.112.0/22 | 1k | RIPE NCC | 11th Jun 2003 | |
| 80.173.116.0/23 | 512 | RIPE NCC | 11th Jun 2003 | |
| 80.173.120.0/21 | 2k | RIPE NCC | 11th Jun 2003 | |
| 80.173.174.0/24 | 256 | RIPE NCC | 11th Jun 2003 | |
| 80.173.64.0/19 | 8.2k | RIPE NCC | 11th Jun 2003 | |
| 80.173.96.0/20 | 4.1k | RIPE NCC | 11th Jun 2003 | |
| 80.224.0.0/17 | 32.8k | RIPE NCC | 28th Sept 2001 | |
| 80.224.128.0/19 | 8.2k | RIPE NCC | 28th Sept 2001 | |
| 80.224.160.0/20 | 4.1k | RIPE NCC | 28th Sept 2001 | |
| 80.224.176.0/22 | 1k | RIPE NCC | 28th Sept 2001 | |
| 80.224.182.0/23 | 512 | RIPE NCC | 28th Sept 2001 | |
| 80.224.184.0/22 | 1k | RIPE NCC | 28th Sept 2001 | |
| 80.224.191.0/24 | 256 | RIPE NCC | 28th Sept 2001 | |
| 80.224.208.0/21 | 2k | RIPE NCC | 28th Sept 2001 | |
| 80.244.2.0/24 | 256 | RIPE NCC | 24th Jan 2024 | |
| 80.248.137.0/24 | 256 | RIPE NCC | 19th Nov 2001 | |
| 80.80.88.0/23 | 512 | RIPE NCC | 30th Mar 2005 | |
| 81.28.240.0/22 | 1k | RIPE NCC | 17th Aug 2018 | |
| 81.30.99.0/24 | 256 | RIPE NCC | 18th Jun 2024 | |
| 82.158.176.0/22 | 1k | RIPE NCC | 2nd Dec 2003 | |
| 85.137.180.0/24 | 256 | RIPE NCC | 3rd Nov 2004 | |
| 85.137.82.0/23 | 512 | RIPE NCC | 3rd Nov 2004 | |
| 85.155.10.0/23 | 512 | RIPE NCC | 5th Nov 2004 | |
| 85.155.12.0/23 | 512 | RIPE NCC | 5th Nov 2004 | |
| 85.155.216.0/21 | 2k | RIPE NCC | 5th Nov 2004 | |
| 85.155.4.0/22 | 1k | RIPE NCC | 5th Nov 2004 | |
| 85.155.9.0/24 | 256 | RIPE NCC | 5th Nov 2004 | |
| 85.8.220.0/24 | 256 | RIPE NCC | 26th Jun 2026 | |
| 85.90.213.0/24 | 256 | RIPE NCC | 11th Nov 2004 | |
| 85.90.214.0/24 | 256 | RIPE NCC | 11th Nov 2004 | |
| 85.90.218.0/23 | 512 | RIPE NCC | 11th Nov 2004 | |
| 86.105.120.0/21 | 2k | RIPE NCC | 18th Apr 2005 | |
| 87.111.0.0/16 | 65.5k | RIPE NCC | 20th Sept 2005 | |
| 89.22.8.0/21 | 2k | RIPE NCC | 11th Jul 2011 | |
| 89.32.64.0/21 | 2k | RIPE NCC | 29th Nov 2005 |