AWS Outage History

29 incidents recorded over the last 365 days, 26 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.

Live AWS status100.00% uptime history

Every Recorded AWS Incident

AWS incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 4, 2026AWS Internet Connectivity Issue in eu-south-2Elevated packet loss2h 41mResolved
Sep 21, 2026Amazon Elastic Compute Cloud Issue in us-east-1Increased Error Rates57 minResolved
Sep 3, 2026Multiple services Issue in us-west-2Increased API Error Rates2h 17mResolved
Aug 21, 2026Amazon Connect Issue in ap-northeast-1Increased Error Rates37 minResolved
Aug 19, 2026Amazon Elastic Compute Cloud Issue in eu-west-2Increased Error Rates3h 32mResolved
Aug 15, 2026AWS Direct Connect Issue in eu-central-1Increased Packet loss72h 18mResolved
Jul 31, 2026AWS Service Issue in ap-south-1Elevated Packet Loss1h 21mResolved
Jul 24, 2026AWS Service Issue in us-west-2Connectivity Issues1h 21mResolved
Jul 17, 2026AWS Service IssueInaccurate Estimated Billing Data29h 24mResolved
Jul 16, 2026AWS Service IssueIncreased 5xx Errors3h 37mResolved
Jul 15, 2026AWS Service Issue in eu-central-1Elevated connectivity issues with a single Avalability zone2h 13mResolved
Jul 6, 2026AWS Service Issue in us-east-1Increased Launch Template API Error Rates2h 7mResolved
Jun 30, 2026AWS Service Issue in eu-north-1Increased Error Rates and Latencies51 minResolved
Jun 13, 2026AWS Service Issue in us-east-1Fable 5 and Mythos 5 Access64h 46mResolved
Jun 6, 2026AWS Service Issue in sa-east-1Internet Connectivity Issues0 minResolved
May 22, 2026AWS Service IssueWe are investigating increased error rates for Route53 API calls—Investigating
May 22, 2026AWS Service IssueIncreased API Error Rates34 minResolved
May 8, 2026AWS Service Issue in us-east-1Increased Error Rate and Latency26h 38mResolved
Apr 27, 2026AWS Service Issue in eu-west-3Increased Connectivity Issues38 minResolved
Mar 7, 2026AWS Service Issue in eu-central-2Increased Error Rates1h 10mResolved
Mar 2, 2026AWS Service Issue in me-south-1Region Availability—Investigating
Mar 1, 2026AWS Service Issue in me-central-1Region Availability—Investigating
Feb 25, 2026AWS Service Issue in us-east-1Intermittent missing or delayed EC2 instance and status check metrics2h 37mResolved
Feb 21, 2026AWS Service Issue in us-east-1AWS Direct Connect Connectivity Issues1h 35mResolved
Feb 10, 2026AWS Service IssueChange Propagation Delays7h 3mResolved
Feb 7, 2026AWS Service Issue in sa-east-1Network Connectivity0 minResolved
Jan 28, 2026AWS Service Issue in eu-west-1Elevated latencies for network change propagation2h 8mResolved
Oct 28, 2025AWS Service Issue in us-east-1Increased Error Rates and Latencies7h 20mResolved
Oct 20, 2025AWS Service Issue in us-east-1Increased Error Rates and Latencies15h 42mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next AWS incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

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 9h 45m. 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.