Supabase incident
Higher connection failure rate for ap-northeast-1 and ap-northeast-2
Resolved on June 10, 2026.
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.
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.
Your product runs on more than Supabase
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services