Major incident

Supabase: Unresponsive Projects

Current status of Supabase: Operational — live Supabase status

Timeline

1. Sep 10, 2026, 15:26 UTC
   investigating
   We are aware of Nano projects becoming unresponsive after a period of time, typically hours. We are investigating.
2. Sep 10, 2026, 15:46 UTC
   identified
   We have identified why projects are becoming unresponsive and are implementing a mitigation.
3. Sep 10, 2026, 17:13 UTC
   identified
   A refined fix is being rolled out to specific regions, we are assessing the impact of the fix.
4. Sep 10, 2026, 17:59 UTC
   identified
   Fix rollouts have been successful in the initial regions, we are proceeding to roll out the fix globally.
5. Sep 10, 2026, 19:41 UTC
   identified
   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. Sep 11, 2026, 03:44 UTC
   monitoring
   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. Sep 11, 2026, 06:19 UTC
   monitoring
   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 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. Sep 11, 2026, 19:06 UTC
   resolved
   This incident has been resolved.

Updates as published by Supabase.