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 in Russia
2,050 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 88.151.104.0/21 | 2k | RIPE NCC | 28th Feb 2006 | |
| 88.210.28.0/24 | 256 | RIPE NCC | 24th Nov 2005 | |
| 88.210.51.0/24 | 256 | RIPE NCC | 24th Nov 2005 | |
| 88.218.244.0/22 | 1k | RIPE NCC | 18th Dec 2018 | |
| 88.81.32.0/19 | 8.2k | RIPE NCC | 2nd Oct 2009 | |
| 89.104.107.0/24 | 256 | RIPE NCC | 9th Mar 2006 | |
| 89.104.119.0/24 | 256 | RIPE NCC | 9th Mar 2006 | |
| 89.104.125.0/24 | 256 | RIPE NCC | 9th Mar 2006 | |
| 89.105.128.0/21 | 2k | RIPE NCC | 16th Mar 2006 | |
| 89.169.192.0/18 | 16.4k | RIPE NCC | 24th Feb 2006 | |
| 89.17.48.0/24 | 256 | RIPE NCC | 20th Jul 2006 | |
| 89.17.50.0/24 | 256 | RIPE NCC | 20th Jul 2006 | |
| 89.191.224.0/24 | 256 | RIPE NCC | 22nd Jun 2006 | |
| 89.191.227.0/24 | 256 | RIPE NCC | 22nd Jun 2006 | |
| 89.191.230.0/24 | 256 | RIPE NCC | 22nd Jun 2006 | |
| 89.191.231.0/24 | 256 | RIPE NCC | 22nd Jun 2006 | |
| 89.191.233.0/24 | 256 | RIPE NCC | 22nd Jun 2006 | |
| 89.191.235.0/24 | 256 | RIPE NCC | 22nd Jun 2006 | |
| 89.207.158.0/24 | 256 | RIPE NCC | 3rd Oct 2023 | |
| 89.207.32.0/21 | 2k | RIPE NCC | 20th May 2009 | |
| 89.207.40.0/21 | 2k | RIPE NCC | 7th Jun 2006 | |
| 89.207.96.0/21 | 2k | RIPE NCC | 15th Jun 2006 | |
| 89.221.200.0/23 | 512 | RIPE NCC | 9th Oct 2006 | |
| 89.221.202.0/24 | 256 | RIPE NCC | 9th Oct 2006 | |
| 89.223.13.0/24 | 256 | RIPE NCC | 19th Sept 2006 | |
| 89.223.21.0/24 | 256 | RIPE NCC | 19th Sept 2006 | |
| 89.223.6.0/23 | 512 | RIPE NCC | 19th Sept 2006 | |
| 89.249.144.0/20 | 4.1k | RIPE NCC | 21st Jul 2006 | |
| 89.249.50.0/24 | 256 | RIPE NCC | 19th Jul 2006 | |
| 89.40.204.0/24 | 256 | RIPE NCC | 29th Nov 2005 | |
| 90.156.176.0/20 | 4.1k | RIPE NCC | 17th Nov 2006 | |
| 91.105.194.0/23 | 512 | RIPE NCC | 13th Aug 2012 | |
| 91.107.104.0/21 | 2k | RIPE NCC | 21st Jun 2012 | |
| 91.107.119.0/24 | 256 | RIPE NCC | 21st Jun 2012 | |
| 91.132.188.0/22 | 1k | RIPE NCC | 20th Dec 2018 | |
| 91.151.32.0/20 | 4.1k | RIPE NCC | 5th Dec 2006 | |
| 91.184.254.0/23 | 512 | RIPE NCC | 16th Oct 2006 | |
| 91.189.48.0/21 | 2k | RIPE NCC | 11th Jan 2007 | |
| 91.193.25.0/24 | 256 | RIPE NCC | 7th Aug 2023 | |
| 91.193.36.0/22 | 1k | RIPE NCC | 27th Mar 2007 | |
| 91.194.164.0/23 | 512 | RIPE NCC | 27th Jun 2007 | |
| 91.194.206.0/23 | 512 | RIPE NCC | 10th Jul 2007 | |
| 91.194.64.0/23 | 512 | RIPE NCC | 5th Jun 2007 | |
| 91.195.148.0/23 | 512 | RIPE NCC | 21st Sept 2007 | |
| 91.196.60.0/22 | 1k | RIPE NCC | 14th Oct 2009 | |
| 91.197.183.0/24 | 256 | RIPE NCC | 10th Sept 2007 | |
| 91.197.236.0/22 | 1k | RIPE NCC | 18th Sept 2007 | |
| 91.198.127.0/24 | 256 | RIPE NCC | 31st Mar 2010 | |
| 91.198.212.0/24 | 256 | RIPE NCC | 18th Oct 2007 | |
| 91.198.69.0/24 | 256 | RIPE NCC | 29th Aug 2007 |