BREAKING: Supabase Access Issues in Brazil – Workarounds Available

Supabase experiencing regional access issues from some providers in Brazil. Monitoring ongoing. Immediate workarounds and status checks inside.

Incident Summary

Supabase is currently experiencing access connectivity issues affecting some internet service providers (ISPs) in Brazil. The issue appears to be regional and provider-specific rather than a complete service outage.

What's Affected

Database connections from certain Brazilian ISPs to Supabase infrastructure

API endpoints may experience intermittent timeouts for affected users

Real-time subscriptions could drop for users in impacted regions

Impact is not global – most regions outside Brazil are unaffected

How to Check If You're Affected

1. Check your location: Are you or your users connecting from Brazil? 2. Test connectivity: Run a simple database query and check response times 3. Monitor logs: Look for connection timeout errors (typically 30-60 second failures) 4. Check Supabase status page: Visit status.supabase.com for official updates 5. ISP verification: Contact your ISP if you're in Brazil – this may be routing-related

Immediate Workarounds

Short-term Solutions

1. Use VPN/Proxy Services

Routing traffic through a VPN provider outside Brazil may bypass ISP-level routing issues

Note: This adds latency and should only be temporary

2. Implement Retry Logic

Add exponential backoff to database queries

Retry failed connections after 2-5 second delays

Most client libraries support this natively

3. Connection Pooling

Use PgBouncer or similar tools to maintain persistent connections

Reduces reconnection overhead during intermittent failures

4. Cache Responses

Implement application-level caching for frequently accessed data

Reduces dependency on real-time database connectivity

Consider Redis or similar in-memory solutions

5. Regional Failover

If you have multiple Supabase projects in different regions, route Brazilian traffic to non-Brazilian infrastructure (if latency permits)

I'm unsure if Supabase currently offers multi-region replication – check documentation

Developer Actions

```

Notify affected users about potential slower responses

Monitor error rates in your observability tools

Increase timeout thresholds temporarily (be cautious)

Consider rate limiting to prevent cascade failures

```

What NOT to Do

❌ Don't dramatically increase timeout values permanently

❌ Don't attempt to migrate data during the incident

❌ Don't disable monitoring – keep close watch

Next Steps

1. Monitor official channels: Follow @supabase on Twitter and status.supabase.com 2. Contact Supabase support: If you're a paying customer, escalate through official channels 3. Document the incident: Log timestamps and affected user regions for your records 4. Prepare contingency: Have a plan for extended outages

Current Status

Supabase team is actively monitoring. Regional nature suggests BGP/routing issues rather than infrastructure failure. Resolution timeline is uncertain.

Last Updated: Check official Supabase status page for real-time updates.

*Disclaimer: This report is based on available incident information. Specific technical details about the root cause are not yet confirmed by Supabase.*