Iran Proxies

Iran has a deep published pool relative to most catalogue entries. Use the Iran depth for measured country-level sampling, not for routing around a quota, challenge, or block. Long-lived Iran flows should prefer a documented sticky session; independent observations can request rotation. In both Iran modes, connection reuse and live supply can produce the same exit more than once. Iran pool depth also cannot authorize collection: the destination's terms, robots guidance, contracts, authentication boundaries, rate controls, and applicable law remain the controlling constraints. Treat a block, CAPTCHA, quota, or explicit denial as a stop or review signal across the whole Iran pool rather than rotating around it. Record Iran failures as data; do not hide them with unlimited retries.

The immediately larger undefined catalogue entry than Iran is Malaysia at 359,137 addresses, and the next smaller is Russian Federation at 298,973. In the Iran comparison set, the regional leader is Indonesia with 2,664,464. These Iran capacity comparisons are useful only when the workload could legitimately run from more than one country. Choose Iran when the research question specifically needs a Iran network-origin observation. Choose a different country from Iran only when it is a valid control or a separate market in the study. Combining Iran observations with other countries in one unlabeled dataset makes regional differences impossible to interpret. Preserve the requested Iran route, observed exit country, network type, timestamp, source, response class, and validation outcome on every retained record.

Before using a Iran result, capture five things: the canonical source URL and permission basis; the Databay network and countryCode-ir setting; the observed exit IP, ASN, and geolocation source; the browser, account, language, currency, address, cookie, and device state; and the UTC timestamp plus response evidence. Repeat the Iran check from a controlled reference and label missing, blocked, challenged, stale, or personalized responses instead of treating them as ordinary content. For a consequential Iran price, availability, advertising, search, compliance, or product decision, obtain a second authorized source or local review. This Iran workflow makes the 324,038-address catalogue figure useful as coverage context without pretending it proves a resident's experience.