Supabase incident
Error spikes in one of the ap-northeast-2 Supavisor clusters
Started
August 24, 2026 at 06:02 AM UTC
Duration
3h 49m
Resolved
August 24, 2026 at 09:51 AM UTC
Updates timeline
- Investigating
We are investigating error spikes in the ap-northeast-2 Supavisor clusters. Users reported failures in connecting to postgres via Supavisor with the error: ClientHandler: (ECHECKOUTTIMEOUT) unable to check out connection from the pool after 15000ms in Transaction mode.
- Investigating
We are continuing to investigate the errors in ap-northeast-2 Supavisor clusters.
- Monitoring
We have applied a fix and are monitoring for full resolution. Errors have ceased in the last minutes and all connections are back to healthy.
- Resolved
The issue has been resolved.
Get an email the next time Supabase goes down
Outage alerts for Supabase, straight to your inbox. No account needed, unsubscribe in every email.
Watching more than one service? A free account covers 5 services + a daily digest — and Pro is currently free.
Live Supabase status
Current indicator + 24h latency
All incidents
Cross-service timeline
Subscribe via RSS
Atom feed for any reader