Supabase outage on November 6, 2026: Increased Errors with Project Lifecycle Operations in US-West-2
Supabase reported an incident affecting Supabase for 2 hours 28 minutes on 6 November 2026, from 23:49 to 02:17 UTC.
Resolved
Official incident reported by Supabase
- Started
- 23:49
- 6 Nov 2026 UTC
- Resolved
- 02:17
- 7 Nov 2026 UTC
- Duration
- 2h 28m
- 2 hours 28 minutes
- Impact
- Minor
- as rated by Supabase
- Updates
- 4
- posted by Supabase
Timeline
All times UTC.
Official incident from Supabase
Increased Errors with Project Lifecycle Operations in US-West-2
-
Official
Identified
All Project Lifecycle operations are currently impacted by an upstream provider incident affecting EC2 instances in US-West-2. Currently up and active projects are unaffected and remain healthy. New project creation, unpauses, restore actions, project size changes, restarts and other lifecycle operations may encounter errors. We advise against taking these actions in US-West-2 at this time while we work with our provider to resolve this issue.
-
Official
Identified
We continue to work with our upstream provider as they investigate the ongoing incident affecting US-West-2. There are no additional updates at this time, and Project Lifecycle operations remain impacted. Currently active projects remain unaffected. We will provide another update in 2 hours, or sooner if additional information becomes available.
-
Official
Monitoring
Our upstream provider has implemented changes, and we are seeing recovery in project creation in US-West-2. We will continue to monitor the recovery of Project Lifecycle operations to ensure stability.
-
Official
Resolved
The upstream provider incident has been resolved, and Project Lifecycle operations in US-West-2 have recovered. All operations are functioning normally, and we are marking this incident as resolved.
"Official" rows are quoted from Supabase's public status page, status.supabase.com. Very long posts are shortened.
What our checkpoints saw
HostTracker's checkpoints, which test supabase.com from several locations, recorded no outage of 5 minutes or longer during this incident. A provider can report a problem that affects only some features, regions or accounts, which a check of the main address does not see. The live Supabase status shows what our checks see right now.
Does your product depend on Supabase?
An outage like this one reaches your users through your product, and most teams hear about it from a customer rather than from a dashboard. HostTracker watches any endpoint you name - your own site, an API you call, a vendor you resell - from 300+ locations, confirms a failure from several of them before it says anything, and then tells you by email, SMS, voice call or your chat tool.
You get the same record you are reading here for your own services: every outage timestamped, with the checks that observed it.
Independent measurement by HostTracker. Not affiliated with Supabase. Official updates are quoted from Supabase's public status page and remain Supabase's own words.