rewindex

ChangesSupabaseProjects stuck in restarting state

Supabase: Incident updated: Projects stuck in restarting state

Incident updateNormal progress (rule, 100%)Changed status.supabase.com (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

Struck in red is what Supabase removed; blue is what they added. Muted text is unchanged context.

ChangedStatus#1
Before: identified
After: monitoring
AddedUpdatemonitoring#2
Before: not present
After: The fix has fully rolled out. Projects are no longer stuck in a restarting state. We will continue to monitor the situation.

Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

History of this incident

Wednesday, October 21

5 incident changes

Tuesday, October 20

2 incident changes

Cite this

Incident updated: Projects stuck in restarting state on Supabase’s status page, changed 2026-10-21 04:53 UTC (change 6 of 7).

Title
Incident updated: Projects stuck in restarting state
Vendor
Supabase
Date
URL
https://rewindex.com/change/r96790b942d9cdb

All Supabase changesSupabase profileMarkdownJSON