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 Ukraine
505 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 2a14:1c00::/29 | 34.4B × /64 | RIPE NCC | 3rd May 2024 | |
| 2a14:2000::/29 | 34.4B × /64 | RIPE NCC | 12th Oct 2023 | |
| 2a14:5880::/29 | 34.4B × /64 | RIPE NCC | 28th Dec 2023 | |
| 2a14:6200::/29 | 34.4B × /64 | RIPE NCC | 2nd Nov 2023 | |
| 2a14:7280::/29 | 34.4B × /64 | RIPE NCC | 12th Jan 2024 | |
| 2a14:7480::/29 | 34.4B × /64 | RIPE NCC | 12th Jan 2024 | |
| 2a14:aa00::/32 | 4.3B × /64 | RIPE NCC | 17th Dec 2024 | |
| 2a14:b080::/29 | 34.4B × /64 | RIPE NCC | 10th Mar 2025 | |
| 2a14:f40::/29 | 34.4B × /64 | RIPE NCC | 4th Mar 2024 | |
| 31.41.104.0/21 | 2k | RIPE NCC | 28th Mar 2011 | |
| 31.41.128.0/21 | 2k | RIPE NCC | 29th Mar 2011 | |
| 31.43.164.0/23 | 512 | RIPE NCC | 1st Mar 2011 | |
| 31.43.185.0/24 | 256 | RIPE NCC | 1st Mar 2011 | |
| 31.43.188.0/23 | 512 | RIPE NCC | 1st Mar 2011 | |
| 31.43.190.0/24 | 256 | RIPE NCC | 1st Mar 2011 | |
| 37.143.88.0/21 | 2k | RIPE NCC | 2nd Mar 2012 | |
| 45.153.174.0/24 | 256 | RIPE NCC | 29th Jan 2026 | |
| 45.154.128.0/22 | 1k | RIPE NCC | 16th Sept 2019 | |
| 46.16.165.0/24 | 256 | RIPE NCC | 7th Oct 2010 | |
| 46.29.128.0/21 | 2k | RIPE NCC | 11th Aug 2010 | |
| 5.180.176.0/24 | 256 | RIPE NCC | 19th May 2021 | |
| 5.207.0.0/16 | 65.5k | RIPE NCC | 5th Sept 2012 | |
| 62.106.84.0/24 | 256 | RIPE NCC | 8th Oct 2021 | |
| 62.182.160.0/21 | 2k | RIPE NCC | 31st Mar 2008 | |
| 77.95.171.0/24 | 256 | RIPE NCC | 17th Jan 2025 | |
| 77.95.173.0/24 | 256 | RIPE NCC | 17th Jan 2025 | |
| 78.41.56.0/24 | 256 | RIPE NCC | 17th Jan 2025 | |
| 79.110.16.0/20 | 4.1k | RIPE NCC | 4th Mar 2008 | |
| 80.70.80.0/20 | 4.1k | RIPE NCC | 27th May 2004 | |
| 83.137.88.0/21 | 2k | RIPE NCC | 14th May 2004 | |
| 84.246.107.0/24 | 256 | RIPE NCC | 17th Aug 2021 | |
| 88.151.113.0/24 | 256 | RIPE NCC | 25th Apr 2022 | |
| 89.19.128.0/19 | 8.2k | RIPE NCC | 24th Aug 2006 | |
| 91.105.208.0/21 | 2k | RIPE NCC | 13th Aug 2012 | |
| 91.193.204.0/22 | 1k | RIPE NCC | 3rd May 2007 | |
| 91.193.76.0/22 | 1k | RIPE NCC | 3rd Apr 2007 | |
| 91.194.40.0/23 | 512 | RIPE NCC | 14th Sept 2009 | |
| 91.196.88.0/22 | 1k | RIPE NCC | 1st Jun 2007 | |
| 91.198.140.0/24 | 256 | RIPE NCC | 20th Sept 2007 | |
| 91.198.235.0/24 | 256 | RIPE NCC | 29th Oct 2007 | |
| 91.199.144.0/24 | 256 | RIPE NCC | 28th Jan 2008 | |
| 91.199.222.0/24 | 256 | RIPE NCC | 29th Feb 2008 | |
| 91.199.35.0/24 | 256 | RIPE NCC | 21st Nov 2007 | |
| 91.204.112.0/22 | 1k | RIPE NCC | 12th Aug 2011 | |
| 91.204.12.0/22 | 1k | RIPE NCC | 26th May 2008 | |
| 91.206.186.0/23 | 512 | RIPE NCC | 7th Aug 2008 | |
| 91.207.46.0/23 | 512 | RIPE NCC | 25th Sept 2008 | |
| 91.208.153.0/24 | 256 | RIPE NCC | 19th Aug 2008 | |
| 91.209.138.0/24 | 256 | RIPE NCC | 20th Nov 2008 | |
| 91.209.176.0/24 | 256 | RIPE NCC | 3rd Dec 2008 |