Brazil Proxies
2,858,324+ residential, datacenter, and mobile proxy IPs in Brazil. City-level geo-targeting, rotating and sticky sessions, HTTP, HTTPS & SOCKS5. Volume plans from $0.50/GB.
Pay as you go from 1 GB. Dataset updated June 2026; live availability varies by network type.
- Argentina 1,225,819
- Colombia 372,203
- 325,035 Chile
- 293,255 Peru
3 network types · 3,348 ASNs
Brazil network coverage
The proxy networks reported for Brazil, 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)
High-speed shared IPs built for bulk, latency-sensitive collection at the lowest unit cost.
- Global pool
- 80K+ IPs
- Network origin
- Hosting network
- From
- $0.50/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 Brazil. Global pool sizes are catalog-wide; browse the live community proxy list for Brazil to sample real endpoints.
Target Brazil down to the city and ASN
Set countryCode-br in your proxy username, then layer city, ZIP, GPS, or AS number on top at no extra cost.
Country routing
One flag,
countryCode-br, requests an exit geolocated to Brazil, 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 3,348 autonomous systems covered in Brazil
- AS4230 CLARO S.A.
- AS7063 LESTE FLU SERVICOS DE TELECOM LTDA
- AS10429 TELEFONICA BRASIL S.A
- AS10704 ML Telecom
- AS11432 Telium Telecomunicacoes Ltda
- AS11706 TELEFONICA BRASIL S.A
- AS11844 Empresa Catarinense de Tecnologia em Telecom. Ltda
- AS13357 Ampernet Telecomunicacoes Ltda
- AS14282 PERSIS TELECOM
- AS14840 BR.Digital Telecom
- AS14868 Ligga Telecomunicacoes S.A.
- AS16735 ALGAR TELECOM SA
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 Brazil
curl -x http://USER-zone-residential-countryCode-br:PASS@gw.databay.co:8888 \
https://databay.com/cdn-cgi/trace
# Sticky session (30 minutes) in Brazil
curl -x http://USER-zone-residential-countryCode-br-sessionId-abc123:PASS@gw.databay.co:8888 \
https://databay.com/cdn-cgi/trace
# Datacenter proxy in Brazil
curl -x http://USER-zone-datacenter-countryCode-br:PASS@gw.databay.co:8888 \
https://databay.com/cdn-cgi/tracePricing for Brazil: 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 Brazil at no extra cost. See documentation.
Network-wide operating targets for Brazil 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 Brazil proxies are used for
Authorized workflows where a documented Brazil network-origin sample can answer a defined question.
Web scraping
Collect permitted public fields from approved sources in Brazil with a documented request budget and validation plan.
ExploreAd verification
Compare authorized campaign rendering from a Brazil network origin while holding account, device, and locale state constant.
ExploreMarket research
Add a Brazil network-origin sample while recording account, language, delivery, tax, and personalization limits.
ExploreSEO monitoring
Record permitted Brazil search observations with the query, language, device, timestamp, and observed exit documented.
ExploreE-commerce tracking
Validate permitted Brazil 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 Brazil (34M+ IPs from $0.90/GB). Testing first? You can browse the live community proxy list for Brazil (refreshed every 5 minutes).
How Brazil compares in the proxy catalogue
Databay's June 9, 2026 paid-network catalogue assigns 2,858,324 addresses to Brazil. That places Brazil number 2 of 195 locations worldwide and number 1 of 14 in South America. The Brazil allocation represents 8.2% of the global catalogue and 54.0% of the South America total. For Brazil, those figures describe catalogue breadth, not a count of exits guaranteed online at one moment. The Brazil count also does not establish address ownership, consent, residential status, latency, reputation, city accuracy, or acceptance by a destination. Use the live Brazil coverage panel on this page to see which Databay network types currently report service, then confirm the observed exit before relying on a result. Brazil pricing is determined by network and plan rather than by inflating the country count into a performance promise.
Isolate the Brazil network-origin variable
The gateway flag countryCode-br requests an exit geolocated to Brazil, subject to current supply and the selected network. For Brazil, it changes one input: the apparent network origin seen by the destination. An exit geolocated to Brazil 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 Brazil, write down the hypothesis first and hold those other inputs constant. Check the Brazil 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 Brazil matters, validate that narrower result separately; country success does not prove subnational accuracy.
Plan Brazil sessions from the actual pool scale
Brazil sits in the catalogue's largest scale band. The Brazil allocation creates room to sample more than one exit, but it is not a request-rate allowance and does not mean every address is simultaneously online. Split authorized Brazil work by source and research question, keep one domain-level request budget across every session, and monitor valid-response rate rather than raw request volume. Brazil 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 Brazil pool rather than rotating around it. Record Brazil failures as data; do not hide them with unlimited retries.
Brazil in its South America comparison set
Brazil is the largest published South America entry. The next entry after Brazil is Argentina with 1,225,819 addresses; that comparison describes catalogue scale only, not quality, latency, or live availability. Choose Brazil when the research question specifically needs a network-origin observation from Brazil. Choose a different country from Brazil only when it is a valid control or a separate market in the study. Combining Brazil observations with other countries in one unlabeled dataset makes regional differences impossible to interpret. Preserve the requested Brazil route, observed exit country, network type, timestamp, source, response class, and validation outcome on every retained record.
A reproducible Brazil validation checklist
Before using a Brazil result, capture five things: the canonical source URL and permission basis; the Databay network and countryCode-br 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 Brazil check from a controlled reference and label missing, blocked, challenged, stale, or personalized responses instead of treating them as ordinary content. For a consequential Brazil price, availability, advertising, search, compliance, or product decision, obtain a second authorized source or local review. This Brazil workflow makes the 2,858,324-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 Brazil?
What types of proxies are available in Brazil?
Which networks and ASNs are covered in Brazil?
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 Brazil proxies
Review live Brazil coverage and access the published pool under the selected plan and service limits.
Pricing, order minimums, and traffic validity vary by product.