Supabase Status · History · Incident #4468

RESOLVED

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

Minor · Started Jun 10, 2026 · 12:00 AM

  • Duration

    < 1m

  • Severity

    Minor

  • Detection lead

  • User reports

Summary

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

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.


  • Started

    Jun 10, 2026 · 12:00 AM

  • Resolved

    Jun 10, 2026 · 12:00 AM

  • Duration

    < 1m

  • Severity

    None

Event timeline

How this incident unfolded

  • Resolved

    Jun 10 · 1:43 AM Supabase

    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.

Get alerted before the next Supabase outage.

Pulsetic catches degradations minutes before vendors acknowledge them.

Start monitoring free