When the target market is Brazil, choose rotating residential (per GB) or static residential (per IP/month) by task. pt-BR/BRL/CEP and delivery checks plus Brazilian ecommerce and localization pointers link to on-site scenes; inventory follows the console; prices follow the console. pt-BR is not es-ES.
What this Brazil page solves
Once the target market is Brazil, the next step is usually not another product brochure—it is two decisions:
- Pick product class by task: public-side sampling / monitoring / localization, or authorized store long-lived identity
- Confirm in the console that Brazil exits are orderable (cities and stock always follow the backend)
This is the Brazil country landing under Locations: map “Brazil × rotating/static” to on-site products and scenes—not a city inventory table. Still need the class frame? Rotating vs static residential. First-time buyer overview: How to choose a residential proxy. Sister markets: United States · Japan · Singapore · United Kingdom · Germany · Australia · Canada · France · Netherlands · South Korea · Italy · Spain. Hub: Locations. Localization / public-path self-check deep-read: Localization testing. Store map: Ecommerce.
When you also run North America exits in parallel within a LatAm / South America frame, open the United States sister page. When you need an Iberian Spanish-language market for comparison within the Romance-language family, open Spain—but remember pt-BR ≠ es-ES: Brazilian Portuguese is not Spanish.
Lawful, authorized commercial and technical use only. Brazil / LatAm / South America scenes mean authorized business and self-checks on publicly reachable paths—not unauthorized access or bypassing platform rules. Mentions of Mercado Livre or Brazilian retail are limited to authorized store operations and public-path localization / assortment self-checks. Not supported for use in mainland China.
How to split the Brazil market: rotating by GB vs static by IP
Rotating residential (per GB)
Fit when you need rotatable, Brazil-selectable, usage-flexible exits: public data sampling, price monitoring, ad creative / landing self-checks, pt-BR copy / BRL pricing / CEP delivery options short-flow previews, Brazilian Portuguese public-path spot checks, and Brazilian ecommerce-context public-side assortment and competitor-page checks within a LatAm / South America frame, etc. Entry: Rotating.
Billing per GB: about $0.40/GB; 100 TB full bundle about $0.20/GB (full bundle only; not split; 1 TB = 1,000 GB). Math: Billing GB vs IP. Console wins on price.
One short flow (finish checkout or a settings page once—e.g. verify a BRL price and a CEP delivery option) can use a sticky session—same exit briefly; sticky ≠ monthly static. Params: console. Detail: Sticky vs static. Multi-page / multi-sample → rotate; do not leave sticky always on.
Static residential (per IP / month)
Fit when you need a relatively fixed exit for the term: authorized Brazil-market store backends (often discussed alongside North America ecommerce in a LatAm / South America context, but this page covers Brazil exits only), persistent environments that need consistent network identity. Entry: Static.
Billing per IP / month: shared about $1.50, dedicated about $5 (USD). Boundary: Shared vs dedicated static. Store map: Ecommerce. Console wins on price.
Localization experience self-checks and public-side Brazil / LatAm market research usually do not need monthly static. If the same project has both store backends and public experience / assortment sampling, split configs (static + rotating each on their own path). When both Brazil and the United States (or Brazil and Spain) are in scope, split exits by market as well—do not mix them, and do not treat a Brazil (pt-BR) exit as a Spain (es-ES) exit.
One table: Brazil-side task mapping
Choose by task
| Task | Prefer | Why | ZTProxy |
|---|---|---|---|
| Public multi-URL / multi-page sampling, price monitoring, BR public research | Rotating + Brazil geo | Traffic + rotatable exits, not monthly identity | Rotating; Price monitoring |
| pt-BR / BRL / CEP delivery and Brazilian Portuguese UI self-check | Rotating; short sticky for one flow | Public-path regional experience, not store long identity | Localization; Sticky vs static |
| Ad creative / landing self-check | Rotating; short sticky or rotate | Object under check is creative + landing | Ad verification |
| Authorized Brazil store backend; long fixed identity | Static (shared or dedicated) | Relatively fixed exit for the term | Static; Ecommerce; Shared vs dedicated |
| Unsure rotating vs static class / first purchase | Selection guides | Align task and bill unit first | Rotating vs static; How to choose |
Console wins; no platform-review, conversion, inventory, or coverage promises.
Rotating vs static (Brazil context)
| Dimension | Rotating residential | Static residential |
|---|---|---|
| What you buy | Rotatable / Brazil-selectable residential exits + traffic | Relatively fixed Brazil exit for the term |
| Billing | Per GB (~$0.40/GB; bundles on pricing) | Per IP / month (shared ~$1.50; dedicated ~$5) |
| Typical use | Monitoring, ad self-check, pt-BR/BRL/CEP localization spot checks, public-side assortment | Authorized stores, persistent environments |
| Entry | Rotating | Static |
| Common miss | Rotating for long login; sticky as monthly fixed | Static monthly for multi-page public / multi-CEP delivery sampling |
How to read Brazil / LatAm·South America scenes (no invented inventory)
Business conversations often mention Brazilian ecommerce and localization (Brazil alongside the United States in North/South America operations), Brazil public-side research, or pt-BR Brazilian Portuguese display differences. This page’s target market remains Brazil exits:
- Brazilian ecommerce / LatAm·South America parallel pointer: authorized Brazil store long identity → static; public assortment, competitor pages, price sampling → rotating. When North America is also in scope, compare United States. Map: Ecommerce. Mercado Livre and similar Brazilian retail contexts are authorized-store and public-path localization / assortment self-checks only—not account farming or bypass.
- pt-BR / BRL / CEP localization: prefer rotating + Brazil geo; sticky for one short flow (including BRL pricing, CEP delivery options, and Brazilian Portuguese UI), rotate for multi-page sampling. Deep-read: Localization.
- CEP & delivery self-check: authorized sampling on publicly reachable checkout / shipping paths only; no promises of carrier outcomes or coverage, and no invented city or CEP lists.
- pt-BR ≠ es-ES: Brazilian Portuguese and Spanish (Spain) are both Romance languages, but they are not the same language and not the same target market. For Spanish (Spain) exits, switch to Spain—do not use this Brazil page as a Spanish page.
- Brazilian ecommerce & localization pointer: a qualitative reminder that public paths may show pt-BR copy, BRL pricing, or CEP delivery differences; this site does not provide translation services and does not promise that a given language pack “will always appear.”
- Competitor SERP themes (qualitative only): match rotating vs static to the task; verify Brazil exit first, then test locale / currency / delivery; split hybrid setups when one project needs both store login and public sampling. No invented volumes or rankings.
Locations is the browse entry; whether Brazil is orderable, and city/resource detail, always follow console/backend. This page invents no city counts, coverage %, or availability SLA. Smoke-test with small traffic or a short term before scale.
If the business target is another market instead of Brazil, switch to: United States · Japan · Singapore · United Kingdom · Germany · Australia · Canada · France · Netherlands · South Korea · Italy · Spain.
How to read price
- Rotating: about $0.40/GB; 100 TB full bundle about $0.20/GB (not split)
- Static: shared about $1.50 /IP/month; dedicated about $5 /IP/month
- Currency USD; self-serve list may follow reseller settings—orders and bills follow console + Pricing
- Effective-cost mindset: Billing GB vs IP
- Payment context: USDT/USDC available; Visa/Mastercard applying / pending
Pre-order checklist
- Public-side sampling / experience / Brazil market research, or authorized store long identity? → match the table
- Target market confirmed Brazil? Console geo / order page shows matching resource? Need a separate United States / Spain config? (pt-BR ≠ es-ES)
- Short sticky or rotate? (sticky params: console)
- Bill by GB or IP×month? Check Pricing
- Protocol / client fields: Docs EN quickstart; checklist HTTP / SOCKS5
- Lawful, authorized use? Avoid mainland China use restriction? First purchase: How to choose
FAQ
For Brazil business, rotating or static?
By task. Public monitoring, ad self-check, pt-BR/BRL/CEP localization and delivery sampling, public research → prefer Rotating. Authorized store long identity → prefer Static. Frame: Rotating vs static.
Who wins on Brazil inventory and city coverage?
Console / backend. This page has no city list or stock numbers; the Locations hub is browse-only.
How is Brazil rotating residential billed? What payments are supported?
Per GB; on-site about $0.40/GB (bundles on pricing). USD; console + Pricing win. Payment context: USDT/USDC available; Visa/Mastercard applying / pending.
Can sticky session act as a Brazil static IP?
No. Sticky keeps the same exit briefly; static is monthly fixed identity. Sticky vs static.
How to set up pt-BR, BRL, or CEP localization?
Prefer rotating + Brazil geo; sticky for one short flow (including BRL / CEP delivery / Brazilian Portuguese UI), rotate for multi-page sampling. Deep-read: Localization. Remember pt-BR ≠ es-ES; for Spanish markets switch to Spain.
How does this differ from US / JP / SG / UK / DE / AU / CA / FR / NL / KR / IT / ES pages?
Same skeleton; different target market. This page leans pt-BR / BRL / CEP, Brazilian ecommerce & localization, LatAm / South America context, and sister United States (N/S America) plus Spain (language-family contrast; pt-BR ≠ es-ES). Compare: Japan · Singapore · United Kingdom · Germany · Australia · Canada · France · Netherlands · South Korea · Italy.
What is the use boundary? Account farming or multi-account evasion?
Lawful, authorized commercial and technical use only, plus self-checks on publicly reachable paths. No account farming, multi-account evasion, or bypassing platform rules; no promises of platform review or conversion outcomes.
Mainland China? Who wins on price?
All proxy services on this site are not supported for use in mainland China. Published prices are USD; orders and bills follow console + Pricing.
Next steps
- Use the task table: rotating or static
- Open Rotating or Static; confirm Brazil exits in console
- Check Pricing; connect via Docs EN quickstart
- Scene deep-reads: Localization · Ecommerce · Price monitoring · Ad verification
- Other markets: Locations · United States · Japan · Singapore · United Kingdom · Germany · Australia · Canada · France · Netherlands · South Korea · Italy · Spain
- First-purchase overview: How to choose
Need help: [email protected] or on-site support (no invented response SLA).