BREAKING: Supabase Access Issues in Brazil – Workarounds Available

Supabase experiencing connectivity issues from some providers in Brazil. Immediate workarounds and status checks inside.

Incident Summary

Supabase is currently experiencing access issues from certain internet providers in Brazil. This appears to be a regional connectivity problem rather than a complete service outage.

What's Affected

Database connections from Brazilian ISPs to Supabase infrastructure

API requests originating from affected Brazilian providers

Real-time features (Realtime subscriptions) may experience delays or disconnections

Not affected: Supabase infrastructure itself appears healthy; issue is regional routing/access

How to Check If You're Affected

1. Check your location: Are your users or servers in Brazil? 2. Test connectivity: Try connecting to your Supabase project from Brazil using: ```bash curl -v https://[your-project].supabase.co/rest/v1/ ``` 3. Monitor your app logs for connection timeouts or refused connections 4. Check Supabase Status Page: Visit status.supabase.com for real-time updates 5. Verify your ISP: Some Brazilian providers are affected; others are not

Immediate Workarounds

1. Use VPN/Proxy (Temporary)

Route traffic through a VPN endpoint outside Brazil

This confirms whether the issue is Brazil-specific

Note: Not recommended for production long-term

2. Implement Connection Retry Logic

```javascript const { createClient } = require('@supabase/supabase-js')

const supabase = createClient(url, key, { db: { schema: 'public', }, auth: { persistSession: true, }, global: { fetch: fetch.bind(globalThis), }, realtime: { params: { eventsPerSecond: 10, }, }, }) ``` Add exponential backoff retry mechanisms in your application code.

3. Use Regional Alternatives (If Available)

If you have infrastructure in other regions, route Brazilian traffic there temporarily

Consider using a CDN with edge locations in Brazil

4. Implement Client-Side Caching

Cache frequently accessed data locally

Reduce real-time dependency during the incident

Queue mutations for retry when connection restores

5. Switch to HTTPS Polling (Temporary)

Disable Realtime subscriptions temporarily

Switch to standard REST API polling with longer intervals

Reduces connection frequency

Alternative Services to Consider

Firebase/Firestore – alternative BaaS with different infrastructure

AWS RDS with API Gateway – more control over routing

Vercel Edge Functions – for distributed request handling

Cloudflare Workers – for edge-based request routing

Next Steps

1. Monitor Supabase status page continuously 2. Implement connection retry logic immediately 3. Communicate with Brazilian users about temporary slowdowns 4. Avoid making infrastructure changes during incident 5. Document which ISPs are affected for future reference

Updates

I'm unsure of:

Specific affected ISPs (this changes with incidents)

Exact ETA for resolution (depends on Supabase investigation)

Whether this affects all Brazilian regions equally

Check official Supabase status page for authoritative updates.

Last Updated: Monitor status.supabase.com for real-time incident updates.