Brazilian residential proxies are real IP addresses from Brazilian households, assigned by consumer ISPs such as Vivo, Claro, TIM and Algar Telecom. They let you browse, scrape and verify Brazilian storefronts, pricing and content as a genuine in-country user — across São Paulo, Rio de Janeiro, Curitiba and Belo Horizonte — instead of from a datacenter IP that Mercado Livre, Magazine Luiza and local geo-gates flag and block on sight.
Brazil residential proxies are real IP addresses from Brazilian households, assigned by consumer ISPs. They let you browse, scrape and verify Brazilian websites, pricing and content as a genuine in-country user — instead of from a datacenter IP that local sites flag and block.
Real residential IPs, precise targeting, and quality you don't have to take on faith.
Every month we run the same benchmark — a random sample of IPs scored against Scamalytics, latency tested from a neutral VPS, and geo-accuracy checked across independent databases. The figures below reflect production, not a best-case lab run.
«Avg. online» is the average number of distinct devices connected and available at the same moment — not a cumulative total. Grouped into High / Medium / Low.
| Region | Latency | Avg. online | Pool |
|---|---|---|---|
| São Paulo | 406 ms | ~27,326 | High |
| Minas Gerais | 411 ms | ~11,006 | High |
| Rio de Janeiro | 394 ms | ~8,555 | High |
| Rio Grande do Sul | 424 ms | ~7,502 | High |
| Santa Catarina | 409 ms | ~6,466 | High |
| Paraná | 413 ms | ~6,285 | High |
| Bahia | 427 ms | ~5,478 | High |
| Pernambuco | 392 ms | ~3,373 | High |
| Goiás | 429 ms | ~3,257 | High |
| Ceará | 364 ms | ~3,241 | Medium |
| Espírito Santo | 414 ms | ~2,172 | Medium |
| Federal District | 427 ms | ~2,106 | Medium |
| Pará | 427 ms | ~1,908 | Medium |
| Paraíba | 379 ms | ~1,711 | Medium |
| Maranhão | 411 ms | ~1,546 | Medium |
| Mato Grosso | 444 ms | ~1,448 | Medium |
| Rio Grande do Norte | 369 ms | ~1,217 | Medium |
| Amazonas | 486 ms | ~1,102 | Medium |
| Mato Grosso do Sul | 437 ms | ~1,020 | Low |
| Alagoas | 381 ms | ~1,004 | Low |
| Sergipe | 409 ms | ~888 | Low |
| Piauí | 378 ms | ~773 | Low |
| Rondônia | 464 ms | ~543 | Low |
| Tocantins | 437 ms | ~362 | Low |
| Amapá | 496 ms | ~313 | Low |
| Roraima | 543 ms | ~132 | Low |
| Acre | 500 ms | ~115 | Low |
| City | Latency | Avg. online | Pool |
|---|---|---|---|
| São Paulo | 395 ms | ~21,503 | High |
| Rio de Janeiro | 392 ms | ~12,819 | High |
| Brasília | 426 ms | ~6,151 | High |
| Curitiba | 406 ms | ~6,151 | High |
| Belo Horizonte | 415 ms | ~5,014 | High |
| Fortaleza | 368 ms | ~4,497 | High |
| Porto Alegre | 421 ms | ~4,187 | High |
| Goiânia | 428 ms | ~3,929 | High |
| Salvador | 416 ms | ~3,412 | High |
| Manaus | 488 ms | ~3,101 | Medium |
| Campinas | 401 ms | ~3,050 | Medium |
| Recife | 398 ms | ~2,688 | Medium |
| Ribeirão Preto | 394 ms | ~2,429 | Medium |
| Santo André | 417 ms | ~2,326 | Medium |
| Blumenau | 377 ms | ~2,068 | Medium |
| Belém | 450 ms | ~1,964 | Medium |
| São Luís | 432 ms | ~1,861 | Low |
| Natal | 394 ms | ~1,861 | Low |
| Uberlândia | 424 ms | ~1,861 | Low |
| Guarulhos | 406 ms | ~1,809 | Low |
| João Pessoa | 370 ms | ~1,757 | Low |
| São José dos Campos | 407 ms | ~1,654 | Low |
| Osasco | 428 ms | ~1,602 | Low |
| Sao Paulo | 431 ms | ~1,602 | Low |
| São José | 396 ms | ~1,551 | Low |
| Provider | Latency | Avg. online | Pool |
|---|---|---|---|
| Claromobile | 431 ms | ~29,684 | High |
| Vivofixed | 384 ms | ~22,726 | High |
| V.talfixed | 408 ms | ~11,117 | High |
| Vivo (Telefônica Brasil)fixed | 408 ms | ~9,113 | High |
| Brisanetfixed | 360 ms | ~5,521 | High |
| Unifiquefixed | 378 ms | ~4,197 | Medium |
| Desktopfixed | 387 ms | ~3,554 | Medium |
| Giga+ Fibrafixed | 367 ms | ~3,290 | Medium |
| Algar Telecomfixed | 405 ms | ~3,214 | Medium |
| Verofixed | 373 ms | ~2,874 | Low |
| MHNet Telecomfixed | 425 ms | ~1,702 | Low |
| Cabo Telecomfixed | 426 ms | ~1,513 | Low |
| Liggafixed | 412 ms | ~1,172 | Low |
| TIMmobile | 429 ms | ~1,172 | Low |
Geo-accuracy — every IP sold as Brazil resolves to Brazil across three independent geo-databases (db-ip, MaxMind, ipinfo); high geo-accuracy is the signal local geo-gates rely on.
Organised by what you're doing, not by platform. Local services are listed where they matter.
Beyond local sites, the same Brazilian pool works for the major global platforms — Google, Meta, Amazon, YouTube, TikTok and Netflix — seen from the Brazilian locale: local pricing, ads, catalogues, SERP and content.
Generate Brazil-scoped endpoints in the dashboard, copy tested snippets, or automate proxy lists through the public API. City, ISP, sticky sessions and saved lists stay in one clean workflow.
Higher volume means lower price per gigabyte. No subscriptions or hidden fees.
Available payment methods
Still weighing whether the Brazilian pool fits your use case? Our team answers real questions on Telegram, around the clock — before and after you buy.
Chat on TelegramCountry guides with local cities, ISPs and practical routing notes for each market.