South Africa Proxies
592,536+ residential and mobile proxy IPs in South Africa. 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 · 82 ASNs
- South Africa592,536 IPs
- Morocco646,631 IPs
- Egypt524,973 IPs
- Algeria309,306 IPs
- Nigeria38,692 IPs
- Kenya21,970 IPs
South Africa network coverage
The proxy networks reported for South Africa, 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 South Africa. Global pool sizes are catalog-wide; browse the live community proxy list for South Africa to sample real endpoints.
Target South Africa down to the city and ASN
Set countryCode-za in your proxy username, then layer city, ZIP, GPS, or AS number on top at no extra cost.
Country routing
One flag,
countryCode-za, requests an exit geolocated to South Africa, 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 82 autonomous systems covered in South Africa
- AS3741 NTT-DATA-Inc
- AS11845 Vox-Telecom
- AS20011 NTT-DATA-Inc
- AS37457 Telkom-Internet
- AS214209 INTERNET-MAGNATE
- AS327750 JENNY-INTERNET
- AS327782 METROFIBRE-NETWORX
- AS327808 Tesuco-Telecommunications
- AS327907 Paw-Paw-Wireless
- AS327991 MEGASURF-WIRELESS-INTERNET
- AS328068 Active-Fibre
- AS328176 ITTX-Telecoms
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 South Africa
curl -x http://USER-zone-residential-countryCode-za:PASS@gw.databay.co:8888 \
https://databay.com/cdn-cgi/trace
# Sticky session (30 minutes) in South Africa
curl -x http://USER-zone-residential-countryCode-za-sessionId-abc123:PASS@gw.databay.co:8888 \
https://databay.com/cdn-cgi/trace
# Datacenter proxy in South Africa
curl -x http://USER-zone-datacenter-countryCode-za:PASS@gw.databay.co:8888 \
https://databay.com/cdn-cgi/tracePricing for South Africa: residential from $0.90/GB (PAYG $2.75/GB), datacenter from $0.50/GB (volume), mobile from $2.50/GB. All tiers include South Africa country targeting at no extra cost. See documentation.
Network-wide operating targets for South Africa 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 South Africa proxies are used for
Authorized workflows where a documented South Africa network-origin sample can answer a defined question.
Web scraping
Collect permitted public fields from approved South Africa sources with a documented request budget and validation plan.
ExploreAd verification
Compare authorized campaign rendering from a South Africa network origin while holding account, device, and locale state constant.
ExploreMarket research
Add a South Africa network-origin sample while recording account, language, delivery, tax, and personalization limits.
ExploreSEO monitoring
Record permitted South Africa search observations with the query, language, device, timestamp, and observed exit documented.
ExploreE-commerce tracking
Validate permitted South Africa 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 South Africa (34M+ IPs from $0.90/GB). Testing first? You can browse the live community proxy list for South Africa (refreshed every 5 minutes).
South Africa coverage: scale before slogans
Databay's June 9, 2026 paid-network catalogue assigns 592,536 addresses to South Africa. That places South Africa number 19 of 195 locations worldwide and number 2 of 50 in Africa. The South Africa allocation represents 1.7% of the global catalogue and 23.1% of the Africa total. For South Africa, those figures describe catalogue breadth, not a count of exits guaranteed online at one moment. The South Africa count also does not establish address ownership, consent, residential status, latency, reputation, city accuracy, or acceptance by a destination. Use the live South Africa coverage panel on this page to see which Databay network types currently report service, then confirm the observed exit before relying on a result. South Africa pricing is determined by network and plan rather than by inflating the country count into a performance promise.
What countryCode-za changes
The gateway flag countryCode-za requests an exit geolocated to South Africa, subject to current supply and the selected network. For South Africa, it changes one input: the apparent network origin seen by the destination. An exit geolocated to South Africa 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 South Africa, write down the hypothesis first and hold those other inputs constant. Check the South Africa 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 South Africa matters, validate that narrower result separately; country success does not prove subnational accuracy.
Plan South Africa sessions from the actual pool scale
South Africa has a deep published pool relative to most catalogue entries. Use the South Africa depth for measured country-level sampling, not for routing around a quota, challenge, or block. Long-lived South Africa flows should prefer a documented sticky session; independent observations can request rotation. In both South Africa modes, connection reuse and live supply can produce the same exit more than once. South Africa 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 South Africa pool rather than rotating around it. Record South Africa failures as data; do not hide them with unlimited retries.
South Africa in its Africa comparison set
The immediately larger Africa catalogue entry than South Africa is Morocco at 646,631 addresses, and the next smaller is Egypt at 524,973. In the South Africa comparison set, the regional leader is Morocco with 646,631. These South Africa capacity comparisons are useful only when the workload could legitimately run from more than one country. Choose South Africa when the research question specifically needs a network-origin observation from South Africa. Choose a different country from South Africa only when it is a valid control or a separate market in the study. Combining South Africa observations with other countries in one unlabeled dataset makes regional differences impossible to interpret. Preserve the requested South Africa route, observed exit country, network type, timestamp, source, response class, and validation outcome on every retained record.
A reproducible South Africa validation checklist
Before using a South Africa result, capture five things: the canonical source URL and permission basis; the Databay network and countryCode-za 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 South Africa check from a controlled reference and label missing, blocked, challenged, stale, or personalized responses instead of treating them as ordinary content. For a consequential South Africa price, availability, advertising, search, compliance, or product decision, obtain a second authorized source or local review. This South Africa workflow makes the 592,536-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 South Africa?
What types of proxies are available in South Africa?
Which networks and ASNs are covered in South Africa?
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 South Africa proxies
Review live South Africa coverage and access the published pool under the selected plan and service limits.
Pricing, order minimums, and traffic validity vary by product.