- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us, us-west-2
- Cascade
- aws-2026-11-06
Summary
Supabase says Project Lifecycle operations in US-West-2 (new project creation, unpauses, restores, project size changes, restarts) were impacted by an upstream provider incident affecting EC2 instances; active projects were unaffected. The incident is now resolved and operations have recovered.
Written by anthropic/claude-haiku-5.5 from Supabase's own updates.
What to do
Check whether you use Supabase in us, us-west-2. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 2h 28m it lasted.
Anything that failed between 2026-11-06 23:49 UTC and 2026-11-07 02:17 UTC may need a replay.Subscribe to Supabase's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=supabase works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Supabase 4
- 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.
provider
- 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.
provider
- 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.
provider
- 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.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-7f735185e0
Is Supabase still down?
No, this incident was resolved 2026-11-07 02:17 UTC. For Supabase's live state, see https://down.guide/providers/supabase.
How long did it last?
2h 28m, from 2026-11-06 23:49 UTC to 2026-11-07 02:17 UTC, by the times Supabase posted.
What was affected?
Supabase named in us, us-west-2.
What caused it?
Supabase hasn't published a root cause. If it does, it shows here.
Where does this come from?
Supabase's official status page, https://status.supabase.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.