Supabase Status · History · Incident #7099

ACTIVE INCIDENT

Unresponsive Projects

Major · Started Sep 10, 2026 · 3:26 PM

  • Duration

    Ongoing

  • Severity

    Major

  • Detection lead

  • User reports

    Peak 1/hr

Summary

Unresponsive Projects

We have rolled out a fix across all regions and are continuing to monitor over the next few hours. Due to this incident, impacted users who's project were compute constrained would have received a 'Your Supabase Project <Name> is running out of Disk IO Budget' email which is no longer valid. No further action is required and your project availability should be restored to normal.


  • Started

    Sep 10, 2026 · 3:26 PM

  • Status

    Monitoring

  • Duration

    Ongoing

  • Severity

    Major

Event timeline

How this incident unfolded

  • Investigating

    Sep 10 · 3:26 PM Supabase

    We are aware of Nano projects becoming unresponsive after a period of time, typically hours. We are investigating.

  • Identified

    Sep 10 · 3:46 PM Supabase

    We have identified why projects are becoming unresponsive and are implementing a mitigation.

  • Identified

    Sep 10 · 5:13 PM Supabase

    A refined fix is being rolled out to specific regions, we are assessing the impact of the fix.

  • Identified

    Sep 10 · 5:59 PM Supabase

    Fix rollouts have been successful in the initial regions, we are proceeding to roll out the fix globally.

  • Identified

    Sep 10 · 7:41 PM Supabase

    We have rolled out a version of the fix across all regions that will prevent recurrence of the issue. Users still affected by project outages are encouraged to restart their projects.

  • Monitoring

    Sep 11 · 3:44 AM Supabase

    We have rolled out a fix across all regions and are continuing to monitor over the next few hours. Users still affected by project outages are encouraged to restart their projects which has shown to resolve lasting errors.

  • Monitoring

    Sep 11 · 6:19 AM Supabase

    We have rolled out a fix across all regions and are continuing to monitor over the next few hours. Due to this incident, impacted users who's project were compute constrained would have received a 'Your Supabase Project <Name> is running out of Disk IO Budget' email which is no longer valid. No further action is required and your project availability should be restored to normal.

User reports · incident window

Report volume over time

Hourly report count. Red bars mark the incident window.

Peak: 1 reports/hr

← Before incident After →

Get alerted before the next Supabase outage.

Pulsetic catches degradations minutes before vendors acknowledge them.