Supabase Status · History · Incident #6637

RESOLVED

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

Minor · Started Aug 24, 2026 · 6:02 AM

  • Duration

    3h 49m

  • Severity

    Minor

  • Detection lead

  • User reports

Summary

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

The issue has been resolved.


  • Started

    Aug 24, 2026 · 6:02 AM

  • Resolved

    Aug 24, 2026 · 9:51 AM

  • Duration

    3h 49m

  • Severity

    Minor

Event timeline

How this incident unfolded

  • Investigating

    Aug 24 · 6:02 AM Supabase

    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 · 7:07 AM Supabase

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

  • Monitoring

    Aug 24 · 9:13 AM Supabase

    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 · 9:51 AM Supabase

    The issue has been resolved.

Get alerted before the next Supabase outage.

Pulsetic catches degradations minutes before vendors acknowledge them.