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,650 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 84.254.123.0/24 | 256 | RIPE NCC |  DE | 6th Oct 2004 |
| 84.38.0.0/24 | 256 | RIPE NCC |  RU | 31st May 2012 |
| 84.38.112.0/20 | 4.1k | RIPE NCC |  AT | 23rd May 2006 |
| 84.38.240.0/24 | 256 | RIPE NCC |  SI | 31st May 2023 |
| 84.38.247.0/24 | 256 | RIPE NCC |  US | 5th Jun 2023 |
| 84.38.254.0/24 | 256 | RIPE NCC |  GB | 6th Jun 2023 |
| 84.38.32.0/20 | 4.1k | RIPE NCC | GB | 13th Apr 2006 |
| 84.38.6.0/23 | 512 | RIPE NCC | RU | 31st May 2012 |
| 84.38.96.0/20 | 4.1k | RIPE NCC |  PL | 22nd May 2006 |
| 84.39.184.0/21 | 2k | RIPE NCC | AT | 3rd Sept 2012 |
| 84.40.48.0/21 | 2k | RIPE NCC | GB | 16th Aug 2004 |
| 84.46.200.0/24 | 256 | RIPE NCC |  LT | 11th Oct 2004 |
| 84.47.166.0/23 | 512 | RIPE NCC |  RO | 15th Oct 2004 |
| 84.47.181.0/24 | 256 | RIPE NCC | RU | 15th Oct 2004 |
| 84.54.15.0/24 | 256 | RIPE NCC |  TR | 15th Nov 2018 |
| 84.54.40.0/22 | 1k | RIPE NCC |  NL | 15th Nov 2018 |
| 84.54.54.0/24 | 256 | RIPE NCC |  AE | 15th Nov 2018 |
| 85.115.204.0/22 | 1k | RIPE NCC |  EE | 9th Oct 2018 |
| 85.116.0.0/19 | 8.2k | RIPE NCC | GB | 4th Mar 2005 |
| 85.116.240.0/21 | 2k | RIPE NCC |  IT | 16th Mar 2005 |
| 85.116.252.0/24 | 256 | RIPE NCC | IT | 16th Mar 2005 |
| 85.116.253.0/24 | 256 | RIPE NCC | IT | 16th Mar 2005 |
| 85.117.234.0/23 | 512 | RIPE NCC | RU | 9th Oct 2018 |
| 85.118.136.0/21 | 2k | RIPE NCC | RU | 21st Apr 2005 |
| 85.119.112.0/21 | 2k | RIPE NCC | GB | 8th Jun 2005 |
| 85.119.152.0/21 | 2k | RIPE NCC | DE | 15th Jun 2005 |
| 85.12.120.0/22 | 1k | RIPE NCC | GB | 7th Mar 2005 |
| 85.12.126.0/24 | 256 | RIPE NCC | GB | 7th Mar 2005 |
| 85.12.127.0/24 | 256 | RIPE NCC | GB | 7th Mar 2005 |
| 85.12.96.0/20 | 4.1k | RIPE NCC | GB | 7th Mar 2005 |
| 85.131.160.0/19 | 8.2k | ARIN |  CA | 4th Apr 2024 |
| 85.134.128.0/17 | 32.8k | RIPE NCC | US | 14th Dec 2004 |
| 85.136.196.0/22 | 1k | RIPE NCC | LT | 3rd Nov 2004 |
| 85.136.210.0/23 | 512 | RIPE NCC |  CY | 3rd Nov 2004 |
| 85.136.88.0/21 | 2k | RIPE NCC | US | 3rd Nov 2004 |
| 85.136.96.0/21 | 2k | RIPE NCC | US | 3rd Nov 2004 |
| 85.137.176.0/22 | 1k | RIPE NCC | LT | 3rd Nov 2004 |
| 85.137.180.0/24 | 256 | RIPE NCC |  ES | 3rd Nov 2004 |
| 85.137.181.0/24 | 256 | RIPE NCC |  KN | 3rd Nov 2004 |
| 85.137.182.0/24 | 256 | RIPE NCC |  NO | 3rd Nov 2004 |
| 85.137.20.0/22 | 1k | RIPE NCC | CY | 3rd Nov 2004 |
| 85.137.208.0/22 | 1k | RIPE NCC | LT | 3rd Nov 2004 |
| 85.137.215.0/24 | 256 | RIPE NCC | LT | 3rd Nov 2004 |
| 85.137.236.0/24 | 256 | RIPE NCC | NL | 3rd Nov 2004 |
| 85.137.80.0/24 | 256 | RIPE NCC | NO | 3rd Nov 2004 |
| 85.137.81.0/24 | 256 | RIPE NCC |  GE | 3rd Nov 2004 |
| 85.137.82.0/23 | 512 | RIPE NCC | ES | 3rd Nov 2004 |
| 85.149.240.0/20 | 4.1k | RIPE NCC | US | 6th Oct 2004 |
| 85.155.10.0/23 | 512 | RIPE NCC | ES | 5th Nov 2004 |
| 85.155.12.0/23 | 512 | RIPE NCC | ES | 5th Nov 2004 |