Projects stuck in restarting state
Supabase · Last saved provider status: identified
The last saved event status is not the current service status. Source lists can be incomplete, and disappearance from a source does not confirm recovery. Open the current report or the official source for newer evidence.
Saved event details
- Provider status
- identified
- Provider impact
- none
- Provider record created
- 20 Oct 2026, 21:59:16 UTC
- Provider record updated
- 20 Oct 2026, 23:06:44 UTC
- Explicit provider start
- Not available
- Explicit provider end
- Not available
Affected components reported by the provider
Component associations were not provided or have not been recovered for this saved revision.
These associations describe this event’s reported scope. They do not establish current component availability or verified dependencies.
A record creation time is not necessarily an outage start. Unreported times remain unavailable. We do not calculate downtime from collection times.
Supabase's published platform indicator and currently listed components, incidents and scheduled maintenance. The component list may cover only part of the platform during its status-page migration. Missing lists remain unavailable; provider region names do not verify regional access or a particular project's health.
Provider updates in saved revisions
Latest first. We show up to 100 distinct updates from the latest 20 saved content revisions. Revised wording at the same provider time is retained separately.
- 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.
Seen in a saved revision at 20 Oct 2026, 23:06:58 UTC - 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.
Seen in a saved revision at 20 Oct 2026, 23:06:58 UTC