Live / Supabase / Incident
Supabase: Increased errors on management api leading to project operation failures
Supabase · supabase.comMinor incidentResolved2026-10-06 09:03 UTC
Public — what happened
Summary
Supabase said that starting at 07:53 UTC on 2026-10-06, its management API was returning more errors than usual, causing failures when users tried to create, pause, unpause or upgrade projects in several regions. By 08:13 UTC the company said it had traced the problem to a rollout, which it said was also behind authentication errors across multiple functions, and that a fix was in place with recovery underway. Supabase rated the issue as minor and marked it resolved at 09:03.
Affected
Management API
Timeline
- Started — 2026-10-06 07:53 UTC
- Investigating — 2026-10-06 07:53 UTC (2 updates)
- Monitoring — 2026-10-06 08:13 UTC
- Resolved — 2026-10-06 09:03 UTC · 1h 10m 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 42, 2026, our weekly internet health report.