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 |
|---|---|---|---|---|
| 103.193.165.0/24 | 256 | RIPE NCC | 31st Jul 2015 | |
| 139.100.0.0/23 | 512 | RIPE NCC | 15th Feb 1990 | |
| 141.170.224.0/19 | 8.2k | RIPE NCC | 4th Jul 2011 | |
| 146.19.204.0/24 | 256 | RIPE NCC | 17th Nov 2021 | |
| 151.249.96.0/21 | 2k | RIPE NCC | 21st Aug 2012 | |
| 159.200.246.0/23 | 512 | RIPE NCC | 1st Sept 1993 | |
| 176.103.112.0/24 | 256 | RIPE NCC | 14th Dec 2011 | |
| 176.103.116.0/22 | 1k | RIPE NCC | 14th Dec 2011 | |
| 176.103.212.0/22 | 1k | RIPE NCC | 20th Dec 2011 | |
| 176.111.33.0/24 | 256 | RIPE NCC | 5th Mar 2012 | |
| 176.111.45.0/24 | 256 | RIPE NCC | 5th Mar 2012 | |
| 176.111.50.0/24 | 256 | RIPE NCC | 5th Mar 2012 | |
| 176.113.160.0/22 | 1k | RIPE NCC | 4th Apr 2012 | |
| 176.126.123.0/24 | 256 | RIPE NCC | 27th Oct 2021 | |
| 176.96.72.0/21 | 2k | RIPE NCC | 19th Jul 2011 | |
| 178.216.8.0/23 | 512 | RIPE NCC | 19th Mar 2010 | |
| 178.23.136.0/21 | 2k | RIPE NCC | 23rd Apr 2010 | |
| 185.0.29.0/24 | 256 | RIPE NCC | 11th Mar 2025 | |
| 185.0.48.0/22 | 1k | RIPE NCC | 29th Jul 2026 | |
| 185.1.111.0/24 | 256 | RIPE NCC | 15th Dec 2017 | |
| 185.1.134.0/24 | 256 | RIPE NCC | 29th Mar 2019 | |
| 185.1.146.0/24 | 256 | RIPE NCC | 26th Sept 2019 | |
| 185.1.16.0/24 | 256 | RIPE NCC | 17th Jul 2013 | |
| 185.1.194.0/24 | 256 | RIPE NCC | 5th Nov 2020 | |
| 185.1.196.0/24 | 256 | RIPE NCC | 5th Nov 2020 | |
| 185.1.198.0/24 | 256 | RIPE NCC | 22nd Jan 2021 | |
| 185.1.213.0/24 | 256 | RIPE NCC | 1st Jul 2021 | |
| 185.1.225.0/24 | 256 | RIPE NCC | 11th Nov 2021 | |
| 185.1.238.0/24 | 256 | RIPE NCC | 17th Mar 2022 | |
| 185.1.39.0/24 | 256 | RIPE NCC | 9th Oct 2015 | |
| 185.1.50.0/23 | 512 | RIPE NCC | 1st Oct 2015 | |
| 185.1.62.0/23 | 512 | RIPE NCC | 18th Dec 2015 | |
| 185.1.66.0/24 | 256 | RIPE NCC | 5th Nov 2020 | |
| 185.1.84.0/24 | 256 | RIPE NCC | 8th Nov 2016 | |
| 185.1.85.0/24 | 256 | RIPE NCC | 8th Nov 2016 | |
| 185.1.96.0/24 | 256 | RIPE NCC | 15th Sept 2017 | |
| 185.1.99.0/24 | 256 | RIPE NCC | 9th Oct 2017 | |
| 185.130.120.0/22 | 1k | RIPE NCC | 8th Dec 2015 | |
| 185.14.192.0/22 | 1k | RIPE NCC | 4th Jan 2013 | |
| 185.163.88.0/22 | 1k | RIPE NCC | 15th Aug 2016 | |
| 185.165.100.0/22 | 1k | RIPE NCC | 25th Aug 2016 | |
| 185.175.236.0/22 | 1k | RIPE NCC | 1st Nov 2016 | |
| 185.189.116.0/22 | 1k | RIPE NCC | 9th Feb 2017 | |
| 185.19.244.0/22 | 1k | RIPE NCC | 26th Feb 2013 | |
| 185.191.112.0/22 | 1k | RIPE NCC | 22nd Feb 2017 | |
| 185.191.172.0/22 | 1k | RIPE NCC | 10th Sept 2019 | |
| 185.191.80.0/22 | 1k | RIPE NCC | 22nd Feb 2017 | |
| 185.228.56.0/24 | 256 | RIPE NCC | 8th Feb 2023 | |
| 185.232.108.0/22 | 1k | RIPE NCC | 17th Nov 2017 | |
| 185.233.64.0/24 | 256 | RIPE NCC | 15th Jan 2021 |