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 Ukraine
500 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 185.36.196.0/22 | 1k | RIPE NCC | 2nd Oct 2013 | |
| 185.37.10.0/24 | 256 | RIPE NCC | 7th Mar 2023 | |
| 185.72.48.0/22 | 1k | RIPE NCC | 3rd Oct 2014 | |
| 185.89.100.0/22 | 1k | RIPE NCC | 24th Feb 2015 | |
| 188.191.144.0/23 | 512 | RIPE NCC | 21st Feb 2011 | |
| 192.166.128.0/22 | 1k | RIPE NCC | 7th Mar 2011 | |
| 192.245.152.0/24 | 256 | RIPE NCC | 9th Nov 1992 | |
| 193.105.171.0/24 | 256 | RIPE NCC | 4th Mar 2010 | |
| 193.106.220.0/22 | 1k | RIPE NCC | 20th Jan 2010 | |
| 193.108.120.0/22 | 1k | RIPE NCC | 8th May 2001 | |
| 193.109.168.0/22 | 1k | RIPE NCC | 4th May 2018 | |
| 193.110.124.0/22 | 1k | RIPE NCC | 8th Jan 2002 | |
| 193.110.176.0/23 | 512 | RIPE NCC | 8th Jan 2002 | |
| 193.111.239.0/24 | 256 | RIPE NCC | 22nd May 2002 | |
| 193.150.28.0/22 | 1k | RIPE NCC | 13th Oct 2011 | |
| 193.162.78.0/24 | 256 | RIPE NCC | 12th Oct 2020 | |
| 193.17.69.0/24 | 256 | RIPE NCC | 9th Jun 2004 | |
| 193.178.162.0/24 | 256 | RIPE NCC | 23rd Mar 2005 | |
| 193.201.100.0/24 | 256 | RIPE NCC | 18th Jun 2002 | |
| 193.201.152.128/25 | 128 | RIPE NCC | 27th Nov 2003 | |
| 193.201.224.0/22 | 1k | RIPE NCC | 23rd Jul 2002 | |
| 193.203.236.0/23 | 512 | RIPE NCC | 28th Jan 2000 | |
| 193.23.140.0/24 | 256 | RIPE NCC | 19th Feb 2009 | |
| 193.23.183.0/24 | 256 | RIPE NCC | 19th Dec 2003 | |
| 193.238.96.0/22 | 1k | RIPE NCC | 4th Mar 2005 | |
| 193.239.250.0/23 | 512 | RIPE NCC | 2nd Aug 2005 | |
| 193.242.166.0/24 | 256 | RIPE NCC | 21st Jun 2012 | |
| 193.25.180.0/23 | 512 | RIPE NCC | 15th Mar 2004 | |
| 193.254.232.0/23 | 512 | RIPE NCC | 23rd Sept 2002 | |
| 193.33.152.0/24 | 256 | RIPE NCC | 15th May 2024 | |
| 193.33.54.0/23 | 512 | RIPE NCC | 7th Feb 2007 | |
| 193.34.196.128/25 | 128 | RIPE NCC | 30th Nov 2023 | |
| 193.41.129.0/24 | 256 | RIPE NCC | 13th Nov 2000 | |
| 193.41.80.0/24 | 256 | RIPE NCC | 2nd Nov 2000 | |
| 193.42.104.0/22 | 1k | RIPE NCC | 23rd Oct 2018 | |
| 193.43.222.0/23 | 512 | RIPE NCC | 3rd Oct 2005 | |
| 193.46.185.0/24 | 256 | RIPE NCC | 13th Feb 2023 | |
| 193.46.89.0/24 | 256 | RIPE NCC | 7th Aug 2007 | |
| 194.0.150.0/24 | 256 | RIPE NCC | 3rd Jan 2007 | |
| 194.0.56.0/23 | 512 | RIPE NCC | 14th Sept 2012 | |
| 194.110.252.0/24 | 256 | RIPE NCC | 13th Nov 2009 | |
| 194.126.224.0/24 | 256 | RIPE NCC | 11th Feb 2005 | |
| 194.146.112.0/24 | 256 | RIPE NCC | 23rd Sept 2003 | |
| 194.169.205.0/24 | 256 | RIPE NCC | 4th Dec 2006 | |
| 194.169.206.0/24 | 256 | RIPE NCC | 4th Dec 2006 | |
| 194.177.15.0/24 | 256 | RIPE NCC | 12th Feb 2024 | |
| 194.187.228.0/22 | 1k | RIPE NCC | 21st Sept 2005 | |
| 194.26.0.0/24 | 256 | RIPE NCC | 8th May 2025 | |
| 194.28.132.0/22 | 1k | RIPE NCC | 6th May 2010 | |
| 194.28.16.0/22 | 1k | RIPE NCC | 16th Apr 2010 |