Live / Amazon Web Services / Incident
Amazon Web Services: [RESOLVED] Elevated Launch Failures — Oregon
Amazon Web Services · aws.amazon.comResolved2026-11-07 01:12 UTC
Public — what happened
Summary
Amazon Web Services said that new EC2 virtual server launches were failing across all availability zones in its US-WEST-2 (Oregon) Region, starting at 22:51 UTC on November 6. The company said the problem came from a subsystem supporting EBS storage volumes that are needed when a server starts, and that services such as DataSync and AWS Backup, which need new instances, were also affected. It said servers already running and existing volumes kept working normally. AWS reported it began fixing the issue at 3:20 PM PST, finished full recovery at 4:21 PM, and advised customers to retry any requests that failed.
Timeline
- Started — 2026-11-06 22:51 UTC
- Investigating — 2026-11-06 22:51 UTC (3 updates)
- Update — 2026-11-07 01:12 UTC
- Resolved — 2026-11-07 01:12 UTC · 2h 21m after it started
What SquidGrid measured
SquidGrid measured 49 internet paths into Amazon Web Services’s network during this incident. None of them ran meaningfully slower than the same paths the day before.
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Amazon Web Services 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 Amazon Web Services: paths off baseline right now, where on the route conditions change, and its full incident track record.
Included with any paid plan.
Open the Amazon Web Services report →
More from Amazon Web Services
Covered in The Squid’s Ink, Week 46, 2026, our weekly internet health report.