- Level
- confirmed
- Worst impact
- Partial outage
- Components
- EC2
- Regions
- eu-west-3
- Down Index
- 56of 100
What to do
Check whether you use AWS EC2 in eu-west-3. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 39m it lasted.
Anything that failed between 2026-04-27 11:27 UTC and 2026-04-27 12:05 UTC may need a replay.Subscribe to AWS's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=aws works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from AWS 2
- investigating
We are investigating instance connectivity issues in a single Availability Zone (euw3-az2) in the EU-WEST-3 Region.
provider
- investigating
Between 3:58 AM and 4:40 AM PDT, we experienced increased error rates and increased launch failures for EC2 instances in a single Availability Zone (euw3-az2) in the EU-WEST-3 Region. During this time, customers attempting to launch new EC2 instances in the affected Availability Zone would have experienced launch failures. Additionally, a subset of existing EC2 instances and EBS volumes in this Availability Zone were impacted and became unreachable. We have identified the root cause to be a loss of power to infrastructure within the affected Availability Zone. Engineers were engaged at 4:02 AM and immediately began working to restore power and assess the scope of impact. By 4:20 AM, power was successfully restored to the affected infrastructure. We then focused our efforts on recovering impacted EC2 instances and EBS volumes. By 4:40 AM, all impacted EC2 instances and EBS volumes had been fully recovered and were operating normally. No additional action is required for EC2 instances and EBS volumes that were impacted during the power loss event, as these have been fully recovered. While EC2 and EBS have recovered, some AWS services may take additional time to fully recover as they process backlogs and complete their own recovery procedures. The issue has been resolved and the service is operating normally.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-a34e95e2a6
Is AWS still down?
No, this incident was resolved 2026-04-27 12:05 UTC. For AWS's live state, see https://down.guide/aws.
How long did it last?
39m, from 2026-04-27 11:27 UTC to 2026-04-27 12:05 UTC, by the times AWS posted.
What was affected?
AWS named EC2 in eu-west-3.
What caused it?
AWS hasn't published a root cause. If it does, it shows here.
Where does this come from?
AWS's official status page, https://health.aws.amazon.com/health/status, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.