Unresponsive Projects

Zeitverlauf

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