Tajikistan Proxies
3,049+ residential proxy IPs in Tajikistan. 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
- 3,049
- ASNs
- 9
- Region rank
- 48/50
Tajikistan network coverage
The proxy networks reported for Tajikistan, 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)
A network shows as Live only when it is currently serving traffic in Tajikistan. Global pool sizes are catalog-wide; browse the live community proxy list for Tajikistan to sample real endpoints.
Target Tajikistan down to the city and ASN
Set countryCode-tj in your proxy username, then layer city, ZIP, GPS, or AS number on top at no extra cost.
Country routing
One flag,
countryCode-tj, requests an exit geolocated to Tajikistan, 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 9 autonomous systems covered in Tajikistan
- AS8847 TTL-AS CJSC Telecomm Technology
- AS43197 TT-MOBILE-AS PJSC TT mobile
- AS44027 SPITAMEN_ALEXANDER_INTERNET-AS
- AS51346 TOJIKTELECOM-AS
- AS24722 BABILON-AS
- AS34557 TACOM-AS 47a Lahuti st
- AS42713 INTERCOM
- AS47139 INDIGO-TAJIKISTAN-AS
- AS208592 AS-AVESTONET KAZTRANSCOM
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 Tajikistan
curl -x http://USER-zone-residential-countryCode-tj:PASS@gw.databay.co:8888 \
https://databay.com/cdn-cgi/trace
# Sticky session (30 minutes) in Tajikistan
curl -x http://USER-zone-residential-countryCode-tj-sessionId-abc123:PASS@gw.databay.co:8888 \
https://databay.com/cdn-cgi/trace
# Datacenter proxy in Tajikistan
curl -x http://USER-zone-datacenter-countryCode-tj:PASS@gw.databay.co:8888 \
https://databay.com/cdn-cgi/tracePricing for Tajikistan: residential from $0.90/GB (PAYG $2.75/GB), datacenter from $0.50/GB (volume), mobile from $2.50/GB. All tiers include Tajikistan country targeting at no extra cost. See documentation.
Network-wide operating targets for Tajikistan 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 Tajikistan proxies are used for
Authorized workflows where a documented Tajikistan network-origin sample can answer a defined question.
Web scraping
Collect permitted public fields from approved Tajikistan sources with a documented request budget and validation plan.
ExploreAd verification
Compare authorized campaign rendering from a Tajikistan network origin while holding account, device, and locale state constant.
ExploreMarket research
Add a Tajikistan network-origin sample while recording account, language, delivery, tax, and personalization limits.
ExploreSEO monitoring
Record permitted Tajikistan search observations with the query, language, device, timestamp, and observed exit documented.
ExploreE-commerce tracking
Validate permitted Tajikistan 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 Tajikistan (34M+ IPs from $0.90/GB). Testing first? You can browse the live community proxy list for Tajikistan (refreshed every 5 minutes).
Tajikistan coverage: scale before slogans
Databay's June 9, 2026 paid-network catalogue assigns 3,049 addresses to Tajikistan. That places Tajikistan number 187 of 195 locations worldwide and number 48 of 50 in Asia. The Tajikistan allocation represents <0.05% of the global catalogue and <0.05% of the Asia total. For Tajikistan, those figures describe catalogue breadth, not a count of exits guaranteed online at one moment. The Tajikistan count also does not establish address ownership, consent, residential status, latency, reputation, city accuracy, or acceptance by a destination. Use the live Tajikistan coverage panel on this page to see which Databay network types currently report service, then confirm the observed exit before relying on a result. Tajikistan pricing is determined by network and plan rather than by inflating the country count into a performance promise.
What countryCode-tj changes
The gateway flag countryCode-tj requests an exit geolocated to Tajikistan, subject to current supply and the selected network. For Tajikistan, it changes one input: the apparent network origin seen by the destination. A Tajikistan exit 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 Tajikistan comparison, write down the hypothesis first and hold those other inputs constant. Check the Tajikistan exit with a diagnostic endpoint you trust, save the timestamp and effective settings, and compare the observation with a direct or controlled reference. If a Tajikistan city, ZIP, coordinate, or ASN matters, validate that narrower result separately; country success does not prove subnational accuracy.
Plan Tajikistan sessions from the actual pool scale
Tajikistan is one of the catalogue's smallest allocations. Use the Tajikistan pool for focused country-origin checks, not broad rotation. Expect repeat Tajikistan exits, validate availability before a long run, keep concurrency low, and retain a controlled comparison from another route. A zero-result Tajikistan filter is evidence to stop or redesign the test, not a reason to increase pressure. Tajikistan 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 Tajikistan pool rather than rotating around it. Record Tajikistan failures as data; do not hide them with unlimited retries.
Tajikistan in its Asia comparison set
The immediately larger undefined catalogue entry than Tajikistan is Mongolia at 4,131 addresses, and the next smaller is Armenia at 2,828. In the Tajikistan comparison set, the regional leader is Indonesia with 2,664,464. These Tajikistan capacity comparisons are useful only when the workload could legitimately run from more than one country. Choose Tajikistan when the research question specifically needs a Tajikistan network-origin observation. Choose a different country from Tajikistan only when it is a valid control or a separate market in the study. Combining Tajikistan observations with other countries in one unlabeled dataset makes regional differences impossible to interpret. Preserve the requested Tajikistan route, observed exit country, network type, timestamp, source, response class, and validation outcome on every retained record.
A reproducible Tajikistan validation checklist
Before using a Tajikistan result, capture five things: the canonical source URL and permission basis; the Databay network and countryCode-tj 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 Tajikistan check from a controlled reference and label missing, blocked, challenged, stale, or personalized responses instead of treating them as ordinary content. For a consequential Tajikistan price, availability, advertising, search, compliance, or product decision, obtain a second authorized source or local review. This Tajikistan workflow makes the 3,049-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 Tajikistan?
What types of proxies are available in Tajikistan?
Which networks and ASNs are covered in Tajikistan?
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 Tajikistan proxies
Review live Tajikistan coverage and access the published pool under the selected plan and service limits.
Pricing, order minimums, and traffic validity vary by product.