Supabase incident
Error spikes in one of the ap-northeast-2 Supavisor clusters
Resolved after 3 hours 49 minutes, on August 24, 2026.
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.
Update timeline
- investigating Aug 24, 2026, 06:02 AM 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 Aug 24, 2026, 07:07 AM UTC
We are continuing to investigate the errors in ap-northeast-2 Supavisor clusters.
- monitoring Aug 24, 2026, 09:13 AM 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 Aug 24, 2026, 09:51 AM UTC
The issue has been resolved.
Your product runs on more than Supabase
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services