Supabase incident

Degraded performance of the Shared Pooler cluster in ap-southeast-1

Minor Resolved View vendor source →

Supabase experienced a minor incident on June 24, 2026, lasting 14m. The incident has been resolved; the full update timeline is below.

Started
Jun 24, 2026, 03:59 PM UTC
Resolved
Jun 24, 2026, 04:14 PM UTC
Duration
14m
Detected by Pingoru
Jun 24, 2026, 03:59 PM UTC

Update timeline

  1. investigating Jun 24, 2026, 03:59 PM UTC

    We are aware of a period of degraded performance of the Shared Pooler cluster in ap-southeast-1. Affected projects experienced increased ECHECKOUTTIMEOUT errors when running queries. The window of the incident was between 14:48 to 15:25 UTC. The issue appears to be resolved. We are investigating the cause of this incident and will continue monitoring the cluster.

  2. resolved Jun 24, 2026, 04:14 PM UTC

    One of the processes in the ap-southeast-1 Supavisor cluster became overloaded, causing difficulties in starting new pools. We restarted a node to stabilize the cluster and scaled the cluster up. The issue appears resolved.