Brazil proxies: carriers, states and location tests

Decide what a Brazil label has to prove

Brazil proxies give your request an exit that the supplier labels as Brazilian, and whether your destination's location service agrees is the first thing to test. The label does not say which of the 27 federative units the exit sits in, which operator carried it, whether access is mobile or fixed residential, or whether its IPv4 address is shared.

Write the pass condition first: when our location database returns BR, with Accept-Language unchanged, our storefront switches to Brazilian Portuguese and prices in the Brazilian real (BRL). No exit reproduces one customer's view, since the CEP, account and payment details come from the customer, and a region a site pre-fills from the network address is an input of its own.

Give each requirement its own row: a São Paulo state check needs a state result, a fault from a TIM subscriber needs operator evidence, and a pt-BR rendering test may need only the country. The Brazil proxies page turns these rows into storefront workflows, and the country guides index covers other markets.

Learn the operator names Anatel uses

Anatel, the telecom regulator, publishes a Relatório de Competição; its Q2 2026 edition counted 276.4 million mobile accesses, up 3.7 percent year over year, with Vivo at 37.9 percent and TIM at 22.4 percent. The news summary gives only those two mobile shares, so it supports no ranking that includes Claro.

Its mobile coverage page links to the maps of five network operators, Claro, TIM, Vivo, Algar and Sercomtel, and publishes coverage by municipality and technology from base-station licensing data: where a handset can expect radio service, not which public address a proxy request carries or where a geolocation database places it.

Record the brand a supplier's menu shows apart from the company that owns it; the ownership notes below are background from each company's own pages. Then ask which layer a carrier filter fixes: the SIM, the antennas that served it, or the holder a registry or routing lookup names for the exit address.

• Vivo: the brand of Telefônica Brasil, which Telefónica calls the leading integrated operator in the Brazilian market.
• Claro: NET, Claro and Embratel are three brands of one company, and NET is now Claro, so any of those names can mean the same organization.
• TIM: TIM S.A. is ultimately controlled by Telecom Italia S.p.A. through TIM Brasil; a Telecom Italia name belongs to the parent.
• Algar Telecom: a Brazilian provider with national operations and a primary focus on B2B clients, but its residential fiber and mobile offer covers cities in four states, so a consumer sample is regional.

Account for MVNOs, roaming, home lines and fallback

Anatel regulates mobile virtual network operators under Resolução nº 777/2025: an Autorizada de Rede Virtual provides mobile service over a host operator's network, the Prestadora Origem, so a retail brand describes a subscription, not necessarily the network that carried the connection. National roaming is mandatory in every municipality with fewer than 30,000 inhabitants, where a subscriber may use another operator's network.

Brazil residential proxies need their own requirement: a fixed home line, such as Algar's fiber broadband in cities of four states, is a different access type from a phone and not automatically exclusive, since the NIC.br sources below describe shared IPv4 at operators generally. Record mobile or fixed residential as its own field, and ask how the supplier sources and authorizes those connections for proxy use.

Ask, too, what happens when a selection cannot be met: if no Vivo or Distrito Federal exit is free, does the request fail, use another operator or state, or fall back to any Brazilian exit, and does the response say so? The trial records such a selection as unavailable and never counts a substitute exit as a pass.

Map the states and regions, then read the state field

IBGE's 2024 framework has 26 states, each in one Grande Região, plus the Distrito Federal, together the Unidades da Federação. The Distrito Federal cannot be divided into municipalities and its seat, Brasília, is the federal capital, so a Brasília requirement passes on a returned Distrito Federal, not a city string. For per-state rows, borrow the layout of the USA proxies guide.

IBGE groups the units into five Grandes Regiões, so list the member states in any regional requirement. The Northeast runs to nine states from Maranhão to Bahia, while the Center-West includes Goiás and the Distrito Federal, so a Northeast selection is met by a Bahia result, not a Goiás one.

Read the returned state as a database estimate. MaxMind says accuracy varies with country, distance and IP type, and that one mobile address may serve phones across a large distance, so it may return the country and state but no city. A missing city is not by itself a defect, but it leaves a city requirement unmet; a state or Distrito Federal requirement passes only when that returned field matches.

Treat the CEP and the CPF as customer inputs

The CEP (Código de Endereçamento Postal) is an eight-digit number that Correios assigns to localities, streets, public bodies, companies and buildings, a precision MaxMind says its GeoIP data never reaches. Americanas uses it to show regional offers and calculate shipping, and Shopee Brasil fills state, city and street from it; at both, the customer supplies it, so hold one CEP fixed whenever the exit is the variable.

The CPF, administered by the Receita Federal, is unique and permanent for each citizen, and Shopee Brasil requires one in regular status to complete a purchase. A location test therefore stops before any third-party checkout, with no CPF entered, real or invented. Test checkout fields only on your own or an authorized staging storefront, with documented fixtures and any Receita Federal status lookup stubbed.

