AWS status history
28 incidents over the last year, newest first; 100.00% uptime (90 days), 100.00% uptime (since Jan 28). History from before down.guide started reading the page is imported from AWS's own archive.
2026-03
3 incidents
- Multiple services (Bahrain): Region Availability
The provider says it is unable to restore access to resources and data hosted exclusively in the Middle East (Bahrain) Region (me-south-1), where damage spanned multiple Availability Zones. It will share a further update in early 2027.
- Multiple services (UAE): Region Availability
AWS says it cannot restore access to resources and data hosted exclusively in mec1-az2 in the ME-CENTRAL-1 (UAE) Region. It continues recovering regional resources and zonal resources in mec1-az1 and mec1-az3. Most customers have moved to other Regions.
- AWSPartial outageS3 (eu-central-2): Increased Error Rates
2026-11
1 incident
- Amazon Elastic Compute Cloud (Oregon): Elevated Launch Failures
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.
2026-10
2 incidents
2026-09
2 incidents
2026-08
3 incidents
2026-07
6 incidents
- AWSDegradedDIRECTCONNECT (ap-south-1): Elevated Packet Loss
- MULTIPLESERVICES (us-west-2): Connectivity Issues
- AWSDegradedBILLINGCONSOLE (global): Inaccurate Estimated Billing Data
- AWSDegradedCLOUDFRONT (global): Increased 5xx Errors
- AWSPartial outageMULTIPLESERVICES (eu-central-1): Elevated connectivity issues with a single Avalability zone
- AWSDegradedEC2 (us-east-1): Increased Launch Template API Error Rates
2026-06
3 incidents
2026-05
2 incidents
2026-04
1 incident
- AWSPartial outageEC2 (eu-west-3): Increased Connectivity Issues
2026-02
4 incidents
2026-01
1 incident
Keep reading
AWS's live status, comparisons with similar providers and the site-wide rankings.