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 Iran
710 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 45.80.84.0/24 | 256 | RIPE NCC | 28th Jan 2026 | |
| 45.84.248.0/22 | 1k | RIPE NCC | 3rd Jun 2019 | |
| 46.248.32.0/19 | 8.2k | RIPE NCC | 17th Dec 2010 | |
| 46.251.224.0/24 | 256 | RIPE NCC | 9th Feb 2011 | |
| 46.251.226.0/24 | 256 | RIPE NCC | 9th Feb 2011 | |
| 46.251.237.0/24 | 256 | RIPE NCC | 9th Feb 2011 | |
| 46.29.33.0/24 | 256 | RIPE NCC | 15th Jan 2025 | |
| 5.220.0.0/15 | 131k | RIPE NCC | 4th Sept 2012 | |
| 5.253.225.0/24 | 256 | RIPE NCC | 24th Jan 2022 | |
| 5.253.96.0/22 | 1k | RIPE NCC | 8th Feb 2019 | |
| 5.73.0.0/16 | 65.5k | RIPE NCC | 11th Jun 2012 | |
| 62.220.109.0/24 | 256 | RIPE NCC | 25th Oct 2001 | |
| 62.220.110.0/23 | 512 | RIPE NCC | 25th Oct 2001 | |
| 85.159.113.0/24 | 256 | RIPE NCC | 30th Dec 2019 | |
| 85.198.48.0/20 | 4.1k | RIPE NCC | 31st Jan 2005 | |
| 85.209.41.0/24 | 256 | RIPE NCC | 2nd Feb 2026 | |
| 85.8.231.0/24 | 256 | RIPE NCC | 29th Jun 2026 | |
| 85.8.236.0/24 | 256 | RIPE NCC | 2nd Jul 2026 | |
| 85.8.243.0/24 | 256 | RIPE NCC | 24th Jul 2026 | |
| 86.107.184.0/24 | 256 | RIPE NCC | 18th Apr 2005 | |
| 88.135.34.0/23 | 512 | RIPE NCC | 16th Nov 2009 | |
| 89.33.87.0/24 | 256 | RIPE NCC | 29th Nov 2005 | |
| 89.35.120.0/22 | 1k | RIPE NCC | 29th Nov 2005 | |
| 89.35.172.0/24 | 256 | RIPE NCC | 29th Nov 2005 | |
| 89.35.180.0/22 | 1k | RIPE NCC | 29th Nov 2005 | |
| 89.35.64.0/21 | 2k | RIPE NCC | 29th Nov 2005 | |
| 89.36.252.0/23 | 512 | RIPE NCC | 29th Nov 2005 | |
| 89.40.110.0/23 | 512 | RIPE NCC | 29th Nov 2005 | |
| 89.40.38.0/23 | 512 | RIPE NCC | 29th Nov 2005 | |
| 89.40.65.0/24 | 256 | RIPE NCC | 29th Nov 2005 | |
| 89.41.58.0/23 | 512 | RIPE NCC | 29th Nov 2005 | |
| 89.42.56.0/23 | 512 | RIPE NCC | 29th Nov 2005 | |
| 89.45.126.0/23 | 512 | RIPE NCC | 29th Nov 2005 | |
| 91.194.6.0/24 | 256 | RIPE NCC | 28th Jan 2026 | |
| 91.195.37.0/24 | 256 | RIPE NCC | 30th Jan 2024 | |
| 91.209.96.0/24 | 256 | RIPE NCC | 1st Jun 2021 | |
| 91.217.166.0/24 | 256 | RIPE NCC | 24th Sept 2025 | |
| 91.220.0.0/24 | 256 | RIPE NCC | 11th Aug 2025 | |
| 91.226.224.0/23 | 512 | RIPE NCC | 28th Apr 2011 | |
| 91.228.192.0/24 | 256 | RIPE NCC | 22nd May 2025 | |
| 91.228.22.0/23 | 512 | RIPE NCC | 3rd Oct 2019 | |
| 91.231.144.0/24 | 256 | RIPE NCC | 26th Jan 2026 | |
| 91.239.108.0/22 | 1k | RIPE NCC | 18th May 2012 | |
| 91.239.210.0/24 | 256 | RIPE NCC | 31st Aug 2022 | |
| 91.240.116.0/24 | 256 | RIPE NCC | 2nd Nov 2022 | |
| 91.243.119.0/24 | 256 | RIPE NCC | 5th Oct 2020 | |
| 91.92.172.0/22 | 1k | RIPE NCC | 15th Aug 2006 | |
| 91.92.220.0/22 | 1k | RIPE NCC | 15th Aug 2006 | |
| 92.114.64.0/20 | 4.1k | RIPE NCC | 15th Oct 2007 | |
| 93.117.176.0/20 | 4.1k | RIPE NCC | 21st Dec 2007 |