Service impact: Increased Error Rates

ResolvedmajorUnverified reportFirst recorded update Aug 19, 2026, 05:03 PM · Resolved Aug 20, 2026, 06:40 PM

On August 18 we launched a new Availability Zone (euw2-az4) in the EU-WEST-2 Region. After the launch, we began experiencing errors launching EC2 instances in the new Availability Zone when a default subnet is not present. We can confirm that existing running instances and resources are not affected. Workflows that automatically get a list of Availability Zones in the Region via the DescribeAvailabilityZones API and then attempt to launch new instances or create resources in the new Availability Zone may encounter errors. For EC2 instance launch failures, we are taking mitigating steps to...

What visitors reported during this incident

No visitor reports were filed for this incident.

Having problems with Amazon Web Services now? Check the current status

Timeline

No vendor updates were captured for this incident before it was resolved.

What to do next

Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
Watch the provider going forward. Follow Amazon Web Services's status feed →

GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.