Supabase incident
Higher connection failure rate for ap-northeast-1
Supabase experienced a notice incident on June 10, 2026, lasting —. The incident has been resolved; the full update timeline is below.
Update timeline
- resolved Jun 10, 2026, 01:43 AM UTC
From 00:52 to 01:02 UTC on 10th June an internal deployment in one of the ap-northeast-1 clusters caused a higher connection failure rate. Users would have experienced failing connections, increased query latency and would not have been able to retrieve pooler metrics. The deployment has now been reverted and full service availability restored.