CompaniesAmazon Web ServicesIncidents
Amazon Web Services: Elevated Launch Failures (us-west-2)
Affected components: Amazon Managed Workflows for Apache AirflowAmazon WorkSpaces ApplicationsAWS BackupAWS BatchBedrock AgentCoreAWS CloudShellAmazon CloudWatchAWS CodeBuildAWS CodePipelineAWS DataSyncAWS Device FarmAmazon DocumentDBAmazon Elastic Container ServiceAWS Elastic BeanstalkAmazon Elastic Load BalancingAWS ElementalAmazon EMR ServerlessAmazon Elastic MapReduceAmazon EventBridgeAWS FargateAmazon GameLift StreamsAmazon GameLift ServersAWS GlueAWS HealthImagingAmazon MQAWS HealthOmicsAWS Parallel Computing ServiceAmazon Relational Database ServiceAmazon SageMakerAWS Step FunctionsVM Import/ExportAmazon WorkSpaces
Timeline of updates
- updateEdited
We are experiencing elevated launch failures in the US-WEST-2 Region.
- update
We are experiencing elevated launch failures in the US-WEST-2 Region caused by an issue with the EBS service. Services that depend on EBS or EC2 will experience failure rates of their own. We are working to mitigate the issues. We will provide you with another update by 4:00 PM PST or sooner if new information becomes available.
- update
We can confirm EC2 instance launch failures affecting all AZs (usw2-az1, usw2-az2, usw2-az3, usw2-az4) in the US-WEST-2 Region. We have identified the issue to be caused by a subsystem that supports EBS Volumes required during instance launch. Services that instantiate new instances, such as cross-region data copy for DataSync, within the US-WEST-2 Region as either the source or destination are also affected. We recommend that customers do not mutate running instances at this time that would result in the replacement or creation of a new EC2 instance in the Region. Running EC2 instances and already created EBS volumes continue to operate as normal.
We are seeing early signs of recovery, and continue to take steps to restore launches within the Region. We will update this post by 5:30 PM PST or earlier if we have new information to share.
- resolved
Between 2:35 PM and 4:21 PM PST, we experienced elevated EC2 instance launch failures affecting all AZs (usw2-az1, usw2-az2, usw2-az3, usw2-az4) in the US-WEST-2 Region. EC2 Instance Launches, AWS services that instantiated new instances, as well as services such as DataSync or AWS Backup which require new instances to support data transfers to or from the US-WEST-2 Region were affected. Our engineers were automatically engaged and immediately began investigating the root cause. We identified the issue to be caused by a subsystem that supports EBS Volumes required during instance launch. We began remediation of that issue at 3:20 PM, and completed full recovery at 4:21 PM. We recommend customers retry requests that failed during this time. Running EC2 instances and already created EBS volumes were not impacted and continued to operate as normal. The issue has been resolved and all AWS services are now operating normally.
Changes Rewindex caught on this incident
- Incident silently edited: Elevated Launch Failures (us-west-2)
- Incident updated: Elevated Launch Failures (us-west-2)
- Incident updated: Elevated Launch Failures (us-west-2)
- Incident updated: Elevated Launch Failures (us-west-2)
- Incident updated: Elevated Launch Failures (us-west-2)
- Incident updated: Elevated Launch Failures (us-west-2)
- Incident updated: Elevated Launch Failures (us-west-2)
- Incident updated: Elevated Launch Failures (us-west-2)
- Incident updated: Elevated Launch Failures (us-west-2)
- Incident updated: Elevated Launch Failures (us-west-2)
- Incident updated: Elevated Launch Failures (us-west-2)
- Incident updated: Elevated Launch Failures (us-west-2)
- Incident updated: Elevated Launch Failures (us-west-2)
- Incident updated: Elevated Launch Failures (us-west-2)
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-11-06 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
bddea5e2e5bc9b19…Version 2 captured
In the 2026-11-06 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
df31f5106a0779e3…Version 3 captured
In the 2026-11-06 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
0163323c825de19a…Version 4 captured
In the 2026-11-06 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
1f1cba35449c8db9…Version 5 captured
In the 2026-11-06 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
a50c3db4713a5ef4…Version 6 captured
In the 2026-11-06 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
c2c2558b6eb53190…Version 7 captured
In the 2026-11-06 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
c7e6601a55425b73…
Rewindex captured a newer version after the last checkpoint; the next run () commits it.
Impact, status and times are the vendor’s own, as last archived. View on health.aws.amazon.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Amazon Web Services, started 2026-11-06 22:51 UTC, resolved after 2.4 h, 4 update(s); edited after publishing.
- Title
- Elevated Launch Failures (us-west-2)
- Vendor
- Amazon Web Services
- Date
- URL
- https://rewindex.com/company/aws/incidents/us-west-2-aws_ec2_operational_issue_62978_c9c1126888d
Amazon Web Services profileRecent Amazon Web Services incidentsAll outages on November 6, 2026Amazon Web Services in November 2026MarkdownJSON