Question 1

Why use Brazilian carrier IPs specifically?

Accepted Answer

Claro, Vivo, and TIM ranges map to millions of legitimate mobile subscribers. LATAM‑facing platforms treat that traffic unlike datacenter ASNs or mis‑geo residential pools — storefronts localize and trust checks align with on‑the‑ground behavior.

Question 2

Which carriers are selectable?

Accepted Answer

Claro (AS28573), Vivo Telefónica Brasil (AS26615), and TIM Brasil (AS26599). Pools stay isolated per carrier via the dashboard or API session parameters.

Question 3

Instagram automation on these gateways?

Accepted Answer

Carrier mobile ASNs reinforce the handset trust pillars Instagram evaluates. Keeping sticky egress for for long periods (hours or days) lets you traverse onboarding and heavy workflows without mid‑flight IP churn.

Question 4

TikTok LATAM stacks?

Accepted Answer

Brazilian egress tags accounts and feeds like regional mobile traffic — important for LATAM creators, storefront funnels, and multi‑session rigs that rely on coherent geo attribution.

Question 5

How do I choose a carrier per session?

Accepted Answer

Use the session builder in the dashboard or pass carrier selectors via the API whenever you want to diversify ASN fingerprints across rivals’ networks.

Question 6

Scraping localized e‑commerce?

Accepted Answer

Major Brazilian marketplaces gate pricing/catalog copy by ASN. Exit through Brazilian carrier ranges to fetch the storefront locals see instead of scraping through foreign datacenter blocks.