Supabase Status · History · Incident #5169

RESOLVED

Endpoints in Americas regions returning 500 Internal server error

Major · Started Jul 6, 2026 · 2:45 PM

  • Duration

    1h 25m

  • Severity

    Major

  • Detection lead

  • User reports

Summary

Endpoints in Americas regions returning 500 Internal server error

Operations have returned to normal. We are implementing improvements to prevent similar recurrences in the future.


  • Started

    Jul 6, 2026 · 2:45 PM

  • Resolved

    Jul 6, 2026 · 4:10 PM

  • Duration

    1h 25m

  • Severity

    Major

Event timeline

How this incident unfolded

  • Investigating

    Jul 6 · 2:45 PM Supabase

    Multiple endpoints are returning 500 Internal server errors across our platform. We are investigating what has caused these errors.

  • Investigating

    Jul 6 · 2:47 PM Supabase

    The 500 errors are limited to us-east-1, we are actively exploring causes.

  • Investigating

    Jul 6 · 3:10 PM Supabase

    The scope of the errors is across regions in the Americas. We are narrowing down the likely causal chains.

  • Identified

    Jul 6 · 3:15 PM Supabase

    We have identified the cause of the 500 errors and are implementing a fix.

  • Monitoring

    Jul 6 · 3:42 PM Supabase

    The fix has been applied and there are improvements to the error rates. We are continuing to work on ensuring the underlying issue does not recur.

  • Resolved

    Jul 6 · 4:10 PM Supabase

    Operations have returned to normal. We are implementing improvements to prevent similar recurrences in the future.

Get alerted before the next Supabase outage.

Pulsetic catches degradations minutes before vendors acknowledge them.

Start monitoring free