# Amazon Elastic Compute Cloud (Oregon): Elevated Launch Failures - Provider: [AWS](https://down.guide/providers/aws) - Confidence: Confirmed - Impact: Degraded - lasted 2h 21m - started 2026-11-06 22:51 UTC - Amazon Elastic Compute Cloud - us-west-2 - AWS states the impact was 2026-11-06 22:35 UTC to 2026-11-07 00:21 UTC (1h 46m) - id: DWN-89ef96e280 - Official page: https://health.aws.amazon.com/health/status - Part of: [aws-2026-11-06](https://down.guide/cascades/aws-2026-11-06) ## Summary The provider says EC2 instance launch failures affected all AZs in US-WEST-2 from 2:35 PM to 4:21 PM PST, caused by a subsystem supporting EBS Volumes. The issue is resolved, running instances were not impacted, and retrying failed requests is recommended. _Written by anthropic/claude-haiku-5.5 from AWS's own updates._ ## Updates from AWS ### 2026-11-06 22:51 UTC: investigating We are experiencing elevated launch failures in the US-WEST-2 Region. ### 2026-11-06 23:19 UTC: investigating 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. ### 2026-11-07 00:08 UTC: investigating 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. ### 2026-11-07 01:12 UTC: 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. From the builder: does your app depend on AWS? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=aws) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention AWS. --- down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-89ef96e280), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.