AWS Outage History
33 incidents recorded over the last 365 days, 30 of them resolved, 3 still open. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded AWS Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Aug 21, 2026 | Amazon Connect Issue in ap-northeast-1Increased Error Rates | 37 min | Resolved |
| Aug 19, 2026 | Amazon Elastic Compute Cloud Issue in eu-west-2Increased Error Rates | 3h 32m | Resolved |
| Aug 15, 2026 | AWS Direct Connect Issue in eu-central-1Increased Packet loss | 72h 18m | Resolved |
| Jul 31, 2026 | AWS Service Issue in ap-south-1Elevated Packet Loss | 1h 21m | Resolved |
| Jul 24, 2026 | AWS Service Issue in us-west-2Connectivity Issues | 1h 21m | Resolved |
| Jul 17, 2026 | AWS Service IssueInaccurate Estimated Billing Data | 29h 24m | Resolved |
| Jul 16, 2026 | AWS Service IssueIncreased 5xx Errors | 3h 37m | Resolved |
| Jul 15, 2026 | AWS Service Issue in eu-central-1Elevated connectivity issues with a single Avalability zone | 2h 13m | Resolved |
| Jul 6, 2026 | AWS Service Issue in us-east-1Increased Launch Template API Error Rates | 2h 7m | Resolved |
| Jun 30, 2026 | AWS Service Issue in eu-north-1Increased Error Rates and Latencies | 51 min | Resolved |
| Jun 13, 2026 | AWS Service Issue in us-east-1Fable 5 and Mythos 5 Access | 64h 46m | Resolved |
| Jun 6, 2026 | AWS Service Issue in sa-east-1Internet Connectivity Issues | 0 min | Resolved |
| May 22, 2026 | AWS Service IssueWe are investigating increased error rates for Route53 API calls | — | Investigating |
| May 22, 2026 | AWS Service IssueIncreased API Error Rates | 34 min | Resolved |
| May 8, 2026 | AWS Service Issue in us-east-1Increased Error Rate and Latency | 26h 38m | Resolved |
| Apr 27, 2026 | AWS Service Issue in eu-west-3Increased Connectivity Issues | 38 min | Resolved |
| Mar 7, 2026 | AWS Service Issue in eu-central-2Increased Error Rates | 1h 10m | Resolved |
| Mar 2, 2026 | AWS Service Issue in me-south-1Increased Error Rates | — | Investigating |
| Mar 1, 2026 | AWS Service Issue in me-central-1Increased Error Rates | — | Investigating |
| Feb 25, 2026 | AWS Service Issue in us-east-1Intermittent missing or delayed EC2 instance and status check metrics | 2h 37m | Resolved |
| Feb 21, 2026 | AWS Service Issue in us-east-1AWS Direct Connect Connectivity Issues | 1h 35m | Resolved |
| Feb 10, 2026 | AWS Service IssueChange Propagation Delays | 7h 3m | Resolved |
| Feb 7, 2026 | AWS Service Issue in sa-east-1Network Connectivity | 0 min | Resolved |
| Jan 28, 2026 | AWS Service Issue in eu-west-1Elevated latencies for network change propagation | 2h 8m | Resolved |
| Oct 28, 2025 | AWS Service Issue in us-east-1Increased Error Rates and Latencies | 7h 20m | Resolved |
| Oct 20, 2025 | AWS Service Issue in us-east-1Increased Error Rates and Latencies | 15h 42m | Resolved |
| Sep 27, 2025 | AWS Service IssueIncreased Error Rates and Latencies | 32 min | Resolved |
| Sep 25, 2025 | AWS Service Issue in eu-north-1SQS Increased API Error Rates | 7h 28m | Resolved |
| Sep 16, 2025 | AWS Service Issue in us-east-1Increased error rates | 40 min | Resolved |
| Sep 11, 2025 | AWS Service Issue in us-east-1Increased API Error Rates | 30 min | Resolved |
| Sep 8, 2025 | AWS Service IssueManagement Console Error Rates | 1h 4m | Resolved |
| Aug 27, 2025 | AWS Service IssueIncreased error rates and latency | 14 min | Resolved |
| Aug 26, 2025 | AWS Service Issue in ap-southeast-2Increased sign-in errors | 52 min | Resolved |
How to Read This AWS Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before AWS acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single AWS outage in this window ran 3d, against a mean recovery of 8h 38m. If you depend on AWS in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.