Tunisia Proxies
3,820+ residential and mobile proxy IPs in Tunisia. 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.
Africa coverage field
2 network types · 8 ASNs
- Tunisia3,820 IPs
- Morocco646,631 IPs
- South Africa592,536 IPs
- Egypt524,973 IPs
- Algeria309,306 IPs
- Nigeria38,692 IPs
Tunisia network coverage
The proxy networks reported for Tunisia, 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 Tunisia. Global pool sizes are catalog-wide; browse the live community proxy list for Tunisia to sample real endpoints.
Target Tunisia down to the city and ASN
Set countryCode-tn in your proxy username, then layer city, ZIP, GPS, or AS number on top at no extra cost.
Country routing
One flag,
countryCode-tn, requests an exit geolocated to Tunisia, 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 Tunisia
- AS37492 ORANGE-
- AS327934 Tunisie-Telecom
- AS328880 STE-INTERNET-SMART-SOLUTIONS-AS
- AS2609 TN-BB-AS Tunisia BackBone AS
- AS37671 GLOBALNET-AS
- AS37693 TUNISIANA
- AS37705 TOPNET
- AS328853 OXAHOST-AS
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 Tunisia
curl -x http://USER-zone-residential-countryCode-tn:PASS@gw.databay.co:8888 \
https://databay.com/cdn-cgi/trace
# Sticky session (30 minutes) in Tunisia
curl -x http://USER-zone-residential-countryCode-tn-sessionId-abc123:PASS@gw.databay.co:8888 \
https://databay.com/cdn-cgi/trace
# Datacenter proxy in Tunisia
curl -x http://USER-zone-datacenter-countryCode-tn:PASS@gw.databay.co:8888 \
https://databay.com/cdn-cgi/tracePricing for Tunisia: residential from $0.90/GB (PAYG $2.75/GB), datacenter from $0.50/GB (volume), mobile from $2.50/GB. All tiers include Tunisia country targeting at no extra cost. See documentation.
Network-wide operating targets for Tunisia 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 Tunisia proxies are used for
Authorized workflows where a documented Tunisia network-origin sample can answer a defined question.
Web scraping
Collect permitted public fields from approved Tunisia sources with a documented request budget and validation plan.
ExploreAd verification
Compare authorized campaign rendering from a Tunisia network origin while holding account, device, and locale state constant.
ExploreMarket research
Add a Tunisia network-origin sample while recording account, language, delivery, tax, and personalization limits.
ExploreSEO monitoring
Record permitted Tunisia search observations with the query, language, device, timestamp, and observed exit documented.
ExploreE-commerce tracking
Validate permitted Tunisia 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 Tunisia (34M+ IPs from $0.90/GB). Testing first? You can browse the live community proxy list for Tunisia (refreshed every 5 minutes).
Reading the published Tunisia address count
Databay's June 9, 2026 paid-network catalogue assigns 3,820 addresses to Tunisia. That places Tunisia number 181 of 195 locations worldwide and number 45 of 50 in Africa. The Tunisia allocation represents <0.05% of the global catalogue and 0.15% of the Africa total. For Tunisia, those figures describe catalogue breadth, not a count of exits guaranteed online at one moment. The Tunisia count also does not establish address ownership, consent, residential status, latency, reputation, city accuracy, or acceptance by a destination. Use the live Tunisia coverage panel on this page to see which Databay network types currently report service, then confirm the observed exit before relying on a result. Tunisia pricing is determined by network and plan rather than by inflating the country count into a performance promise.
What countryCode-tn changes
The gateway flag countryCode-tn requests an exit geolocated to Tunisia, subject to current supply and the selected network. For Tunisia, it changes one input: the apparent network origin seen by the destination. A Tunisia 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 Tunisia comparison, write down the hypothesis first and hold those other inputs constant. Check the Tunisia 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 Tunisia city, ZIP, coordinate, or ASN matters, validate that narrower result separately; country success does not prove subnational accuracy.
Plan Tunisia sessions from the actual pool scale
Tunisia is one of the catalogue's smallest allocations. Use the Tunisia pool for focused country-origin checks, not broad rotation. Expect repeat Tunisia exits, validate availability before a long run, keep concurrency low, and retain a controlled comparison from another route. A zero-result Tunisia filter is evidence to stop or redesign the test, not a reason to increase pressure. Tunisia 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 Tunisia pool rather than rotating around it. Record Tunisia failures as data; do not hide them with unlimited retries.
Tunisia in its Africa comparison set
The immediately larger undefined catalogue entry than Tunisia is Senegal at 3,849 addresses, and the next smaller is Somalia at 3,567. In the Tunisia comparison set, the regional leader is Morocco with 646,631. These Tunisia capacity comparisons are useful only when the workload could legitimately run from more than one country. Choose Tunisia when the research question specifically needs a Tunisia network-origin observation. Choose a different country from Tunisia only when it is a valid control or a separate market in the study. Combining Tunisia observations with other countries in one unlabeled dataset makes regional differences impossible to interpret. Preserve the requested Tunisia route, observed exit country, network type, timestamp, source, response class, and validation outcome on every retained record.
A reproducible Tunisia validation checklist
Before using a Tunisia result, capture five things: the canonical source URL and permission basis; the Databay network and countryCode-tn 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 Tunisia check from a controlled reference and label missing, blocked, challenged, stale, or personalized responses instead of treating them as ordinary content. For a consequential Tunisia price, availability, advertising, search, compliance, or product decision, obtain a second authorized source or local review. This Tunisia workflow makes the 3,820-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 Tunisia?
What types of proxies are available in Tunisia?
Which networks and ASNs are covered in Tunisia?
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 Tunisia proxies
Review live Tunisia coverage and access the published pool under the selected plan and service limits.
Pricing, order minimums, and traffic validity vary by product.