Supabase reported this major-impact incident on its official status page on Sep 10, 2026, 15:26 UTC. It was resolved after 1d 3h.
Right now Supabase is degraded. Live Supabase status →
This incident has been resolved.
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.
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.
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.
Fix rollouts have been successful in the initial regions, we are proceeding to roll out the fix globally.
A refined fix is being rolled out to specific regions, we are assessing the impact of the fix.
We have identified why projects are becoming unresponsive and are implementing a mitigation.
We are aware of Nano projects becoming unresponsive after a period of time, typically hours. We are investigating.
Our 5-minute checks didn't record a change in Supabase's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.
Overlapping incidents aren't necessarily related.
Supabase reported 43 incidents in the last 90 days, 16 of them major or critical. A typical incident lasted 2h 2m. See Supabase's uptime and incident history