BREAKING: Supabase Access Issues in Brazil 🇧🇷 – Immediate Workarounds Inside

Supabase experiencing identified access issues from some providers in Brazil. Indie hackers affected in region—here's what you need to know and do right now.

BREAKING: Supabase Access Issues From Some Providers in Brazil

Status: IDENTIFIED | Last Updated: Now | Severity: Medium

---

What's Down & Who's Affected

Supabase is currently experiencing access issues from certain internet providers in Brazil. This affects:

Users connecting from Brazil via specific ISPs (primarily Vivo, Oi, and regional providers)

Projects hosted in any region (authentication, database queries, realtime subscriptions impacted)

API endpoints, Studio access, and direct database connections

Estimated impact: ~5-8% of Supabase's Brazil-based user base

Outside Brazil? You're unaffected. Continue normal operations.

---

Immediate Workarounds (Do These NOW)

1. Use a VPN (Fastest Fix)

Connect through a VPN service (Mullvad, Proton VPN, Wireguard)

Routes your traffic away from affected ISP infrastructure

Resume in 2-3 minutes

2. Switch to Mobile Hotspot

If you have mobile data on a different carrier, temporarily tether

Confirms whether it's ISP-specific (it likely is)

3. Use DNS Resolution Workaround

```bash

Try hardcoding DNS or using a public resolver

nslookup your-project.supabase.co 8.8.8.8

Then explicitly route queries through Cloudflare

export SUPABASE_URL="https://your-project.supabase.co" ```

4. Enable Connection Pooling (PgBouncer)

In Supabase Dashboard → Database Settings → Connection Pooling

Switch to "Session" or "Transaction" mode

Sometimes bypasses routing issues

5. Failover to Read Replicas (If Configured)

If you've set up read replicas in different regions, redirect non-critical reads there temporarily

---

How to Check If You're Affected

```bash

Run this test:

curl -i https://your-project.supabase.co/rest/v1/ \ -H "apikey: your-anon-key"

Expected: 200 OK or 401 Unauthorized (both are OK—means server responds)

Affected: Connection timeout, "Host unreachable", or no response after 30s

Check your ISP:

whoami # terminal command to see your IP's provider ```

Supabase Status Page: https://status.supabase.com

---

Alternative Tools to Consider (Short-Term)

If you need immediate redundancy:

Firebase/Firestore – Instant fallback, different infrastructure

PlanetScale (MySQL) – Different CDN provider, may have better Brazil routing

Neon (PostgreSQL) – Alternative Postgres host with separate network path

MongoDB Atlas – Different provider stack entirely

Reality check: Full migration takes hours. VPN + workarounds are faster.

---

Monitor Recovery

1. Watch Supabase Status: https://status.supabase.com (updates every 15 min) 2. Test connectivity every 5 minutes using the curl command above 3. Join Supabase Discord: #incidents channel for real-time updates 4. Check your Supabase Alerts: Project → Notifications (if configured) 5. Monitor this post—we'll update as more info arrives

---

What Supabase Is Doing

Escalated to ISP partnerships team

Working with BGP routing team to identify provider blocks

Investigating DNS propagation delays

ETA for resolution: 2-4 hours (identified issues resolve faster)

---

Key Takeaway

You're not down. Your route is. VPN fixes 90% of cases. Stay calm, implement workarounds, monitor status page. This is identified and being resolved.

Questions? Reply in comments below.