Skip to main content
awsdown

Is Amazon EC2 down?

DegradedLast checked Oct 13, 2026, 4:24 PM UTC

Last 90 days

99.947% uptime · 2 incidents
2026-07-16: operational2026-07-17: operational2026-07-18: operational2026-07-19: operational2026-07-20: operational2026-07-21: operational2026-07-22: operational2026-07-23: operational2026-07-24: operational2026-07-25: operational2026-07-26: operational2026-07-27: operational2026-07-28: operational2026-07-29: operational2026-07-30: operational2026-07-31: operational2026-08-01: operational2026-08-02: operational2026-08-03: operational2026-08-04: operational2026-08-05: operational2026-08-06: operational2026-08-07: operational2026-08-08: operational2026-08-09: operational2026-08-10: operational2026-08-11: operational2026-08-12: operational2026-08-13: operational2026-08-14: operational2026-08-15: operational2026-08-16: operational2026-08-17: operational2026-08-18: operational2026-08-19: degraded2026-08-20: operational2026-08-21: operational2026-08-22: operational2026-08-23: operational2026-08-24: operational2026-08-25: operational2026-08-26: operational2026-08-27: operational2026-08-28: operational2026-08-29: operational2026-08-30: operational2026-08-31: operational2026-09-01: operational2026-09-02: operational2026-09-03: operational2026-09-04: operational2026-09-05: operational2026-09-06: operational2026-09-07: operational2026-09-08: operational2026-09-09: operational2026-09-10: operational2026-09-11: operational2026-09-12: operational2026-09-13: operational2026-09-14: operational2026-09-15: operational2026-09-16: operational2026-09-17: operational2026-09-18: operational2026-09-19: operational2026-09-20: operational2026-09-21: degraded2026-09-22: degraded2026-09-23: operational2026-09-24: operational2026-09-25: operational2026-09-26: operational2026-09-27: operational2026-09-28: operational2026-09-29: operational2026-09-30: operational2026-10-01: operational2026-10-02: operational2026-10-03: operational2026-10-04: operational2026-10-05: operational2026-10-06: operational2026-10-07: operational2026-10-08: operational2026-10-09: operational2026-10-10: operational2026-10-11: operational2026-10-12: operational2026-10-13: operational
2026-07-162026-10-13

What Amazon EC2 does - and how it fails

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

  • [RESOLVED] Increased Error Rates

    September 21, 2026 · 58m

    Between 3:49 PM and 5:06 PM PDT, we experienced increased error rates affecting new instance launches in the US-EAST-1 Region. During this time, customers may have experienced elevated error rates when attempting to launch new EC2 instances through RunInstances, CreateFleet, and related EC2 launch workflows. AWS services that launch EC2 instances on behalf of customers, including Amazon ECS, AWS Fargate, Amazon EMR, amongst others were also impacted during this period. We identified the root cause as a recent deployment to a subsystem within the EC2 service responsible for processing instance launch requests. We initiated a rollback of the problematic deployment and began observing initial signs of recovery at 4:44 PM. Existing instances remain unaffected. The issue has been resolved and the service is operating normally.

  • [RESOLVED] Increased Error Rates

    August 19, 2026 · 3h 32m

    Between August 18 5:00 PM and August 19 11:00 AM PDT, we experienced elevated errors launching EC2 instances in a newly launched Availability Zone (euw2-az4) in the EU-WEST-2 Region. After the new Availability Zone launch, we began experiencing errors when using a default VPC. We discovered the root cause of the issue on August 19 at 9:00 AM and began deploying a change to resolve the issue at 9:30 AM. While the change was underway, we began to see incremental improvements in new instance launches, with full recovery at 11:00 AM. Existing running instances and resources were not affected. Some regional services, such as Lambda functions or Aurora databases, were not available at the launch of the new Availability Zone and service availability will be added over time. Customers attempting to create resources before the services become available will see a message reporting that it is not supported in the Availability Zone. The issue has been resolved and the service is operating normally.

Full analyses live in the post-mortem archive.

Amazon EC2 questions

Is EC2 down right now?

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.

Get outage alerts