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 Russia
2,085 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 80.90.68.0/22 | 1k | RIPE NCC |  RU | 6th Sept 2001 |
| 80.90.72.0/21 | 2k | RIPE NCC | RU | 6th Sept 2001 |
| 80.92.160.0/20 | 4.1k | RIPE NCC | RU | 24th Sept 2001 |
| 81.163.64.0/21 | 2k | RIPE NCC | RU | 25th Aug 2011 |
| 81.163.88.0/21 | 2k | RIPE NCC | RU | 30th Aug 2011 |
| 81.201.64.0/20 | 4.1k | RIPE NCC | RU | 10th Oct 2002 |
| 81.22.194.0/23 | 512 | RIPE NCC | RU | 25th Feb 2002 |
| 81.28.0.0/22 | 1k | RIPE NCC | RU | 16th Apr 2002 |
| 81.95.208.0/20 | 4.1k | RIPE NCC | RU | 31st May 2006 |
| 82.198.0.0/20 | 4.1k | RIPE NCC | RU | 14th Nov 2003 |
| 83.217.32.0/19 | 8.2k | RIPE NCC | RU | 4th Mar 2004 |
| 83.222.20.0/22 | 1k | RIPE NCC | RU | 21st Apr 2004 |
| 83.242.106.0/24 | 256 | RIPE NCC | RU | 12th Mar 2012 |
| 84.38.0.0/24 | 256 | RIPE NCC | RU | 31st May 2012 |
| 84.38.6.0/23 | 512 | RIPE NCC | RU | 31st May 2012 |
| 84.47.181.0/24 | 256 | RIPE NCC | RU | 15th Oct 2004 |
| 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.198.100.0/22 | 1k | RIPE NCC | RU | 31st Jan 2005 |
| 85.198.84.0/22 | 1k | RIPE NCC | RU | 31st Jan 2005 |
| 85.198.92.0/22 | 1k | RIPE NCC | RU | 31st Jan 2005 |
| 85.198.96.0/22 | 1k | RIPE NCC | RU | 31st Jan 2005 |
| 85.209.196.0/22 | 1k | RIPE NCC | RU | 27th Feb 2019 |
| 85.8.215.0/24 | 256 | RIPE NCC | RU | 26th Jun 2026 |
| 85.91.104.0/24 | 256 | RIPE NCC | RU | 22nd Nov 2004 |
| 85.91.106.0/24 | 256 | RIPE NCC | RU | 22nd Nov 2004 |
| 85.92.0.0/19 | 8.2k | RIPE NCC | RU | 2nd Dec 2004 |
| 86.110.195.0/24 | 256 | RIPE NCC | RU | 26th Jul 2005 |
| 86.110.213.0/24 | 256 | RIPE NCC | RU | 26th Jul 2005 |
| 86.110.214.0/24 | 256 | RIPE NCC | RU | 26th Jul 2005 |
| 87.117.139.0/24 | 256 | RIPE NCC | RU | 28th Sept 2005 |
| 87.117.144.0/23 | 512 | RIPE NCC | RU | 28th Sept 2005 |
| 87.117.150.0/23 | 512 | RIPE NCC | RU | 28th Sept 2005 |
| 87.236.40.0/21 | 2k | RIPE NCC | RU | 21st Jul 2005 |
| 87.236.87.0/24 | 256 | RIPE NCC | RU | 12th Aug 2005 |
| 87.239.34.0/24 | 256 | RIPE NCC | RU | 22nd Sept 2009 |
| 87.242.66.0/24 | 256 | RIPE NCC | RU | 22nd Jul 2005 |
| 87.249.60.0/24 | 256 | RIPE NCC | RU | 25th Aug 2005 |
| 88.151.104.0/21 | 2k | RIPE NCC | RU | 28th Feb 2006 |
| 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.210.7.0/24 | 256 | RIPE NCC | RU | 24th Nov 2005 |
| 88.218.244.0/22 | 1k | RIPE NCC | RU | 18th Dec 2018 |
| 88.81.32.0/19 | 8.2k | RIPE NCC | RU | 2nd Oct 2009 |
| 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.105.128.0/21 | 2k | RIPE NCC | RU | 16th Mar 2006 |
| 89.169.192.0/18 | 16.4k | RIPE NCC | RU | 24th Feb 2006 |
| 89.17.48.0/24 | 256 | RIPE NCC | RU | 20th Jul 2006 |