Live  /  Supabase  /  Incident

Supabase: Project lifecycle operations such as project creation, pausing, and restoration, in all regions

Supabase · supabase.comMajor incidentResolved2026-10-21 16:51 UTC
Public — what happened

Summary

Supabase said it was looking into a problem that affected actions like creating, pausing and restoring projects, in all regions, starting at 15:36 UTC on 2026-10-21. By 16:12 UTC the company reported that it had applied a fix and was seeing fewer failures of these jobs, and it kept watching to make sure things stayed stable. Supabase marked the incident resolved at 16:51 UTC and did not state a cause in the text provided.

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.