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 Türkiye
698 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 2a14:cb80::/29 | 34.4B × /64 | RIPE NCC | 21st Mar 2025 | |
| 2a14:cf80::/29 | 34.4B × /64 | RIPE NCC | 25th Mar 2025 | |
| 2a14:d600::/29 | 34.4B × /64 | RIPE NCC | 23rd Dec 2024 | |
| 2a14:d700::/29 | 34.4B × /64 | RIPE NCC | 27th Jan 2025 | |
| 2a14:e400::/29 | 34.4B × /64 | RIPE NCC | 10th Dec 2024 | |
| 2a14:ea00::/29 | 34.4B × /64 | RIPE NCC | 24th Dec 2024 | |
| 2a14:f580::/29 | 34.4B × /64 | RIPE NCC | 22nd Apr 2025 | |
| 2a14:f600::/29 | 34.4B × /64 | RIPE NCC | 30th Dec 2024 | |
| 2a14:fd00::/29 | 34.4B × /64 | RIPE NCC | 11th Feb 2025 | |
| 2a14:fd80::/29 | 34.4B × /64 | RIPE NCC | 24th Apr 2025 | |
| 2a14:ff00::/29 | 34.4B × /64 | RIPE NCC | 12th Feb 2025 | |
| 31.14.218.0/24 | 256 | RIPE NCC | 18th Apr 2011 | |
| 31.14.232.0/24 | 256 | RIPE NCC | 18th Apr 2011 | |
| 31.14.253.0/24 | 256 | RIPE NCC | 18th Apr 2011 | |
| 31.14.64.0/24 | 256 | RIPE NCC | 18th Apr 2011 | |
| 31.176.0.0/17 | 32.8k | RIPE NCC | 4th Mar 2011 | |
| 31.210.58.0/23 | 512 | RIPE NCC | 4th May 2011 | |
| 31.24.254.0/24 | 256 | RIPE NCC | 29th Jun 2022 | |
| 37.1.144.0/24 | 256 | RIPE NCC | 12th Dec 2011 | |
| 37.1.146.0/23 | 512 | RIPE NCC | 12th Dec 2011 | |
| 37.1.148.0/23 | 512 | RIPE NCC | 12th Dec 2011 | |
| 37.1.150.0/24 | 256 | RIPE NCC | 12th Dec 2011 | |
| 37.122.224.0/20 | 4.1k | RIPE NCC | 15th Feb 2012 | |
| 37.123.0.0/18 | 16.4k | RIPE NCC | 15th Feb 2012 | |
| 37.153.137.0/24 | 256 | RIPE NCC | 13th Mar 2012 | |
| 37.246.0.0/16 | 65.5k | RIPE NCC | 17th Apr 2012 | |
| 45.182.188.0/24 | 256 | RIPE NCC | 19th Sept 2019 | |
| 45.81.140.0/22 | 1k | RIPE NCC | 20th May 2019 | |
| 45.88.32.0/22 | 1k | RIPE NCC | 18th Jun 2019 | |
| 46.28.239.0/24 | 256 | RIPE NCC | 27th Jul 2010 | |
| 5.181.17.0/24 | 256 | RIPE NCC | 1st Apr 2019 | |
| 5.182.246.0/24 | 256 | RIPE NCC | 9th Apr 2019 | |
| 5.183.160.0/24 | 256 | RIPE NCC | 14th Jan 2025 | |
| 5.44.144.0/20 | 4.1k | RIPE NCC | 23rd May 2012 | |
| 62.108.80.0/21 | 2k | RIPE NCC | 15th Jun 2000 | |
| 62.204.47.0/24 | 256 | RIPE NCC | 11th Oct 2021 | |
| 77.241.72.0/22 | 1k | RIPE NCC | 4th Oct 2018 | |
| 77.95.217.0/24 | 256 | RIPE NCC | 18th Feb 2025 | |
| 78.108.116.0/24 | 256 | RIPE NCC | 23rd Jun 2026 | |
| 78.108.119.0/24 | 256 | RIPE NCC | 23rd Jun 2026 | |
| 78.135.117.0/24 | 256 | RIPE NCC | 28th Jun 2007 | |
| 78.135.118.0/23 | 512 | RIPE NCC | 28th Jun 2007 | |
| 78.135.120.0/21 | 2k | RIPE NCC | 28th Jun 2007 | |
| 78.135.78.0/24 | 256 | RIPE NCC | 28th Jun 2007 | |
| 79.170.168.0/21 | 2k | RIPE NCC | 1st Oct 2007 | |
| 80.71.145.0/24 | 256 | RIPE NCC | 23rd Sept 2021 | |
| 81.162.128.0/18 | 16.4k | RIPE NCC | 6th Dec 2011 | |
| 84.252.80.0/22 | 1k | RIPE NCC | 16th Nov 2018 | |
| 84.54.15.0/24 | 256 | RIPE NCC | 15th Nov 2018 | |
| 85.136.208.0/23 | 512 | RIPE NCC | 3rd Nov 2004 |