Unresponsive Projects

Timeline

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