Companies / Supabase / incidents

Supabase: Unresponsive Projects

Timeline of updates

1. investigating2026-09-10 15:26 UTC

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

2. identified2026-09-10 15:46 UTC

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

3. identified2026-09-10 17:13 UTC

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

4. identified2026-09-10 17:59 UTC

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

5. identified2026-09-10 19:41 UTC

   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.

6. monitoring2026-09-11 03:44 UTC

   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.

7. monitoring2026-09-11 06:19 UTC

   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.

8. resolved2026-09-11 19:06 UTC

   This incident has been resolved.

Impact, status and times are the vendor’s own, as last archived. View on status.supabase.com (opens in new tab). Supabase profile · Recent Supabase incidents · Markdown · JSON