Supabase: Projects stuck in restarting state
Timeline of updates
- investigating
Some projects in us-east-2 are stuck in restarting state. We are actively investigating this and will provide more updates as information becomes available.
- identified
We've identified the root cause of this issue and are working on a fix. We will continue to provide updates as things progress.
- identified
We are rolling out a fix to affected projects. We will provide further updates as the rollout progresses.
- identified
We continue with rolling out the fix to affected projects. We will provide further updates as the rollout progresses.
- identified
We continue with rolling out the fix to affected projects. We will provide further updates as the rollout progresses.
- identified
We continue with rolling out the fix to affected projects. No new projects are affected and we will provide further updates as the rollout progresses. Our next update will be in 2 hours.
- monitoring
The fix has fully rolled out. Projects are no longer stuck in a restarting state. We will continue to monitor the situation.
- resolved
All affected projects have be fixed. We have not seen recurrence of the issue and we are resolving the incident.
Changes Rewindex caught on this incident
- Incident updated: Projects stuck in restarting state
- Incident updated: Projects stuck in restarting state
- Incident updated: Projects stuck in restarting state
- Incident updated: Projects stuck in restarting state
- Incident updated: Projects stuck in restarting state
- Incident updated: Projects stuck in restarting state
- Incident updated: Projects stuck in restarting state
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.
First version captured
In the 2026-10-20 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
5660d3394e283510…Version 2 captured
In the 2026-10-20 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
fcd55600c5b82423…Version 3 captured
In the 2026-10-20 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
8e25baa5bdef6209…Version 4 captured
In the 2026-10-21 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
992a7de11541c095…Version 5 captured
In the 2026-10-21 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
0c978890d3b163f4…Version 6 captured
In the 2026-10-21 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
bdca745ed49d072b…Version 7 captured
In the 2026-10-21 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
38fb07d04693fdf7…Version 8 captured
In the 2026-10-21 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
ef44b7c40b1c5df6…
Impact, status and times are the vendor’s own, as last archived. View on status.supabase.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Supabase, started 2026-10-20 21:59 UTC, resolved after 7.7 h, 8 update(s); edited after publishing.
- Title
- Projects stuck in restarting state
- Vendor
- Supabase
- Date
- URL
- https://rewindex.com/company/supabase/incidents/01M5DN6V02FJHZTE9390XJM9YY
Supabase profileRecent Supabase incidentsAll outages on October 20, 2026Supabase in October 2026MarkdownJSON