# Supabase: Error spikes in one of the ap-northeast-2 Supavisor clusters

- Impact (vendor’s label): none
- Status: resolved
- Started: 2026-08-24 06:02 UTC · Resolved: 2026-08-24 09:51 UTC · Duration: 3.8 h
- Updates: 4
- [Vendor status page: https://status.supabase.com/incidents/01M0S5S8XFZ97JKPYD7N6W2C0Z](https://status.supabase.com/incidents/01M0S5S8XFZ97JKPYD7N6W2C0Z)
- [Company: Supabase](https://rewindex.com/company/supabase.md)

## Timeline of updates

- **investigating** 2026-08-24 06:02 UTC: 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** 2026-08-24 07:07 UTC: We are continuing to investigate the errors in ap-northeast-2 Supavisor clusters.
- **monitoring** 2026-08-24 09:13 UTC: 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** 2026-08-24 09:51 UTC: The issue has been resolved.


---
Canonical: https://rewindex.com/company/supabase/incidents/01M0S5S8XFZ97JKPYD7N6W2C0Z · Markdown: https://rewindex.com/company/supabase/incidents/01M0S5S8XFZ97JKPYD7N6W2C0Z.md · JSON: https://rewindex.com/api/v1/companies/supabase/incidents/01M0S5S8XFZ97JKPYD7N6W2C0Z · Generated 2026-10-18T09:43:32.859Z