Amazon EC2 is the virtual-server backbone of AWS - when EC2 has problems in a region, almost everything built on top of it (including managed services) can wobble. EC2 incidents usually show up as failed instance launches, unreachable instances in one Availability Zone, or API errors, rather than everything going dark at once.
Instance launch failures in a single Availability Zone (capacity or control-plane issues)
Network connectivity impairment for instances in one AZ
Elevated EC2 API error rates (RunInstances, DescribeInstances) while running instances stay up
EBS volume degradation making instances slow rather than down
Recent Amazon EC2 incidents
Instance launch failures in a single Availability Zone (eu-west-1)
July 1, 2026 · 3h
New instance launches failed in one eu-west-1 Availability Zone for ~3 hours; running instances were unaffected.
The live status at the top of this page reflects our latest check of EC2 health, updated continuously. If it shows Operational, current problems are more likely in your specific AZ, your networking, or a dependent service.
Why is my EC2 instance down when AWS says EC2 is fine?+
AWS status reflects regional service health. A single-AZ event, an exhausted instance type, your security groups, or an EBS issue can take your instance out while the region as a whole stays green.
Does an EC2 outage qualify for an SLA credit?+
If region-level monthly uptime falls below 99.99%, the EC2 SLA pays a 10–100% credit on affected spend - but only if you file a claim within about 60 days.
Get alerted when Amazon EC2 breaks
Instant email the moment we detect an incident - affected services and regions included.
aws