Companies / Supabase / incidents

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

Impact: noneStatus: resolvedStarted Resolved (3.8 h)4 updatesSource: status.supabase.com (opens in new tab)

Timeline of updates

  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.

Impact, status and times are the vendor’s own, as last archived. View on status.supabase.com (opens in new tab). Supabase profile · Recent Supabase incidents · Markdown · JSON