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

What to do

• Check whether you use Supabase in ap-northeast-2. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 3h 49m it lasted.

  Anything that failed between 2026-08-24 06:02 UTC and 2026-08-24 09:51 UTC may need a replay.

• Subscribe to Supabase's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=supabase works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Supabase 4

1. investigatingAug 24, 2026, 6: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.

   provider

2. investigatingAug 24, 2026, 7:07 AM UTC

   We are continuing to investigate the errors in ap-northeast-2 Supavisor clusters.

   provider

3. monitoringAug 24, 2026, 9: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.

   provider

4. resolvedAug 24, 2026, 9:51 AM UTC

   The issue has been resolved.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.