BREAKING: Supabase Access Issues From Brazil Providers Identified – Workarounds Inside

Supabase experiencing connectivity issues from specific Brazilian ISPs. Immediate workarounds and status checks available.

Supabase Access Issues From Brazilian Providers – Live Incident

What's Affected

Supabase is currently experiencing access issues specifically from certain Internet Service Providers operating in Brazil. This appears to be a regional connectivity problem rather than a global outage.

Affected services may include:

Database connections (PostgreSQL access)

API endpoints

Authentication services

Real-time subscriptions

Note: I'm uncertain about which specific Brazilian ISPs are impacted. Check Supabase's status page for the most current provider list.

How to Check If You're Affected

1. Location check: Are you or your users connecting from Brazil? 2. Error symptoms: - Connection timeouts when accessing *.supabase.co domains - "Cannot reach database" errors - API requests hanging or failing 3. Test connectivity: Run ping api.supabase.io or use online tools like mxtoolbox.com to test from Brazilian IPs 4. Official status: Visit [status.supabase.com](https://status.supabase.com) for real-time incident updates

Immediate Workarounds

For End Users in Brazil

VPN/Proxy Solution:

Connect through a VPN service with servers outside Brazil

This bypasses the affected ISP routing

Services like Mullvad, ProtonVPN, or commercial options may help

DNS Changes:

Try switching DNS to 8.8.8.8 (Google) or 1.1.1.1 (Cloudflare)

Some ISP DNS servers may have stale routing information

Wait for ISP routing fixes:

Contact your ISP to report the issue

Most regional issues resolve within 2-6 hours once identified

For Developers

If serving Brazilian users:

Implement retry logic with exponential backoff

Cache data locally where possible to reduce real-time dependency

Use a database connection pooler with failover capabilities

Document the issue for users; provide VPN guidance

Temporary alternatives:

Consider AWS RDS, Google Cloud SQL, or PlanetScale as temporary fallbacks (if you maintain them)

Implement a circuit breaker pattern to gracefully degrade service

Queue requests and retry when connectivity restores

Alternatives & Mitigation

1. Multi-region architecture: Deploy read replicas outside Brazil for Brazilian traffic 2. CDN/Edge caching: Cache API responses to reduce database hits 3. Hybrid approach: Maintain a lightweight PostgreSQL instance in a different region 4. Application-level timeout: Set aggressive timeouts (5-10 seconds) to fail fast

Next Steps

Monitor [status.supabase.com](https://status.supabase.com) for updates

Subscribe to incident notifications

Document which ISPs are affected once officially confirmed

Contact Supabase support if issues persist beyond 6 hours

Important Notes

I'm uncertain about:

Which specific Brazilian ISPs are currently affected

Exact root cause (routing, BGP hijacking, ISP maintenance, DDoS)

Estimated time to resolution

Always verify critical details on the official Supabase status page.

---

Last Updated: Check status.supabase.com for real-time information