Afghanistan Proxies
19,289+ residential and mobile proxy IPs in Afghanistan. City-level geo-targeting, rotating and sticky sessions, HTTP, HTTPS & SOCKS5. Plans from $0.90/GB.
Pay as you go from 1 GB. Dataset updated June 2026; live availability varies by network type.
Asia route lanes
- Published IPs
- 19,289
- ASNs
- 8
- Region rank
- 26/50
Afghanistan network coverage
The proxy networks reported for Afghanistan, with global catalogue size, network origin, and volume-plan entry price.
ISP-origin IPs for authorized regional sampling and workflows that require a consumer-network route.
- Global pool
- 34M+ IPs
- Network origin
- ISP-classified
- From
- $0.90/GB (1 TB plan)
Mobile Proxies
Live4G and 5G carrier-network IPs for authorized app testing and mobile-network checks.
- Global pool
- 800K+ IPs
- Network origin
- Mobile carrier
- From
- $2.50/GB (512 GB plan)
A network shows as Live only when it is currently serving traffic in Afghanistan. Global pool sizes are catalog-wide; browse the live community proxy list for Afghanistan to sample real endpoints.
Target Afghanistan down to the city and ASN
Set countryCode-af in your proxy username, then layer city, ZIP, GPS, or AS number on top at no extra cost.
Country routing
One flag,
countryCode-af, requests an exit geolocated to Afghanistan, subject to live availability.City, ZIP & GPS requests
Request a narrower residential location, then verify the observed exit because live supply and geolocation can vary.
ASN targeting request
Request an autonomous system by AS number, subject to network support and current eligible exits.
Rotating or sticky
Request gateway-selected exits or a sticky target up to 120 minutes; connections and availability affect reuse.
- Country, city, ZIP, GPS, and ASN targeting included on every plan
- Gateway-selected exits or sticky session targets, subject to availability
- HTTP, HTTPS, and SOCKS5 on one gateway, no allowlisting
- Every flag set in the proxy username, no code changes
Sample of 8 autonomous systems covered in Afghanistan
- AS131284 ETISALATAFG-AS-AP Etisalat Afghan
- AS133894 EASYCONNECTISP-AS-AP Easy Connect- ISP
- AS135298 TRANSWORLD-AS-AP Ankabut Internet Service Provider
- AS135376 RAHANET-ISP-AS-AP Rahanet Internet Service Provider
- AS137039 ZT-AS-AP Zohak Technology Z-Tech
- AS149173 HBISC-AS-AP Hindukush Bridge ICT Services Company
- AS153975 KABULSUPPLYCHAIN-AS-AP Kabul Supply Chain
- AS55330 GCN-DCN-AS AFGHANTELECOM GOVERNMENT COMMUNICATION NETWORK
Select any country, city, or AS number directly in the proxy username. ASN availability varies by network type and real-time device counts.
# Rotating residential proxy in Afghanistan
curl -x http://USER-zone-residential-countryCode-af:PASS@gw.databay.co:8888 \
https://databay.com/cdn-cgi/trace
# Sticky session (30 minutes) in Afghanistan
curl -x http://USER-zone-residential-countryCode-af-sessionId-abc123:PASS@gw.databay.co:8888 \
https://databay.com/cdn-cgi/trace
# Datacenter proxy in Afghanistan
curl -x http://USER-zone-datacenter-countryCode-af:PASS@gw.databay.co:8888 \
https://databay.com/cdn-cgi/tracePricing for Afghanistan: residential from $0.90/GB (PAYG $2.75/GB), datacenter from $0.50/GB (volume), mobile from $2.50/GB. All tiers include country targeting for Afghanistan at no extra cost. See documentation.
Network-wide operating targets for Afghanistan routes
These catalogue-wide figures describe the service target, not a country-specific guarantee. Measure the exact route and workload before relying on it.
- Uptime target
- 99.9%+
- Network-wide availability
- Residential latency
- ~1.1s
- Median response time
- Datacenter latency
- ~780ms
- Median response time
- Max sticky target
- 120 min
- Subject to live exit availability
Latency and uptime are network-wide medians and targets. See how Databay benchmarks its network.
What Afghanistan proxies are used for
Authorized workflows where a documented Afghanistan network-origin sample can answer a defined question.
Web scraping
Collect permitted public fields from approved sources in Afghanistan with a documented request budget and validation plan.
ExploreAd verification
Compare authorized campaign rendering from a Afghanistan network origin while holding account, device, and locale state constant.
ExploreMarket research
Add a Afghanistan network-origin sample while recording account, language, delivery, tax, and personalization limits.
ExploreSEO monitoring
Record permitted Afghanistan search observations with the query, language, device, timestamp, and observed exit documented.
ExploreE-commerce tracking
Validate permitted Afghanistan price and availability observations against feeds, APIs, or another authorized source.
ExploreSocial media
Operate authorized client accounts using platform-approved tools and stable sessions where the platform permits proxy access.
Explore
Other proxy locations
Compare published catalogue counts and then check live network and targeting availability for the exact location you need.
Largest pools worldwide
Need rotating IPs with city and ASN targeting? Get residential proxies in Afghanistan (34M+ IPs from $0.90/GB). Testing first? You can browse the live community proxy list for Afghanistan (refreshed every 5 minutes).
Afghanistan proxy coverage, in numbers
Databay's June 9, 2026 paid-network catalogue assigns 19,289 addresses to Afghanistan. That places Afghanistan number 72 of 195 locations worldwide and number 26 of 50 in Asia. The Afghanistan allocation represents 0.06% of the global catalogue and 0.15% of the Asia total. For Afghanistan, those figures describe catalogue breadth, not a count of exits guaranteed online at one moment. The Afghanistan count also does not establish address ownership, consent, residential status, latency, reputation, city accuracy, or acceptance by a destination. Use the live Afghanistan coverage panel on this page to see which Databay network types currently report service, then confirm the observed exit before relying on a result. Afghanistan pricing is determined by network and plan rather than by inflating the country count into a performance promise.
Build a controlled Afghanistan location test
The gateway flag countryCode-af requests an exit geolocated to Afghanistan, subject to current supply and the selected network. For Afghanistan, it changes one input: the apparent network origin seen by the destination. An exit geolocated to Afghanistan does not set a browser language, currency, time zone, delivery address, tax jurisdiction, account country, cookie history, device profile, or legal eligibility. For a useful comparison involving Afghanistan, write down the hypothesis first and hold those other inputs constant. Check the Afghanistan exit with a diagnostic endpoint you trust, save the timestamp and effective settings, and compare the observation with a direct or controlled reference. If city, ZIP, coordinate, or ASN precision in Afghanistan matters, validate that narrower result separately; country success does not prove subnational accuracy.
Plan Afghanistan sessions from the actual pool scale
Afghanistan has a limited but material published allocation. Design Afghanistan work for repeat exits: pace requests, use sticky sessions for multi-step authorized flows, and avoid multiplying concurrency merely because the gateway can rotate. If a narrow Afghanistan filter returns no suitable exit, broaden the test or stop rather than claiming unavailable coverage. Afghanistan 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 Afghanistan pool rather than rotating around it. Record Afghanistan failures as data; do not hide them with unlimited retries.
Afghanistan in its Asia comparison set
The immediately larger Asia catalogue entry than Afghanistan is Syrian Arab Republic at 19,851 addresses, and the next smaller is Oman at 17,569. In the Afghanistan comparison set, the regional leader is Indonesia with 2,664,464. These Afghanistan capacity comparisons are useful only when the workload could legitimately run from more than one country. Choose Afghanistan when the research question specifically needs a network-origin observation from Afghanistan. Choose a different country from Afghanistan only when it is a valid control or a separate market in the study. Combining Afghanistan observations with other countries in one unlabeled dataset makes regional differences impossible to interpret. Preserve the requested Afghanistan route, observed exit country, network type, timestamp, source, response class, and validation outcome on every retained record.
A reproducible Afghanistan validation checklist
Before using a Afghanistan result, capture five things: the canonical source URL and permission basis; the Databay network and countryCode-af 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 Afghanistan check from a controlled reference and label missing, blocked, challenged, stale, or personalized responses instead of treating them as ordinary content. For a consequential Afghanistan price, availability, advertising, search, compliance, or product decision, obtain a second authorized source or local review. This Afghanistan workflow makes the 19,289-address catalogue figure useful as coverage context without pretending it proves a resident's experience.
Frequently asked questions
How many proxy IPs does Databay have in Afghanistan?
What types of proxies are available in Afghanistan?
Which networks and ASNs are covered in Afghanistan?
How do I authenticate with Databay proxies?
Which protocols are supported?
Is there an API?
How do I get started?
Do you offer reseller or volume plans?
Start using Afghanistan proxies
Review live Afghanistan coverage and access the published pool under the selected plan and service limits.
Pricing, order minimums, and traffic validity vary by product.