Live  /  Supabase  /  Incident

Supabase: Projects stuck in restarting state

Supabase · supabase.comResolved2026-10-21 05:39 UTC
Public — what happened

Summary

Supabase said some projects in its us-east-2 region were stuck in a restarting state, beginning around 21:59 UTC on October 20, 2026. About an hour later the company said it had found the root cause and was preparing a fix, which it began rolling out to affected projects shortly before midnight UTC. Supabase reported that no new projects were affected as the rollout continued, and by 04:47 UTC on October 21 it said the fix was fully deployed and projects were no longer stuck. The incident was marked resolved at 05:39 UTC.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Supabase against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Supabase: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Supabase report →

More from Supabase

Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.

The full archive is on the Supabase status & history page.

Related: Supabase status & history. SquidGrid is not affiliated with Supabase.