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 |
|---|---|---|---|---|
| 86.54.226.0/23 | 512 | RIPE NCC |  GB | 12th May 2005 |
| 86.54.229.0/24 | 256 | RIPE NCC | GB | 12th May 2005 |
| 86.54.230.0/23 | 512 | RIPE NCC | GB | 12th May 2005 |
| 86.54.232.0/23 | 512 | RIPE NCC | GB | 12th May 2005 |
| 86.54.236.0/22 | 1k | RIPE NCC | GB | 12th May 2005 |
| 86.54.240.0/21 | 2k | RIPE NCC | GB | 12th May 2005 |
| 86.54.250.0/23 | 512 | RIPE NCC | GB | 12th May 2005 |
| 86.54.252.0/22 | 1k | RIPE NCC | GB | 12th May 2005 |
| 86.54.40.0/23 | 512 | RIPE NCC | GB | 12th May 2005 |
| 86.54.48.0/20 | 4.1k | RIPE NCC | GB | 12th May 2005 |
| 86.54.64.0/20 | 4.1k | RIPE NCC | GB | 12th May 2005 |
| 86.54.8.0/23 | 512 | RIPE NCC | GB | 12th May 2005 |
| 86.54.84.0/23 | 512 | RIPE NCC | GB | 12th May 2005 |
| 86.54.88.0/21 | 2k | RIPE NCC | GB | 12th May 2005 |
| 87.120.16.0/20 | 4.1k | RIPE NCC | GB | 12th Jul 2005 |
| 87.121.222.0/24 | 256 | RIPE NCC | GB | 12th Jul 2005 |
| 87.192.32.0/19 | 8.2k | RIPE NCC | GB | 3rd Jun 2005 |
| 87.236.165.0/24 | 256 | RIPE NCC | GB | 19th Aug 2021 |
| 87.237.48.0/22 | 1k | RIPE NCC | GB | 26th Jun 2018 |
| 87.252.112.0/21 | 2k | RIPE NCC | GB | 21st Sept 2005 |
| 88.218.88.0/22 | 1k | RIPE NCC | GB | 14th Dec 2018 |
| 88.82.128.0/19 | 8.2k | RIPE NCC | GB | 21st Dec 2005 |
| 89.104.32.0/19 | 8.2k | RIPE NCC | GB | 1st Mar 2006 |
| 89.106.144.0/21 | 2k | RIPE NCC | GB | 30th Mar 2006 |
| 89.17.96.0/19 | 8.2k | RIPE NCC | GB | 21st Jul 2006 |
| 89.200.128.0/21 | 2k | RIPE NCC | GB | 13th Apr 2006 |
| 89.207.0.0/21 | 2k | RIPE NCC | GB | 31st May 2006 |
| 89.207.208.0/21 | 2k | RIPE NCC | GB | 11th Jul 2006 |
| 89.222.48.0/20 | 4.1k | RIPE NCC | GB | 7th Sept 2006 |
| 89.251.4.0/22 | 1k | RIPE NCC | GB | 10th Sept 2019 |
| 89.31.208.0/22 | 1k | RIPE NCC | GB | 22nd Sept 2006 |
| 89.31.28.0/22 | 1k | RIPE NCC | GB | 21st Jun 2018 |
| 89.36.255.0/24 | 256 | RIPE NCC | GB | 29th Nov 2005 |
| 89.37.94.0/24 | 256 | RIPE NCC | GB | 29th Nov 2005 |
| 89.41.27.0/24 | 256 | RIPE NCC | GB | 29th Nov 2005 |
| 89.42.154.0/24 | 256 | RIPE NCC | GB | 29th Nov 2005 |
| 89.42.155.0/24 | 256 | RIPE NCC | GB | 29th Nov 2005 |
| 91.103.136.0/24 | 256 | RIPE NCC | GB | 12th Jan 2024 |
| 91.105.224.0/21 | 2k | RIPE NCC | GB | 20th Jun 2012 |
| 91.132.32.0/22 | 1k | RIPE NCC | GB | 18th Dec 2018 |
| 91.192.16.0/22 | 1k | RIPE NCC | GB | 26th Jan 2007 |
| 91.192.232.0/22 | 1k | RIPE NCC | GB | 16th Mar 2007 |
| 91.193.108.0/23 | 512 | RIPE NCC | GB | 14th Sept 2009 |
| 91.194.158.0/23 | 512 | RIPE NCC | GB | 26th Jun 2007 |
| 91.194.42.0/23 | 512 | RIPE NCC | GB | 25th May 2007 |
| 91.195.166.0/23 | 512 | RIPE NCC | GB | 26th Sept 2007 |
| 91.195.182.0/23 | 512 | RIPE NCC | GB | 2nd Oct 2007 |
| 91.195.186.0/23 | 512 | RIPE NCC | GB | 3rd Oct 2007 |
| 91.195.192.0/23 | 512 | RIPE NCC | GB | 4th Oct 2007 |
| 91.195.82.0/23 | 512 | RIPE NCC | GB | 3rd Sept 2007 |