Skip to content
OutageDeck

Incident detail

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

Resolved incidentMinor

Timeline window

to

Get alerted the next time Supabase breaks

Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Set up free alertsHow Supabase alerts work

Timeline

Incident updates

Every update on the official status source, oldest to newest, exactly as it appeared there.

  1. 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.

  2. Investigating

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

  3. 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.

  4. Resolved

    The issue has been resolved.

Keep exploring

More from Supabase

Neighboring incidents on Supabase's timeline and the rest of their record on OutageDeck.

← Older incident

Error spikes in one of the eu-east-1 Supavisor clusters

Newer incident →

Issues affecting automatic disk resizing

All Supabase incidentsSupabase live status