Live / Supabase / Incident
Supabase: Elevated Mgmt API Error Rates in Multiple Regions
Supabase · supabase.comMajor incidentResolved2026-10-22 13:42 UTC
Public — what happened
Summary
Supabase reported a major incident starting at 11:29 UTC on 2026-10-22, in which its Management API had more errors and slower responses across multiple regions. The company said tasks relying on it, such as creating new projects, could fail or be slow, and that logins to supabase.com were also timing out. At 12:07 UTC Supabase said it had applied a mitigation and that error rates and response times were back to normal, and it kept watching for stability. The incident was marked resolved at 13:42, and no cause was given in the text.
Timeline
- Started — 2026-10-22 11:29 UTC
- Investigating — 2026-10-22 11:29 UTC (2 updates)
- Monitoring — 2026-10-22 12:07 UTC
- Resolved — 2026-10-22 13:42 UTC · 2h 13m 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.