Live / Supabase / Incident
Supabase: Increased Errors with Project Lifecycle Operations in US-West-2
Supabase · supabase.comMinor incidentResolved2026-11-07 02:17 UTC
Public — what happened
Summary
Supabase said that starting at 23:49 UTC on 2026-11-06, actions that manage projects in its US-West-2 region, such as creating new projects, unpausing, restoring, resizing and restarting, could fail. The company attributed this to a problem at an upstream provider affecting EC2 instances, and said projects that were already running were not affected. It advised customers to avoid those actions in the region while it worked with the provider. By 01:34 UTC on 2026-11-07 Supabase reported that the provider had made changes and project creation was recovering, and the incident was marked resolved at 02:17 UTC.
Timeline
- Started — 2026-11-06 23:49 UTC
- Identified — 2026-11-06 23:49 UTC (2 updates)
- Monitoring — 2026-11-07 01:34 UTC
- Resolved — 2026-11-07 02:17 UTC · 2h 28m 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 46, 2026, our weekly internet health report.