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 registered through RIPE NCC
25,269 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 87.236.86.0/24 | 256 | RIPE NCC |  RU | 12th Aug 2005 |
| 87.236.87.0/24 | 256 | RIPE NCC | RU | 12th Aug 2005 |
| 87.237.165.0/24 | 256 | RIPE NCC |  DE | 8th May 2020 |
| 87.237.48.0/22 | 1k | RIPE NCC |  GB | 26th Jun 2018 |
| 87.237.88.0/21 | 2k | RIPE NCC | DE | 10th Nov 2005 |
| 87.238.227.0/24 | 256 | RIPE NCC |  BE | 24th Jan 2006 |
| 87.239.224.0/21 | 2k | RIPE NCC |  CH | 30th Mar 2006 |
| 87.239.34.0/24 | 256 | RIPE NCC | RU | 22nd Sept 2009 |
| 87.239.48.0/22 | 1k | RIPE NCC |  AT | 21st Jun 2018 |
| 87.239.72.0/21 | 2k | RIPE NCC |  PL | 24th Nov 2005 |
| 87.243.16.0/20 | 4.1k | RIPE NCC |  KZ | 8th Jul 2010 |
| 87.246.39.0/24 | 256 | RIPE NCC |  BG | 25th Aug 2005 |
| 87.247.132.0/22 | 1k | RIPE NCC | RU | 9th Oct 2018 |
| 87.247.240.0/21 | 2k | RIPE NCC | DE | 3rd Feb 2006 |
| 87.248.192.0/19 | 8.2k | RIPE NCC |  US | 22nd Aug 2005 |
| 87.249.60.0/24 | 256 | RIPE NCC | RU | 25th Aug 2005 |
| 87.252.112.0/21 | 2k | RIPE NCC | GB | 21st Sept 2005 |
| 87.252.120.0/22 | 1k | RIPE NCC | DE | 21st Sept 2005 |
| 87.252.124.0/23 | 512 | RIPE NCC | DE | 21st Sept 2005 |
| 87.253.176.0/21 | 2k | RIPE NCC | DE | 6th Oct 2005 |
| 87.58.0.0/19 | 8.2k | RIPE NCC |  NL | 20th May 2005 |
| 88.135.34.0/23 | 512 | RIPE NCC |  IR | 16th Nov 2009 |
| 88.144.0.0/15 | 131k | RIPE NCC |  SE | 18th Nov 2005 |
| 88.151.104.0/21 | 2k | RIPE NCC | RU | 28th Feb 2006 |
| 88.151.113.0/24 | 256 | RIPE NCC |  UA | 25th Apr 2022 |
| 88.210.28.0/24 | 256 | RIPE NCC | RU | 24th Nov 2005 |
| 88.210.51.0/24 | 256 | RIPE NCC | RU | 24th Nov 2005 |
| 88.218.124.0/22 | 1k | RIPE NCC | BE | 17th Dec 2018 |
| 88.218.176.0/22 | 1k | RIPE NCC |  DK | 17th Dec 2018 |
| 88.218.208.0/22 | 1k | RIPE NCC | DE | 17th Dec 2018 |
| 88.218.244.0/22 | 1k | RIPE NCC | RU | 18th Dec 2018 |
| 88.218.36.0/22 | 1k | RIPE NCC |  IE | 14th Dec 2018 |
| 88.218.88.0/22 | 1k | RIPE NCC | GB | 14th Dec 2018 |
| 88.80.192.0/19 | 8.2k | RIPE NCC | DE | 1st Dec 2005 |
| 88.80.4.0/22 | 1k | RIPE NCC | SE | 24th Nov 2005 |
| 88.81.32.0/19 | 8.2k | RIPE NCC | RU | 2nd Oct 2009 |
| 88.82.128.0/19 | 8.2k | RIPE NCC | GB | 21st Dec 2005 |
| 88.82.224.0/19 | 8.2k | RIPE NCC | DE | 27th Dec 2005 |
| 89.104.107.0/24 | 256 | RIPE NCC | RU | 9th Mar 2006 |
| 89.104.119.0/24 | 256 | RIPE NCC | RU | 9th Mar 2006 |
| 89.104.125.0/24 | 256 | RIPE NCC | RU | 9th Mar 2006 |
| 89.104.32.0/19 | 8.2k | RIPE NCC | GB | 1st Mar 2006 |
| 89.105.128.0/21 | 2k | RIPE NCC | RU | 16th Mar 2006 |
| 89.105.72.0/22 | 1k | RIPE NCC |  IT | 15th Mar 2006 |
| 89.105.80.0/21 | 2k | RIPE NCC | IT | 15th Mar 2006 |
| 89.106.102.0/23 | 512 | RIPE NCC | BG | 23rd Mar 2006 |
| 89.106.104.0/23 | 512 | RIPE NCC | BG | 23rd Mar 2006 |
| 89.106.144.0/21 | 2k | RIPE NCC | GB | 30th Mar 2006 |
| 89.106.201.0/24 | 256 | RIPE NCC | CH | 25th Jan 2022 |
| 89.106.204.0/24 | 256 | RIPE NCC | NL | 25th Jan 2022 |