Increased rates of Pooler connection timeouts in us-east-1
Aug 24, 15:26 UTCAug 24, 16:38 UTC
Duration
1h 12m
Impact
Informational
Root cause
Not disclosed
Supabase, 90 days
56 incidents
Affected
Connection Pooler
Final update
This incident has been resolved.
Timeline
- Resolved · Aug 24, 16:38 UTC
This incident has been resolved.
- Monitoring · Aug 24, 15:38 UTC
We have identified a degraded Supavisor node and we have rolled out a fix. We are monitoring to ensure continued stability. Confirmed Impact: On Aug 24, 2026 between 14:30 and 15:20 UTC we observed increased rates of connection timeouts connecting to Supavisor in us-east-1 due to a degraded node.
- Investigating · Aug 24, 15:26 UTC
We are aware of reports of increased rates of connection timeouts for users connecting to Projects in us-east-1 via Supavisor.
More from Supabase
Full historyInterruption in connections to Supavisor in eu-west-2lasted 1h 42mIncreased Errors with Project Lifecycle Operations in US-West-2lasted 2h 28mIntermittent 502/503 errors for pg_net calls to Edge Functionslasted 42mStorage issues in us-east-1 and eu-central-1lasted 16h 18mIntermittent errors on Supavisor Shared Pooler in us-east-2lasted 29mManagement API Postgres config updates overwriting previous updateslasted 2h 8m