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
85,356 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 212.6.60.0/24 | 256 | RIPE NCC |  IT | 15th Jan 2020 |
| 212.62.128.0/18 | 16.4k | RIPE NCC |  FR | 14th May 1998 |
| 212.63.160.0/19 | 8.2k | RIPE NCC |  DE | 17th Mar 1999 |
| 212.67.0.0/21 | 2k | RIPE NCC |  RU | 27th Oct 1998 |
| 212.67.128.0/19 | 8.2k | RIPE NCC |  PL | 29th Jan 2008 |
| 212.67.20.0/22 | 1k | RIPE NCC | RU | 27th Oct 1998 |
| 212.68.52.0/24 | 256 | RIPE NCC |  TR | 14th May 2008 |
| 212.7.96.0/19 | 8.2k | RIPE NCC | RU | 7th Oct 2009 |
| 212.70.136.0/23 | 512 | RIPE NCC |  BG | 4th Dec 2007 |
| 212.70.148.0/23 | 512 | RIPE NCC | BG | 4th Dec 2007 |
| 212.72.213.0/24 | 256 | RIPE NCC | BG | 21st Apr 1999 |
| 212.72.220.0/24 | 256 | RIPE NCC | BG | 21st Apr 1999 |
| 212.72.222.0/23 | 512 | RIPE NCC | BG | 21st Apr 1999 |
| 212.74.231.0/24 | 256 | RIPE NCC | RU | 26th May 2000 |
| 212.78.109.0/24 | 256 | RIPE NCC | DE | 10th Nov 1999 |
| 212.78.110.0/23 | 512 | RIPE NCC | DE | 10th Nov 1999 |
| 212.78.252.0/22 | 1k | RIPE NCC |  IE | 16th Jun 2008 |
| 212.78.96.0/21 | 2k | RIPE NCC | DE | 10th Nov 1999 |
| 212.79.224.0/19 | 8.2k | RIPE NCC | DE | 19th May 2000 |
| 212.8.237.0/24 | 256 | RIPE NCC | RU | 22nd Sept 1999 |
| 212.84.0.0/19 | 8.2k | RIPE NCC |  NL | 30th Sept 1998 |
| 212.86.107.0/24 | 256 | RIPE NCC |  GI | 10th Nov 1999 |
| 212.88.192.0/19 | 8.2k | RIPE NCC | DE | 21st Apr 1999 |
| 212.92.120.0/22 | 1k | RIPE NCC | NL | 3rd Nov 1999 |
| 212.97.72.0/21 | 2k | RIPE NCC |  GB | 5th Feb 1999 |
| 213.108.26.0/23 | 512 | RIPE NCC |  NO | 4th Jun 2009 |
| 213.108.30.0/24 | 256 | RIPE NCC | PL | 4th Jun 2009 |
| 213.109.104.0/22 | 1k | RIPE NCC |  US | 9th Sept 2009 |
| 213.109.180.0/22 | 1k | RIPE NCC | GB | 6th Nov 2018 |
| 213.109.198.0/24 | 256 | RIPE NCC |  CY | 4th Oct 2021 |
| 213.109.205.0/24 | 256 | RIPE NCC | CY | 4th Oct 2021 |
| 213.109.207.0/24 | 256 | RIPE NCC |  HR | 4th Oct 2021 |
| 213.109.73.0/24 | 256 | RIPE NCC | FR | 6th May 2024 |
| 213.110.230.0/23 | 512 | RIPE NCC |  UZ | 22nd Sept 2009 |
| 213.110.232.0/22 | 1k | RIPE NCC | RU | 22nd Sept 2009 |
| 213.110.236.0/23 | 512 | RIPE NCC | RU | 22nd Sept 2009 |
| 213.12.0.0/16 | 65.5k | RIPE NCC | GB | 24th Aug 1999 |
| 213.130.68.0/23 | 512 | RIPE NCC | HR | 7th Mar 2000 |
| 213.130.95.0/24 | 256 | RIPE NCC | BG | 7th Mar 2000 |
| 213.134.16.0/24 | 256 | RIPE NCC |  ES | 9th Jan 2024 |
| 213.134.18.0/24 | 256 | RIPE NCC | RU | 9th Jan 2024 |
| 213.134.19.0/24 | 256 | RIPE NCC |  MT | 9th Jan 2024 |
| 213.134.24.0/24 | 256 | RIPE NCC | US | 16th Jan 2024 |
| 213.134.28.0/24 | 256 | RIPE NCC | US | 22nd Jan 2024 |
| 213.134.3.0/24 | 256 | RIPE NCC | DE | 9th Jan 2024 |
| 213.134.8.0/24 | 256 | RIPE NCC | RU | 9th Jan 2024 |
| 213.135.79.0/24 | 256 | RIPE NCC | RU | 5th Apr 2000 |
| 213.138.0.0/19 | 8.2k | RIPE NCC | FR | 28th May 2008 |
| 213.139.229.0/24 | 256 | RIPE NCC | RU | 3rd Dec 2018 |
| 213.139.248.0/22 | 1k | RIPE NCC | RU | 4th Dec 2018 |