Turkey Proxies
248,694+ residential and mobile proxy IPs in Turkey. 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
- 248,694
- ASNs
- 114
- Region rank
- 14/50
Turkey network coverage
The proxy networks reported for Turkey, 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 Turkey. Global pool sizes are catalog-wide; browse the live community proxy list for Turkey to sample real endpoints.
Target Turkey down to the city and ASN
Set countryCode-tr in your proxy username, then layer city, ZIP, GPS, or AS number on top at no extra cost.
Country routing
One flag,
countryCode-tr, requests an exit geolocated to Turkey, 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 114 autonomous systems covered in Turkey
- AS15897 VODAFONETURKEY
- AS15924 BORUSANTELEKOM-AS
- AS47516 DEHOST DEHOST INTERNET VE BILISIM TEKNOLOJILERI SANAYI TICARET LIMITED SIRKETI
- AS56582 NETFACTOR-ASN Netfactor - ISP Broadband services TR
- AS58127 CDNTELEKOM
- AS202303 ISP-TRENDNET-AS202303
- AS204209 BIZIMINTERNET
- AS205768 FIBERIX
- AS205852 ISTTELKOM
- AS206119 VEGANET-TELEKOM
- AS209007 WIFITELEKOM Wifi Telekomwifi.net.tr
- AS209380 ARATTELEKOM
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 Turkey
curl -x http://USER-zone-residential-countryCode-tr:PASS@gw.databay.co:8888 \
https://databay.com/cdn-cgi/trace
# Sticky session (30 minutes) in Turkey
curl -x http://USER-zone-residential-countryCode-tr-sessionId-abc123:PASS@gw.databay.co:8888 \
https://databay.com/cdn-cgi/trace
# Datacenter proxy in Turkey
curl -x http://USER-zone-datacenter-countryCode-tr:PASS@gw.databay.co:8888 \
https://databay.com/cdn-cgi/tracePricing for Turkey: 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 Turkey at no extra cost. See documentation.
Network-wide operating targets for Turkey 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 Turkey proxies are used for
Authorized workflows where a documented Turkey network-origin sample can answer a defined question.
Web scraping
Collect permitted public fields from approved sources in Turkey with a documented request budget and validation plan.
ExploreAd verification
Compare authorized campaign rendering from a Turkey network origin while holding account, device, and locale state constant.
ExploreMarket research
Add a Turkey network-origin sample while recording account, language, delivery, tax, and personalization limits.
ExploreSEO monitoring
Record permitted Turkey search observations with the query, language, device, timestamp, and observed exit documented.
ExploreE-commerce tracking
Validate permitted Turkey 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 Turkey (34M+ IPs from $0.90/GB). Testing first? You can browse the live community proxy list for Turkey (refreshed every 5 minutes).
Turkey proxy coverage, in numbers
Databay's June 9, 2026 paid-network catalogue assigns 248,694 addresses to Turkey. That places Turkey number 36 of 195 locations worldwide and number 14 of 50 in Asia. The Turkey allocation represents 0.71% of the global catalogue and 1.9% of the Asia total. For Turkey, those figures describe catalogue breadth, not a count of exits guaranteed online at one moment. The Turkey count also does not establish address ownership, consent, residential status, latency, reputation, city accuracy, or acceptance by a destination. Use the live Turkey coverage panel on this page to see which Databay network types currently report service, then confirm the observed exit before relying on a result. Turkey pricing is determined by network and plan rather than by inflating the country count into a performance promise.
Build a controlled Turkey location test
The gateway flag countryCode-tr requests an exit geolocated to Turkey, subject to current supply and the selected network. For Turkey, it changes one input: the apparent network origin seen by the destination. An exit geolocated to Turkey 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 Turkey, write down the hypothesis first and hold those other inputs constant. Check the Turkey 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 Turkey matters, validate that narrower result separately; country success does not prove subnational accuracy.
Plan Turkey sessions from the actual pool scale
Turkey falls in the catalogue's substantial middle-to-large band. It can support repeated authorized Turkey observations when requests are paced and results are validated, but narrower city, ZIP, coordinate, or ASN filters reduce the eligible pool. Run a small Turkey pilot with the exact filter combination before setting concurrency, retry, or schedule assumptions. Turkey 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 Turkey pool rather than rotating around it. Record Turkey failures as data; do not hide them with unlimited retries.
Turkey in its Asia comparison set
The immediately larger Asia catalogue entry than Turkey is Russian Federation at 298,973 addresses, and the next smaller is Israel at 216,716. In the Turkey comparison set, the regional leader is Indonesia with 2,664,464. These Turkey capacity comparisons are useful only when the workload could legitimately run from more than one country. Choose Turkey when the research question specifically needs a network-origin observation from Turkey. Choose a different country from Turkey only when it is a valid control or a separate market in the study. Combining Turkey observations with other countries in one unlabeled dataset makes regional differences impossible to interpret. Preserve the requested Turkey route, observed exit country, network type, timestamp, source, response class, and validation outcome on every retained record.
A reproducible Turkey validation checklist
Before using a Turkey result, capture five things: the canonical source URL and permission basis; the Databay network and countryCode-tr 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 Turkey check from a controlled reference and label missing, blocked, challenged, stale, or personalized responses instead of treating them as ordinary content. For a consequential Turkey price, availability, advertising, search, compliance, or product decision, obtain a second authorized source or local review. This Turkey workflow makes the 248,694-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 Turkey?
What types of proxies are available in Turkey?
Which networks and ASNs are covered in Turkey?
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 Turkey proxies
Review live Turkey coverage and access the published pool under the selected plan and service limits.
Pricing, order minimums, and traffic validity vary by product.