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 Iran
709 blocks match, ordered by prefix.
| Prefix | Addresses | Registry | Country | Allocated |
|---|---|---|---|---|
| 185.41.220.0/22 | 1k | RIPE NCC |  IR | 4th Feb 2019 |
| 185.46.0.0/22 | 1k | RIPE NCC | IR | 27th Jan 2014 |
| 185.46.108.0/22 | 1k | RIPE NCC | IR | 30th Jan 2014 |
| 185.49.104.0/23 | 512 | RIPE NCC | IR | 4th Mar 2014 |
| 185.5.213.0/24 | 256 | RIPE NCC | IR | 16th Jun 2025 |
| 185.50.36.0/24 | 256 | RIPE NCC | IR | 12th Mar 2014 |
| 185.57.200.0/22 | 1k | RIPE NCC | IR | 16th May 2014 |
| 185.77.21.0/24 | 256 | RIPE NCC | IR | 30th Apr 2025 |
| 185.79.16.0/24 | 256 | RIPE NCC | IR | 27th Jun 2025 |
| 185.82.180.0/22 | 1k | RIPE NCC | IR | 30th Dec 2014 |
| 185.83.184.0/22 | 1k | RIPE NCC | IR | 12th Jan 2015 |
| 185.83.76.0/22 | 1k | RIPE NCC | IR | 7th Jan 2015 |
| 185.84.157.0/24 | 256 | RIPE NCC | IR | 17th Jan 2025 |
| 188.0.242.0/23 | 512 | RIPE NCC | IR | 27th May 2011 |
| 188.208.208.0/21 | 2k | RIPE NCC | IR | 8th May 2009 |
| 188.211.128.0/19 | 8.2k | RIPE NCC | IR | 8th May 2009 |
| 188.213.96.0/19 | 8.2k | RIPE NCC | IR | 8th May 2009 |
| 188.214.120.0/23 | 512 | RIPE NCC | IR | 8th May 2009 |
| 192.166.36.0/24 | 256 | RIPE NCC | IR | 6th Feb 2026 |
| 193.109.56.0/24 | 256 | RIPE NCC | IR | 5th Jun 2023 |
| 193.142.232.0/23 | 512 | RIPE NCC | IR | 11th Oct 2019 |
| 193.142.254.0/23 | 512 | RIPE NCC | IR | 11th Oct 2019 |
| 193.163.73.0/24 | 256 | RIPE NCC | IR | 16th Jun 2026 |
| 193.177.245.0/24 | 256 | RIPE NCC | IR | 5th Aug 2025 |
| 193.201.23.0/24 | 256 | RIPE NCC | IR | 19th Jan 2026 |
| 193.24.103.0/24 | 256 | RIPE NCC | IR | 2nd Jul 2024 |
| 193.24.118.0/24 | 256 | RIPE NCC | IR | 2nd Jul 2024 |
| 193.28.181.0/24 | 256 | RIPE NCC | IR | 4th Oct 2011 |
| 193.29.50.0/24 | 256 | RIPE NCC | IR | 8th May 2025 |
| 193.93.182.0/24 | 256 | RIPE NCC | IR | 5th Jul 2023 |
| 194.0.234.0/24 | 256 | RIPE NCC | IR | 14th May 2024 |
| 194.113.116.0/24 | 256 | RIPE NCC | IR | 9th Jul 2026 |
| 194.117.82.0/24 | 256 | RIPE NCC | IR | 14th Oct 2025 |
| 194.147.170.0/24 | 256 | RIPE NCC | IR | 22nd Nov 2019 |
| 194.150.165.0/24 | 256 | RIPE NCC | IR | 28th Apr 2025 |
| 194.246.34.0/24 | 256 | RIPE NCC | IR | 8th May 2024 |
| 194.26.64.0/24 | 256 | RIPE NCC | IR | 18th Aug 2025 |
| 194.33.125.0/24 | 256 | RIPE NCC | IR | 4th Jun 2012 |
| 194.33.126.0/23 | 512 | RIPE NCC | IR | 4th Jun 2012 |
| 194.36.172.0/22 | 1k | RIPE NCC | IR | 16th May 2018 |
| 194.5.40.0/22 | 1k | RIPE NCC | IR | 20th Jul 2018 |
| 195.190.139.0/24 | 256 | RIPE NCC | IR | 25th Nov 2019 |
| 195.190.144.0/24 | 256 | RIPE NCC | IR | 25th Nov 2019 |
| 195.2.234.0/24 | 256 | RIPE NCC | IR | 26th Jul 2022 |
| 195.200.76.0/24 | 256 | RIPE NCC | IR | 17th Jul 2024 |
| 195.96.153.0/24 | 256 | RIPE NCC | IR | 2nd Nov 2021 |
| 2001:14e8::/32 | 4.3B × /64 | RIPE NCC | IR | 15th Jul 2003 |
| 2001:1500::/32 | 4.3B × /64 | RIPE NCC | IR | 16th Jul 2003 |
| 2001:3040::/29 | 34.4B × /64 | RIPE NCC | IR | 4th Sept 2024 |
| 2001:30c0::/29 | 34.4B × /64 | RIPE NCC | IR | 5th Sept 2024 |