Supabase incident
Error spikes in one of the ap-northeast-2 Supavisor clusters
Resolved after 3 h 49 min.
- Started
- Ended
- Worst state
- Degraded
- On Supabase’s status page
- Source
Timeline
- Supabase status page · Reported Error spikes in one of the ap-northeast-2 Supavisor clusters
- Supabase status page · 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.
- Supabase status page · Investigating We are continuing to investigate the errors in ap-northeast-2 Supavisor clusters.
- Supabase status page · 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.
- Supabase status page · Resolved The issue has been resolved.
Cite this incident
Site Qwality, “Error spikes in one of the ap-northeast-2 Supavisor clusters,” Aug 24, 2026, https://siteqwality.com/is-supabase-down/incidents/supabase-202608240602/
Free to quote with a link to this page.