BREAKING: Supabase Access Issues From Brazil Providers — Workarounds Inside

Supabase experiencing connectivity issues from specific providers in Brazil. Check status and apply immediate workarounds.

Incident Summary

Supabase is currently experiencing access issues from some internet service providers (ISPs) in Brazil. The issue appears to be connectivity-related rather than a complete platform outage. Database and authentication services may be intermittently unavailable for affected users.

What Is Affected

Database connections from Brazilian ISP networks

Real-time subscriptions may experience delays or disconnections

API requests originating from affected Brazilian providers

Authentication flows for users in affected regions

What is NOT affected:

Supabase infrastructure itself appears operational

Users outside Brazil or on unaffected ISPs

Deployed applications may continue functioning if connection pooling is configured

Immediate Workarounds

1. Connection Pooling (Recommended)

Enable PgBouncer connection pooling in your Supabase project:

Navigate to Database Settings → Connection Pooling

Enable pooling mode (set to "Transaction" or "Session")

Use the pooling connection string instead of direct connections

This masks temporary connectivity interruptions

2. Use VPN/Proxy Services

Route traffic through a VPN provider outside Brazil

This bypasses ISP-level routing issues

Consider services like Cloudflare WARP, NordVPN, or ExpressVPN

3. Implement Retry Logic

```javascript const retryConnection = async (maxRetries = 5) => { for (let i = 0; i < maxRetries; i++) { try { return await supabase.from('table').select(); } catch (error) { if (i === maxRetries - 1) throw error; await new Promise(r => setTimeout(r, 1000 * (i + 1))); } } }; ```

4. Failover to Edge Functions

Deploy Supabase Edge Functions in regions closer to Brazil (São Paulo if available)

Reduces latency and improves reliability

5. Queue Non-Critical Operations

Implement message queues (Redis, Bull) for non-essential database writes

Process queued items once connectivity stabilizes

How to Check If You're Affected

1. Check Supabase Status Page: https://status.supabase.com 2. Test connectivity manually: ```bash curl -X GET 'https://YOUR_PROJECT.supabase.co/rest/v1/' \ -H 'apikey: YOUR_ANON_KEY' ``` 3. Check your ISP: Contact your Brazilian ISP to confirm routing issues 4. Test from different networks: Try 4G, corporate network, or VPN 5. Monitor logs: Check application error logs for connection timeout patterns

Alternatives During Outage

Firebase Realtime Database: Quick migration for real-time apps

AWS RDS Proxy: Direct PostgreSQL with connection pooling

Planet Scale: MySQL-compatible serverless alternative

Vercel KV: For caching to reduce database load

Status Updates

Monitor:

[Supabase Status Page](https://status.supabase.com)

Supabase Discord #incidents channel

Your application error tracking (Sentry, LogRocket)

Next Steps

1. Apply connection pooling immediately if not already enabled 2. Implement retry logic in your application 3. Monitor error rates from Brazilian users 4. Contact your ISP if personal testing confirms their involvement 5. Have failover plan ready if connectivity doesn't improve

Note: This appears to be a regional/ISP-specific issue. Impact varies by provider. Stay updated on official Supabase channels for resolution timeline.