Pix is the Banco Central do Brasil's instant payment scheme, established by Resolution BCB 1 of 12 August 2020. Whether a checkout lists it is the merchant's configuration, not a location result, so check it only on your own staging storefront, as an option you set up.

Log who holds a Brazilian address, and over which family

Operator names describe companies; address records describe holders. For every exit, log two identity fields apart, next to the address family: the registry holder, from the RIR record, and the origin ASN and holder, from a named routing lookup with the lookup time. Brazilian IPv4, IPv6 and ASN resources are NIC.br's responsibility, through Registro.br, while LACNIC is the regional registry.

Neither field places the exit. In 2018 LACNIC noted that the geographic information it lists includes the holder's country of legal domicile, often not where the address is used, so a registry country cannot settle a state requirement. Likewise, a Telefônica Brasil holder is consistent with a Vivo selection but does not show whose antennas served the handset.

In a 2014 tutorial, NIC.br's IPv6.br program said CGNAT at operators made sharing IPv4 addresses among customers unavoidable for some time during the transition to IPv6, and that identifying one user behind CGNAT also takes the source port. In 2023 NIC.br's projects and development manager said the large operators and large internet providers run 100% IPv6 networks, while shared IPv4 causes problems for applications. Record each address an exit presents, IPv6 or shared IPv4.

Set the legal time zone and pt-BR in the browser

Brazilian legal time uses four zones under Lei nº 12.876 of 30 October 2013, and an exit does not choose one. Look up the legal time for the place your test represents on the Observatório Nacional's Hora Legal Brasileira page, set that zone in your browser tooling and record it with each capture, along with the cookie state and location permission.

Google's Play Console lists Brazilian and European Portuguese as separate locales, pt-BR and pt-PT, and a storefront that reads the browser's language may serve either one to a Brazilian exit. Until the trial's language row has separated those two causes, a European Portuguese page seen through a Brazilian exit is a language result, not a network one.

Observe Magazine Luiza and Google from public pages

Magazine Luiza's store locator has a list for each federative unit, 27 from Lojas Acre to Lojas Tocantins, so an explicit state choice can be observed on a public, signed-out page. Its “Localizando lojas próximo a você” message suggests it may also locate the visitor, possibly through the browser, so test the chosen state first and treat any default state as incidental unless the supplier documents state selection.

Hold every third-party site to the same bounds: limit proxied checks to your own service, authorized destinations, or a storefront's public, signed-out pages as its terms permit, by hand and at low volume; create no accounts, enter no personal or invented identity data such as a CPF, card or phone number, and place no orders. Brazil's data-protection law, the LGPD (Lei nº 13.709/2018), is supervised by the ANPD; ask your legal advisor how it applies to your records.

Google said in April 2025 that since 2017 it had given the same local results whether people used google.com or their country's domain, and that it would gradually redirect country-code domains such as google.com.br to google.com. Do not pin the domain; record the query, the interface language, the location Google reports and the time.

Run the Brazil trial in blocks of six requests

Connect with the curl setup guide, then read each exit from an endpoint you operate that sees the connection directly, not through a CDN, over your destination's address families or through separate IPv4-only and IPv6-only endpoints. A block is six requests: two documented selections, three apiece in sequence, one fixed pause, one per-request deadline and no automatic retries. Log those settings and any session parameter with the block, so a difference between its two selections cannot come from timing.

Score every request on four lines: completed; BR returned; the required state or Distrito Federal, N/A where a row makes no state claim; and pt-BR text with BRL prices, N/A except on storefront rows, which add one page capture per request. Beside the score, keep both identity fields, the observed address and family, the zoned timestamp and the geolocation answer. A selection the supplier cannot make is scored unavailable, never replaced by a generic Brazil exit.

Run only the rows you need; the language and CEP rows take two blocks each, so all five come to 42 requests at most. Verify the language row's Portuguese exit as the Portugal proxies guide describes before relying on it. None of the rows has been run by ipvolt, which has no Brazilian supply under contract and has confirmed no country, state or operator inventory; your results describe the supplier you test.

• Language row, two blocks, on your own storefront: hold one Brazilian exit and send three requests with pt-BR and three with pt-PT; then hold pt-BR and send three through the Brazilian exit and three through a Portuguese one. It passes when, with pt-BR fixed, the Brazilian exit returns BR and gets pt-BR text and BRL prices; it makes no state claim.
• Distrito Federal row: pass a Brasília selection only when the named geolocation service returns the Distrito Federal; Goiás or another Center-West unit fails it.
• CEP row, two blocks, on your own storefront: hold one exit and send three requests with each of two approved CEP fixtures, then hold one CEP and send three through each of two exit selections. Only an offer that moves in the second block is a network finding.
• Operator row: for a Vivo, Claro or TIM selection, record the label, any MVNO or roaming explanation and both identity fields, counting Claro, NET and Embratel as one company.
• Session row: per selection, send two requests at the fixed pause and a third after the documented address lifetime; pass if the address holds or changes as documented. Source ports help match a disputed connection across logs but prove nothing about exclusive use.