Supabase incident

Edge Functions experiencing high response times in ap-northeast-1 and ap-northeast-2

Major Resolved View vendor source →

Supabase experienced a major incident on March 6, 2026 affecting Edge Functions, lasting 5h 9m. The incident has been resolved; the full update timeline is below.

Started
Mar 06, 2026, 02:26 PM UTC
Resolved
Mar 06, 2026, 07:36 PM UTC
Duration
5h 9m
Detected by Pingoru
Mar 06, 2026, 02:26 PM UTC

Affected components

Edge Functions

Update timeline

  1. investigating Mar 06, 2026, 02:26 PM UTC

    We are currently investigating the cause for increased response times.

  2. investigating Mar 06, 2026, 02:47 PM UTC

    We are continuing to investigate reports of Edge Functions experiencing high response times in Asia Pacific regions Our team is still working to determine the underlying cause. We understand the disruption this may be causing and are treating this with high priority.

  3. investigating Mar 06, 2026, 03:17 PM UTC

    We are continuing to investigate reports of Edge Functions experiencing high response times in Asia Pacific regions Our team is still working to determine the underlying cause. We understand the disruption this may be causing and are treating this with high priority.

  4. identified Mar 06, 2026, 03:46 PM UTC

    Response times in the ap-northeast-1 (Tokyo) region have improved following mitigation efforts. We are currently rolling out the fix to the ap-northeast-2 (Seoul) region. Further updates will be provided as the rollout continues.

  5. monitoring Mar 06, 2026, 03:56 PM UTC

    Response times in both the ap-northeast-1 (Tokyo) and ap-northeast-2 (Seoul) regions have now stabilised. We will continue to monitor the systems closely to ensure stability.

  6. resolved Mar 06, 2026, 07:36 PM UTC

    Both regions are now working as usual.