Live / Supabase / Incident
Supabase: Project lifecycle operation errors in the EU region
Supabase · supabase.comMajor incidentResolved2026-10-22 15:56 UTC
Public — what happened
Summary
Supabase said it saw more failures than usual when people tried to create, restore, or pause projects in its EU region, starting around 23:00 UTC on 21 October. In its first update at 03:53 UTC on 22 October, the company said it had applied a mitigation and that error rates had dropped back to normal, while it worked on fixing projects that were affected. A later update at 09:15 UTC said error levels were still normal and that it was continuing to watch for stability. Supabase marked the incident resolved at 15:56 UTC on 22 October and did not state a cause in the text provided.
Timeline
- Started — 2026-10-22 03:53 UTC
- Monitoring — 2026-10-22 03:53 UTC (2 updates)
- Resolved — 2026-10-22 15:56 UTC · 12h 03m after it started
With SquidGrid — where it starts on the route
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 seeCustomers 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.