How do I check if my landing page is blocked in Brazil?
Published 2026-05-27 · 8 min read
TL;DR
Test the URL from real residential and mobile networks inside Brazil on all four major carriers:
Vivo (AS26599 fixed / AS27699 mobile), Claro (AS28573), TIM (AS26615 / AS41059 mobile),
Oi (AS7738). If three or four of them return 403, 451, a DNS failure, or a
block page while a datacenter probe gets 200, you have an Anatel-level country block or a
multi-carrier filter. If only one or two fail, it's an ASN-level block on those specific operators.
Signature of a Brazilian block
Conversions from Brazil collapse overnight while clicks keep coming from your traffic source.
Brazilian affiliate partners and end-users report the page won't load — but Anatel announces no public order.
Your own test from outside Brazil (or from AWS/GCP São Paulo region) returns a clean
200.Traditional uptime monitors (Pingdom, UptimeRobot, StatusCake) stay green throughout.
Vivo Mobile users complain first — mobile carriers in Brazil typically enforce regulator orders within hours, fixed-line within a day.
How to verify it (step by step)
- 1
Don't test from your own connection. If you're on a corporate ISP, VPN, or cloud probe, you bypass the filter that's blocking real Brazilian users.
- 2
Check all four major Brazilian carriers. Vivo (AS26599), Claro (AS28573), TIM (AS26615), Oi (AS7738) cover the overwhelming majority of consumer traffic in Brazil.
- 3
Test mobile and fixed-line separately. Vivo Mobile (AS27699) and TIM Mobile (AS41059) often filter differently from their fixed-line counterparts. A page can work on Claro fixed and fail on Claro mobile.
- 4
Record HTTP status, DNS result, and final URL per carrier. A
451or DNS failure across all four means an Anatel / judicial block. A403or block page on one means a single-ISP filter. A wrong final URL means a hijacked redirect. - 5
Screenshot the result on each carrier. A block page rendered from Vivo Mobile is the proof — not the status code.
- 6
Compare against a datacenter probe. If AWS São Paulo gets
200while four residential ASNs return errors, the server is fine — the path between users and the server is filtered. - 7
Set continuous per-carrier monitoring with alerts. Anatel orders flip the filter within hours. Per-carrier alerts catch it before a partner does.
Brazilian carrier reference table
| Carrier | ASN (fixed) | ASN (mobile) | Coverage notes |
|---|---|---|---|
| Vivo (Telefônica Brasil) | AS26599 | AS27699 | Largest mobile + fixed; first to enforce regulator orders. |
| Claro (América Móvil) | AS28573 | AS28573 | Strong SE + NE region presence; aggressive WAF behavior. |
| TIM Brasil | AS26615 | AS41059 | Mobile filter often differs from fixed; always test both. |
| Oi | AS7738 | AS7738 | Slower to enforce orders; useful as a "lag indicator". |
How to read the result
| Pattern across 4 carriers | Likely cause | Fix path |
|---|---|---|
| 4 / 4 fail with 451 or DNS error | Anatel / judicial order, country-level block | Switch to a mirror, request unblock through legal channel, rebrand domain. |
| 3 / 4 fail, one still 200 (often Oi) | Anatel order being rolled out — lagging carrier | Treat as full block, prep mirror; track lagging carrier for confirmation. |
| 1–2 carriers fail with 403, others 200 | ASN-level filter or Cloudflare-vs-carrier issue | Open ticket with affected carrier or Cloudflare; whitelist their IP ranges. |
| Only mobile fails, fixed-line 200 | Mobile carrier filter (content classification) | Adjust prelander; contest carrier classification. |
| All 4 carriers see a challenge page | Cloudflare / WAF blocking BR residential / mobile ranges | Loosen Cloudflare bot/firewall rules; whitelist BR ASNs. |
Anatel and the Bets Law (Law 14.790/2023)
Since the implementation of Brazil's regulated betting framework, Anatel and the Ministry of Finance have actively ordered ISPs to block unlicensed iGaming domains. Enforcement is uneven across operators — Vivo Mobile and Claro typically apply orders within hours; TIM within a day; Oi can lag 24–48 hours. If your offer is in iGaming, dating, crypto-adjacent or any regulated vertical, expect periodic country-level blocks and plan mirror rotation accordingly. A multi-carrier monitor is the only way to know when a block lands without waiting for affiliates to complain.
Related reading
For background on per-network checks, read what is ASN monitoring. For mirror rotation playbook, see how to monitor rotating mirror domains. To prove the block to your partners, see how to know if a domain is blocked in a country.
FAQ
How do I check if my landing page is blocked in Brazil?
Test the URL from real residential and mobile networks inside Brazil on all four major carriers: Vivo (AS26599 / AS27699 mobile), Claro (AS28573), TIM (AS26615 / AS41059 mobile), and Oi (AS7738). If three or four of them return 403, 451, a DNS failure, or a block page while a datacenter probe gets 200, the page is blocked at the country or carrier level. If only one or two fail, it is an ASN-level block on those specific operators.
Which ASNs should I check to cover Brazil?
Cover the four operators that account for almost all Brazilian internet users: Vivo (Telefônica), Claro, TIM, and Oi. Check each on fixed-line and mobile separately — Vivo Mobile (AS27699) often filters differently than Vivo Fixed (AS26599), and the same is true for TIM (AS41059 mobile vs AS26615 fixed).
Does Anatel block websites in Brazil?
Anatel is the Brazilian telecom regulator and can issue blocking orders that ISPs are required to enforce — most notably against unlicensed iGaming and certain gambling sites under Law 14.790/2023 (the Bets Law). When that happens, multiple carriers begin returning DNS failures or block pages within hours of the order. A court order can also force a block via the judiciary. Checking from several ASNs at once tells you whether you're seeing a regulator-driven country-wide block or a single-operator filter.
Why does my page work from São Paulo but not from a Vivo Mobile user?
Different ASNs apply different filters. A Vivo fixed-line connection in São Paulo and a Vivo Mobile connection in the same building can sit behind different filtering rules — mobile operators often enforce regulator orders, content filtering, or carrier-grade NAT policies that fixed-line networks ignore. Always test mobile separately from fixed-line.
How do I prove to a Brazilian affiliate partner that their offer is blocked?
Capture timestamped screenshots and HTTP status codes from Vivo, Claro, TIM, and Oi (mobile and fixed) inside Brazil. A shareable incident report showing four red carriers in a single market, with the actual block page rendered, settles the dispute in minutes and supports a media-spend refund or chargeback.
What is the difference between a Brazilian country block and a Vivo-only block?
A country block (typically Anatel-driven) hits all four major Brazilian operators within a short window. A Vivo-only block — usually a carrier rule, a Cloudflare-vs-Vivo dispute, or a WAF treatment of Vivo's IP ranges — only affects Vivo users while Claro, TIM, and Oi keep working. Always check all four to tell them apart.
Edits
- 2026-05-27: First published.
Monitor your URL from Vivo, Claro, TIM and Oi
Per-carrier checks from real Brazilian residential and mobile networks, with screenshot proof of every block. Free trial includes 8 ASNs — enough to cover Brazil with mobile splits.