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

Supabase experiencing access issues from some providers in Brazil. Immediate workarounds for indie hackers affected by this outage.

⚠️ INCIDENT ALERT: Supabase Access Issues in Brazil

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

---

What's Down & Who's Affected

Supabase is reporting access connectivity issues originating from specific ISPs and providers in Brazil. This primarily impacts:

Users accessing Supabase from Brazilian IP addresses

Applications hosted in Brazil connecting to Supabase databases

Some international connections routed through Brazilian infrastructure

Real-time subscriptions and API endpoints

Not affected: US, EU, and most APAC regions (currently). If you're outside Brazil, you're likely okay—but check below.

---

Immediate Workarounds (Do These Now)

1. Use a VPN/Proxy

If you're in Brazil:

Route traffic through a US or EU VPN endpoint

This bypasses the problematic Brazilian ISP routing

Services: Mullvad, ProtonVPN, or CloudFlare WARP (free tier works)

2. Switch to HTTP-Only Mode

Disable real-time subscriptions temporarily

Use REST API instead of WebSocket connections

Add this to your Supabase client:

```javascript const supabase = createClient(url, key, { realtime: { params: { eventsPerSecond: 0 } } }) ```

3. Implement Connection Retries

Add exponential backoff to your connection logic

Retry failed requests with 2s → 4s → 8s delays

Most connections succeed on second/third attempt

4. Use Read Replicas (If Available)

Route queries to alternative database endpoints

Check your Supabase dashboard for replica availability

5. Queue Critical Operations

Don't fail silently—queue writes to local storage

Retry when connection restores

Use browser localStorage or IndexedDB as fallback

---

How to Check If Your Project Is Affected

Quick Check: 1. Go to [status.supabase.com](https://status.supabase.com) → Check incident details 2. In Supabase Dashboard → Settings → Logs → Filter errors by timestamp 3. Look for network timeouts or 503 errors in last 1 hour 4. Test connectivity: ```bash curl -v https://[your-project].supabase.co/rest/v1/ ```

If you see:

Connection timeouts: You're likely affected

Authentication errors: Probably a different issue

200 OK: You're fine

---

Alternative Tools to Consider (Temporary Backup)

If you need immediate redundancy:

Firebase Realtime Database – Quick setup, global CDN

PlanetScale (MySQL) – Database only, no auth layer

MongoDB Atlas – Flexible schema, solid SLA

Fauna – Similar to Supabase, different infrastructure

AWS RDS + Cognito – More complex but battle-tested

Our take: Don't migrate yet. This is likely resolved within hours. Use alternatives only if you can't wait.

---

Monitor Recovery in Real-Time

Watch these channels: 1. Supabase Status Page – [status.supabase.com](https://status.supabase.com) (refresh every 5 min) 2. Discord – Join [Supabase Discord](https://discord.supabase.com) #incidents channel 3. Twitter – Follow [@supabase](https://twitter.com/supabase) 4. GitHub Status – Check [github.com/status](https://github.com/status) (if broader issue)

Expected recovery: Supabase typically resolves regional issues within 1-4 hours. This one's already identified, which is good.

---

Stay Calm. You've Got This.

Outages happen. Your users won't abandon you over a few hours of degradation if you communicate. Update them via status page, and implement the workarounds above.

We'll update this post as Supabase provides more details. Check back in 30 minutes.