Supabase incident

Higher connection failure rate for ap-northeast-1 and ap-northeast-2

Informational Resolved Upstream link ↗

Started

June 10, 2026 at 12:00 AM UTC

Duration

0 min

Resolved

June 10, 2026 at 12:00 AM UTC

Updates timeline

  1. Resolved

    From 00:52 to 01:02 UTC on 10th June an internal deployment in one of the ap-northeast-1 and ap-northeast-2 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.

Live Supabase status

Current indicator + 24h latency

All incidents

Cross-service timeline

Subscribe via RSS

Atom feed for any reader