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,050 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 193.232.232.0/23 | 512 | RIPE NCC | 9th Jun 1993 | |
| 193.232.242.0/24 | 256 | RIPE NCC | 9th Jun 1993 | |
| 193.232.244.0/24 | 256 | RIPE NCC | 9th Jun 1993 | |
| 193.232.71.0/24 | 256 | RIPE NCC | 9th Jun 1993 | |
| 193.232.76.0/24 | 256 | RIPE NCC | 9th Jun 1993 | |
| 193.232.78.0/24 | 256 | RIPE NCC | 9th Jun 1993 | |
| 193.232.87.0/24 | 256 | RIPE NCC | 9th Jun 1993 | |
| 193.232.92.0/24 | 256 | RIPE NCC | 9th Jun 1993 | |
| 193.238.116.0/24 | 256 | RIPE NCC | 11th Mar 2005 | |
| 193.238.45.0/24 | 256 | RIPE NCC | 11th May 2018 | |
| 193.239.229.0/24 | 256 | RIPE NCC | 27th Nov 2024 | |
| 193.242.106.0/24 | 256 | RIPE NCC | 19th Nov 2019 | |
| 193.242.109.0/24 | 256 | RIPE NCC | 19th Nov 2019 | |
| 193.242.153.0/24 | 256 | RIPE NCC | 19th Nov 2019 | |
| 193.243.161.0/24 | 256 | RIPE NCC | 19th Nov 2019 | |
| 193.243.182.0/24 | 256 | RIPE NCC | 19th Nov 2019 | |
| 193.246.153.0/24 | 256 | RIPE NCC | 19th Nov 2019 | |
| 193.246.206.0/24 | 256 | RIPE NCC | 19th Nov 2019 | |
| 193.246.245.0/24 | 256 | RIPE NCC | 19th Nov 2019 | |
| 193.246.51.0/24 | 256 | RIPE NCC | 19th Nov 2019 | |
| 193.27.230.0/23 | 512 | RIPE NCC | 20th Jan 2004 | |
| 193.27.36.0/22 | 1k | RIPE NCC | 10th Jul 2018 | |
| 193.28.186.0/24 | 256 | RIPE NCC | 12th Jul 2023 | |
| 193.28.6.0/24 | 256 | RIPE NCC | 8th Dec 2008 | |
| 193.30.108.0/24 | 256 | RIPE NCC | 23rd Mar 2022 | |
| 193.32.196.0/23 | 512 | RIPE NCC | 18th Oct 2018 | |
| 193.32.200.0/23 | 512 | RIPE NCC | 18th Oct 2018 | |
| 193.34.200.128/25 | 128 | RIPE NCC | 3rd Dec 2009 | |
| 193.34.203.0/25 | 128 | RIPE NCC | 6th Apr 2010 | |
| 193.35.109.0/24 | 256 | RIPE NCC | 16th Sept 2011 | |
| 193.36.56.0/22 | 1k | RIPE NCC | 12th Sept 2018 | |
| 193.37.141.0/24 | 256 | RIPE NCC | 17th Oct 2006 | |
| 193.43.146.0/23 | 512 | RIPE NCC | 9th Oct 2019 | |
| 193.43.72.0/24 | 256 | RIPE NCC | 14th Nov 2019 | |
| 193.46.207.0/24 | 256 | RIPE NCC | 20th Aug 2007 | |
| 193.56.188.0/24 | 256 | RIPE NCC | 15th Nov 2019 | |
| 193.56.190.0/24 | 256 | RIPE NCC | 15th Nov 2019 | |
| 193.56.30.0/24 | 256 | RIPE NCC | 4th Jul 2025 | |
| 193.93.192.0/22 | 1k | RIPE NCC | 26th Mar 2010 | |
| 193.93.61.0/24 | 256 | RIPE NCC | 27th Feb 2006 | |
| 194.0.121.0/24 | 256 | RIPE NCC | 30th Oct 2006 | |
| 194.110.223.0/24 | 256 | RIPE NCC | 12th Apr 2007 | |
| 194.110.71.0/24 | 256 | RIPE NCC | 3rd Feb 2026 | |
| 194.110.80.0/22 | 1k | RIPE NCC | 25th Sept 2018 | |
| 194.113.209.0/24 | 256 | RIPE NCC | 22nd Nov 2019 | |
| 194.116.162.0/23 | 512 | RIPE NCC | 20th Jan 2005 | |
| 194.116.190.0/23 | 512 | RIPE NCC | 30th Oct 2019 | |
| 194.116.214.0/23 | 512 | RIPE NCC | 30th Oct 2019 | |
| 194.116.216.0/23 | 512 | RIPE NCC | 30th Oct 2019 | |
| 194.117.50.128/25 | 128 | RIPE NCC | 10th Mar 2005 |