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 in Spain
907 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 2a14:b880::/29 | 34.4B × /64 | RIPE NCC | 12th Mar 2025 | |
| 2a14:bc00::/29 | 34.4B × /64 | RIPE NCC | 6th Dec 2024 | |
| 2a14:d080::/29 | 34.4B × /64 | RIPE NCC | 26th Mar 2025 | |
| 2a14:d40::/29 | 34.4B × /64 | RIPE NCC | 27th Feb 2024 | |
| 2a14:ff80::/29 | 34.4B × /64 | RIPE NCC | 25th Apr 2025 | |
| 31.14.104.0/21 | 2k | RIPE NCC | 18th Apr 2011 | |
| 31.14.192.0/21 | 2k | RIPE NCC | 18th Apr 2011 | |
| 31.193.224.0/21 | 2k | RIPE NCC | 28th Apr 2011 | |
| 31.214.155.0/24 | 256 | RIPE NCC | 6th May 2011 | |
| 31.3.220.0/24 | 256 | RIPE NCC | 8th Apr 2011 | |
| 45.12.152.0/22 | 1k | RIPE NCC | 1st May 2019 | |
| 45.120.220.0/22 | 1k | RIPE NCC | 23rd Jun 2015 | |
| 45.13.170.0/24 | 256 | RIPE NCC | 6th May 2019 | |
| 45.144.231.0/24 | 256 | RIPE NCC | 23rd Aug 2019 | |
| 45.152.140.0/22 | 1k | RIPE NCC | 12th Sept 2019 | |
| 45.155.32.0/22 | 1k | RIPE NCC | 17th Sept 2019 | |
| 45.156.68.0/22 | 1k | RIPE NCC | 20th Sept 2019 | |
| 45.157.20.0/22 | 1k | RIPE NCC | 24th Sept 2019 | |
| 45.83.80.0/22 | 1k | RIPE NCC | 27th May 2019 | |
| 45.91.232.0/22 | 1k | RIPE NCC | 28th Jun 2019 | |
| 45.93.180.0/22 | 1k | RIPE NCC | 4th Jul 2019 | |
| 46.102.103.0/24 | 256 | RIPE NCC | 25th Jun 2010 | |
| 5.152.168.0/21 | 2k | RIPE NCC | 19th Jul 2012 | |
| 5.154.234.0/23 | 512 | RIPE NCC | 19th Jul 2012 | |
| 5.159.240.0/21 | 2k | RIPE NCC | 30th Jul 2012 | |
| 5.181.220.0/22 | 1k | RIPE NCC | 3rd Apr 2019 | |
| 5.183.150.0/24 | 256 | RIPE NCC | 11th Apr 2019 | |
| 62.117.128.0/19 | 8.2k | RIPE NCC | 27th Jul 2000 | |
| 62.117.160.0/19 | 8.2k | RIPE NCC | 31st Oct 2000 | |
| 62.117.192.0/18 | 16.4k | RIPE NCC | 31st Oct 2000 | |
| 62.83.0.0/16 | 65.5k | RIPE NCC | 11th Feb 2000 | |
| 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/17 | 32.8k | RIPE NCC | 3rd Dec 2007 | |
| 79.171.24.0/21 | 2k | RIPE NCC | 30th Jan 2008 | |
| 80.173.0.0/17 | 32.8k | RIPE NCC | 11th Jun 2003 | |
| 80.173.174.0/24 | 256 | RIPE NCC | 11th Jun 2003 | |
| 80.173.176.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/18 | 16.4k | 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 | |
| 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/23 | 512 | RIPE NCC | 3rd Nov 2004 | |
| 85.137.82.0/23 | 512 | RIPE NCC | 3rd Nov 2004 |