Live / Supabase / Incident
Supabase: Upgrade Issues
Supabase · supabase.comMinor incidentResolved2026-10-06 18:18 UTC
Public — what happened
Summary
Supabase reported a minor incident on 2026-10-06 starting at 15:23 UTC, in which some attempts to upgrade projects to version 17.11.0.003 were failing. The company said the problem only affected projects moving from older PG17 versions to the newest release, and it temporarily paused all project upgrades at 16:03 UTC after pinpointing the issue. Supabase said it built and rolled out a fix, brought upgrades back by 17:27 UTC, and marked the incident resolved at 18:18 after a period of monitoring.
Timeline
- Started — 2026-10-06 15:23 UTC
- Investigating — 2026-10-06 15:23 UTC
- Identified — 2026-10-06 16:03 UTC (2 updates)
- Monitoring — 2026-10-06 17:27 UTC
- Resolved — 2026-10-06 18:18 UTC · 2h 56m 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.