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 United Kingdom
2,614 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 212.47.52.0/24 | 256 | RIPE NCC | 16th Mar 2026 | |
| 212.52.6.0/24 | 256 | RIPE NCC | 5th Nov 2021 | |
| 212.97.72.0/21 | 2k | RIPE NCC | 5th Feb 1999 | |
| 213.109.180.0/22 | 1k | RIPE NCC | 6th Nov 2018 | |
| 213.12.0.0/16 | 65.5k | RIPE NCC | 24th Aug 1999 | |
| 213.147.224.0/19 | 8.2k | RIPE NCC | 20th Jan 2003 | |
| 213.170.200.0/22 | 1k | RIPE NCC | 6th Nov 2018 | |
| 213.177.32.0/19 | 8.2k | RIPE NCC | 12th Jan 2001 | |
| 213.178.144.0/22 | 1k | RIPE NCC | 18th Mar 2019 | |
| 213.187.32.0/19 | 8.2k | RIPE NCC | 5th Feb 2001 | |
| 213.221.160.0/19 | 8.2k | RIPE NCC | 4th Oct 2000 | |
| 213.225.128.0/19 | 8.2k | RIPE NCC | 24th May 2000 | |
| 213.234.32.0/19 | 8.2k | RIPE NCC | 5th Dec 2001 | |
| 213.237.192.0/18 | 16.4k | RIPE NCC | 18th Mar 2003 | |
| 213.254.166.0/23 | 512 | RIPE NCC | 17th Oct 2000 | |
| 216.116.131.0/24 | 256 | RIPE NCC | 1st Jun 2018 | |
| 216.249.16.0/22 | 1k | RIPE NCC | 24th Jan 2001 | |
| 216.87.55.0/24 | 256 | RIPE NCC | 9th Jul 1999 | |
| 217.138.0.0/21 | 2k | RIPE NCC | 31st Jan 2001 | |
| 217.140.16.0/20 | 4.1k | RIPE NCC | 5th Mar 2001 | |
| 217.154.104.0/24 | 256 | RIPE NCC | 19th Feb 2001 | |
| 217.154.12.0/24 | 256 | RIPE NCC | 19th Feb 2001 | |
| 217.154.151.0/24 | 256 | RIPE NCC | 19th Feb 2001 | |
| 217.154.158.0/24 | 256 | RIPE NCC | 19th Feb 2001 | |
| 217.154.209.0/24 | 256 | RIPE NCC | 19th Feb 2001 | |
| 217.154.219.0/24 | 256 | RIPE NCC | 19th Feb 2001 | |
| 217.154.221.0/24 | 256 | RIPE NCC | 19th Feb 2001 | |
| 217.154.236.0/24 | 256 | RIPE NCC | 19th Feb 2001 | |
| 217.154.25.0/24 | 256 | RIPE NCC | 19th Feb 2001 | |
| 217.154.46.0/24 | 256 | RIPE NCC | 19th Feb 2001 | |
| 217.16.48.0/20 | 4.1k | RIPE NCC | 22nd Nov 2002 | |
| 217.177.13.0/24 | 256 | RIPE NCC | 2nd Mar 2001 | |
| 217.177.96.0/19 | 8.2k | RIPE NCC | 2nd Mar 2001 | |
| 217.18.84.0/24 | 256 | RIPE NCC | 8th Mar 2023 | |
| 217.18.91.0/24 | 256 | RIPE NCC | 26th Jan 2026 | |
| 217.180.0.0/21 | 2k | RIPE NCC | 2nd Mar 2001 | |
| 217.180.36.0/23 | 512 | RIPE NCC | 2nd Mar 2001 | |
| 217.180.60.0/24 | 256 | RIPE NCC | 2nd Mar 2001 | |
| 217.180.8.0/22 | 1k | RIPE NCC | 2nd Mar 2001 | |
| 217.197.96.0/24 | 256 | RIPE NCC | 15th May 2023 | |
| 217.198.32.0/20 | 4.1k | RIPE NCC | 3rd May 2001 | |
| 217.198.48.0/21 | 2k | RIPE NCC | 5th Nov 2004 | |
| 217.22.8.0/24 | 256 | RIPE NCC | 26th Jun 2026 | |
| 217.29.196.0/22 | 1k | RIPE NCC | 23rd Oct 2000 | |
| 217.29.200.0/21 | 2k | RIPE NCC | 23rd Oct 2000 | |
| 217.65.74.0/24 | 256 | RIPE NCC | 11th Jun 2025 | |
| 2a00:1070::/32 | 4.3B × /64 | RIPE NCC | 29th Jun 2009 | |
| 2a00:10f0::/32 | 4.3B × /64 | RIPE NCC | 13th Jul 2009 | |
| 2a00:11c8::/32 | 4.3B × /64 | RIPE NCC | 5th Aug 2009 | |
| 2a00:1350::/32 | 4.3B × /64 | RIPE NCC | 15th Sept 2009 |