BREAKING: Supabase Intermittent Latency in Eastern US Region — Workarounds Inside

Supabase experiencing intermittent latency affecting Eastern US users. Immediate workarounds and status checks available.

Incident Summary

Supabase is currently experiencing intermittent latency in the Eastern US region. This is affecting database query response times and API calls for projects hosted in or connecting through eastern availability zones.

What's Affected

Database queries experiencing 2-10x slower response times

REST API endpoints showing increased response times

Real-time subscriptions may experience connection instability

Authentication services may have delayed responses

Impact appears regional (Eastern US primarily), with Western US and EU regions reportedly unaffected

*Note: We're unsure if Edge Functions or Vector operations are separately impacted—check your specific service.*

Immediate Workarounds

1. Route to Alternate Regions

If your application supports it:

Temporarily redirect traffic to Western US or EU regions if you have multi-region deployments

Configure your client SDK to use backup endpoints if available

2. Implement Client-Side Retry Logic

```javascript // Add exponential backoff for failed requests const MAX_RETRIES = 3; const BASE_DELAY = 1000; // 1 second

async function queryWithRetry(query, retries = 0) { try { return await supabase.from('table').select().execute(); } catch (error) { if (retries < MAX_RETRIES) { await new Promise(r => setTimeout(r, BASE_DELAY * Math.pow(2, retries))); return queryWithRetry(query, retries + 1); } throw error; } } ```

3. Enable Query Caching

Implement aggressive caching in your application layer (Redis, in-memory)

Reduce unnecessary queries by batching requests

Cache user sessions and frequently accessed data

4. Use Connection Pooling

Ensure PgBouncer is properly configured:

Verify pool mode is set to transaction

Monitor active connections to prevent exhaustion

5. Temporarily Increase Timeouts

```javascript const { data, error } = await supabase .from('table') .select() .timeout(15000); // Increase from default 5000ms ```

How to Check If You're Affected

1. Check Supabase Status Page: Visit status.supabase.com and look for regional incident reports 2. Monitor Your Logs: Check for increased response times in the last 30 minutes 3. Query Performance: Run simple SELECT 1 queries and measure latency 4. Geographic Test: Test from Eastern US IP versus other regions to confirm regional impact 5. Supabase Dashboard: Navigate to Project → Logs → Slow Queries for performance insights

Alternatives While Investigating

Temporary fallback database: Route non-critical queries to a secondary database (if available)

Queue critical operations: Use job queues to defer non-urgent writes

Read replicas: If configured, route read operations to replicas outside the affected region

Disable real-time: Temporarily disable real-time subscriptions and use polling instead

Next Steps

Monitor the Supabase status page for updates

Check your project's metrics dashboard for improvement signals

Contact Supabase Support if latency persists beyond 2 hours

Implement permanent multi-region failover if this recurs

Last Updated: Check status.supabase.com for latest incident timeline.

*We recommend monitoring your application metrics closely during this incident.*