AWS EC2 launch failures in Oregon (US-WEST-2), November 6, 2026

Amazon Web Services reported elevated launch failures for Amazon EC2 in the US-WEST-2 Region (Oregon) on November 6, 2026, beginning at 10:51 PM UTC (5:51 PM Eastern / 2:51 PM Pacific). In its 11:19 PM UTC update (6:19 PM Eastern / 3:19 PM Pacific), AWS said the failures are caused by an issue with the EBS service, and that services that depend on EBS or EC2 will experience failure rates of their own. In its 12:08 AM UTC update on November 7, 2026 (7:08 PM Eastern / 4:08 PM Pacific, November 6), AWS confirmed the launch failures affect all Availability Zones in the region (usw2-az1, usw2-az2, usw2-az3 and usw2-az4), identified the cause as a subsystem that supports EBS volumes required during instance launch, said services that instantiate new instances, such as cross-region data copy for DataSync with US-WEST-2 as source or destination, are also affected, advised customers not to mutate running instances in a way that would replace or create a new EC2 instance in the region, said running EC2 instances and already created EBS volumes continue to operate normally, and reported early signs of recovery. In its final update, posted at 1:12 AM UTC on November 7, 2026 (8:12 PM Eastern / 5:12 PM Pacific, November 6), AWS said the issue has been resolved and all AWS services are now operating normally: between 2:35 PM and 4:21 PM Pacific, EC2 instance launches in all Availability Zones in US-WEST-2 were affected, along with AWS services that instantiated new instances and services such as DataSync or AWS Backup which require new instances to support data transfers to or from US-WEST-2; remediation of the EBS-volume subsystem issue began at 3:20 PM Pacific, and full recovery was completed at 4:21 PM Pacific (7:21 PM Eastern). AWS recommended customers retry requests that failed during this time.

Timeline: AWS status record, as mirrored by Pingoru and PulsAPI from AWS's official status feed — first entry at 10:51 PM UTC, November 6, 2026 (5:51 PM Eastern / 2:51 PM Pacific), "We are experiencing elevated launch failures in the US-WEST-2 Region," status Monitoring; update at 11:19 PM UTC (6:19 PM Eastern / 3:19 PM Pacific) identifying the EBS service as the cause and warning that EBS- and EC2-dependent services will experience failure rates of their own; update at 12:08 AM UTC, November 7, 2026 (7:08 PM Eastern / 4:08 PM Pacific, November 6) confirming impact across all four Availability Zones in US-WEST-2, refining the cause to a subsystem that supports EBS volumes required during instance launch, naming DataSync cross-region data copy as an affected example, and reporting early signs of recovery; final entry at 1:12 AM UTC, November 7, 2026 (8:12 PM Eastern / 5:12 PM Pacific, November 6), status Resolved, stating full recovery was completed at 4:21 PM Pacific (7:21 PM Eastern) and all AWS services are now operating normally. The incident record duration is shown as 2 hours 21 minutes by both mirrors (first status entry to the resolution post); AWS's own stated impact window in its final entry is 2:35 PM to 4:21 PM Pacific (5:35 PM to 7:21 PM Eastern).

Affected services and scope: Amazon Elastic Compute Cloud in Oregon (US-WEST-2), all Availability Zones (usw2-az1, usw2-az2, usw2-az3, usw2-az4), and the EBS subsystem that supports volumes required during instance launch. Services that instantiate new instances in the region were also affected, including cross-region data copy for DataSync and AWS Backup transfers to or from US-WEST-2. Independent confirmation of material downstream impact: Databricks, on its own status page for Databricks on AWS, reported incident ES-2342108 starting at 10:42 PM UTC (5:42 PM Eastern / 2:42 PM Pacific), stating that customers using Databricks on AWS in US West 2 may experience degraded availability with Classic Compute, Databricks SQL, Declarative Pipelines, and Jobs, including cluster launch failures, delayed or failed SQL warehouse startups, and failures or delays in job and pipeline runs, and that the issue is under investigation in coordination with the cloud provider. No other AWS region was named in AWS's account.

Provider's account: AWS said the elevated EC2 launch failures in US-WEST-2 were caused by a subsystem that supports EBS volumes required during instance launch, that dependent services experienced failure rates of their own, that remediation began at 3:20 PM Pacific, and that full recovery was completed at 4:21 PM Pacific. Running EC2 instances and already created EBS volumes were not impacted and continued to operate as normal, per AWS. No compensation has been stated.

Status: Restored November 6, 2026. Full recovery completed at 4:21 PM Pacific / 7:21 PM Eastern, per AWS's final update posted at 1:12 AM UTC, November 7, 2026 (8:12 PM Eastern, November 6), and verified at 8:53 PM Eastern, November 6, 2026.

Sources: AWS incident via Pingoru, mirroring AWS official status, AWS status summary via PulsAPI, checked 7 November 2026, 01:52 UTC, Databricks AWS incident ES-2342108 via Pingoru