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
84,783 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 87.120.168.0/21 | 2k | RIPE NCC |  SA | 12th Jul 2005 |
| 87.120.48.0/21 | 2k | ARIN |  US | 22nd May 2024 |
| 87.120.88.0/23 | 512 | RIPE NCC |  BG | 12th Jul 2005 |
| 87.121.144.0/23 | 512 | RIPE NCC | BG | 12th Jul 2005 |
| 87.121.146.0/23 | 512 | RIPE NCC | BG | 12th Jul 2005 |
| 87.121.176.0/20 | 4.1k | RIPE NCC | SA | 12th Jul 2005 |
| 87.121.222.0/24 | 256 | RIPE NCC |  GB | 12th Jul 2005 |
| 87.121.223.0/24 | 256 | RIPE NCC | BG | 12th Jul 2005 |
| 87.121.240.0/21 | 2k | RIPE NCC | SA | 12th Jul 2005 |
| 87.121.28.0/22 | 1k | RIPE NCC |  DE | 12th Jul 2005 |
| 87.121.60.0/23 | 512 | RIPE NCC |  AL | 12th Jul 2005 |
| 87.121.98.0/24 | 256 | RIPE NCC | BG | 12th Jul 2005 |
| 87.192.0.0/18 | 16.4k | RIPE NCC |  IE | 3rd Jun 2005 |
| 87.199.112.0/21 | 2k | RIPE NCC |  PL | 28th Jun 2006 |
| 87.199.120.0/22 | 1k | APNIC |  HK | 28th Jun 2006 |
| 87.199.126.0/24 | 256 | RIPE NCC | DE | 28th Jun 2006 |
| 87.199.132.0/24 | 256 | RIPE NCC |  KZ | 28th Jun 2006 |
| 87.199.133.0/24 | 256 | RIPE NCC | KZ | 28th Jun 2006 |
| 87.199.134.0/23 | 512 | RIPE NCC | KZ | 28th Jun 2006 |
| 87.199.144.0/22 | 1k | RIPE NCC | PL | 28th Jun 2006 |
| 87.199.148.0/22 | 1k | RIPE NCC | DE | 28th Jun 2006 |
| 87.199.156.0/22 | 1k | RIPE NCC | PL | 28th Jun 2006 |
| 87.199.96.0/20 | 4.1k | RIPE NCC | PL | 28th Jun 2006 |
| 87.230.32.0/22 | 1k | RIPE NCC | DE | 25th Jul 2005 |
| 87.230.48.0/23 | 512 | RIPE NCC | DE | 25th Jul 2005 |
| 87.230.64.0/24 | 256 | RIPE NCC | DE | 25th Jul 2005 |
| 87.230.65.0/24 | 256 | RIPE NCC | DE | 25th Jul 2005 |
| 87.230.66.0/23 | 512 | RIPE NCC | DE | 25th Jul 2005 |
| 87.230.68.0/22 | 1k | RIPE NCC | DE | 25th Jul 2005 |
| 87.230.76.0/22 | 1k | RIPE NCC | DE | 25th Jul 2005 |
| 87.230.80.0/23 | 512 | RIPE NCC | DE | 25th Jul 2005 |
| 87.232.160.0/19 | 8.2k | RIPE NCC |  IT | 1st Jul 2005 |
| 87.236.163.0/24 | 256 | RIPE NCC |  NL | 19th Aug 2021 |
| 87.236.165.0/24 | 256 | RIPE NCC | GB | 19th Aug 2021 |
| 87.236.166.0/24 | 256 | RIPE NCC |  AU | 19th Aug 2021 |
| 87.236.178.0/23 | 512 | RIPE NCC |  CH | 31st Aug 2005 |
| 87.236.36.0/24 | 256 | RIPE NCC | PL | 8th Mar 2023 |
| 87.236.40.0/21 | 2k | RIPE NCC |  RU | 21st Jul 2005 |
| 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 |