AWS Outage History
Uptime record, past incidents, and downtime history for AWS.
Checking current status...
90-Day Trend
Monthly Uptime
| Month | Uptime | Days Tracked | Days with Issues |
|---|---|---|---|
| May 2026 | 76% | 25 | 6 |
| April 2026 | 93.3% | 30 | 2 |
| March 2026 | 83.9% | 31 | 5 |
| February 2026 | 80% | 5 | 1 |
Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.
Daily Status (Last 91 Days)
Feb 24
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
May 2026
Service is operating normally: [RESOLVED] Increased API Error Rates
Started: May 23, 12:13 AM
resolved
Between 4:00 PM and 4:46 PM, we experienced increased error rates for the Route53 APIs. This issue did not impact resolution of existing DNS records. Engineers were automatically engaged and immediately began investigating the issue. During this time, customers may have received 500s for Route53 APIs and the Route53 Management Console. We have identified the root cause and have mitigated this issue. Other AWS Services that call the Route53 APIs in their workflows may also have been impacted d...
May 23, 12:13 AM
Service impact: We are investigating increased error rates for Route53 API calls
Started: May 22, 11:39 PM
investigating
We are investigating increased error rates for Route53 API calls.
May 22, 11:39 PM
Service impact: Increased API Error Rates
Started: May 22, 11:38 PM
investigating
We are investigating increased error rates for Route53 API calls.
May 22, 11:38 PM
Service is operating normally: [RESOLVED] Increased Error Rate and Latency
Started: May 9, 3:04 AM
resolved
Starting May 7 4:20 PM PDT, we experienced increased impaired EC2 instances and degraded EBS volumes in a single facility (data center) within a single Availability Zone (use1-az4) in the US-EAST-1 Region. The issue was caused by a thermal event resulting in a loss of power. As part of our recovery effort, we shifted traffic away from the impacted Availability Zone for most services at May 7 5:06 PM.
AWS services, like Elastic Load Balancing, Elastic Kubernetes Service, ElastiCache, Redshift...
May 9, 3:04 AM
Service impact: Increased Error Rate and Latency
Started: May 8, 11:00 PM
investigating
We have begun to see improvements in the overall number of affected EC2 instances and degraded EBS volumes in a single Availability Zone (use1-az4) in the US-EAST-1 Region. The steps taken to supply additional cooling capacity have been showing steady signs of progress. Some EBS Volumes and EC2 instances affected by the issue will continue to experience impairments while we continue to drive these efforts. We continue to recommend that customers who require immediate recovery restore from EBS...
May 8, 11:00 PM
Service impact: Increased Error Rate and Latency
Started: May 8, 7:29 PM
investigating
We continue to work towards the recovery of the impaired EC2 instances and degraded EBS volumes in a single Availability Zone (use1-az4) in the US-EAST-1 Region though efforts are slower than we had previously anticipated. We are taking measured steps to ensure that cooling capacity is brought online in a safe and controlled manner. As a result, EBS Volumes and EC2 instances affected by the issue will continue to experience impairments. We continue to recommend that customers who require imme...
May 8, 7:29 PM
Service impact: Increased Error Rate and Latency
Started: May 8, 6:12 PM
investigating
We are experiencing an increase in timeouts to Amazon Managed Streaming for Apache Kafka partitions on a subset of clusters as a result of the ongoing issue in a single Availability Zone (use1-az4) in the US-EAST-1 Region. We are working in parallel to determine a path towards mitigation for affected clusters. We will provide an additional update by 12:30 PM or sooner.
May 8, 6:12 PM
Service impact: Increased Error Rate and Latency
Started: May 8, 4:30 PM
investigating
We have observed complete recovery of increased error rates and query failures for Redshift clusters in the US-EAST-1 Region. We were able to resolve the impact independently of the ongoing efforts to recover the affected hardware in the use1-az4 Availability Zone. The issue affecting Redshift has been resolved and the service is operating normally. We will provide an additional update regarding the efforts towards hardware restoration by 12:30 PM or sooner.
May 8, 4:30 PM
Service impact: Increased Error Rate and Latency
Started: May 8, 3:58 PM
investigating
We continue our efforts to work towards the recovery of the impaired EC2 instances and degraded EBS volumes in a single Availability Zone (use1-az4) in the US-EAST-1 Region. We are making progress towards the restoration of the cooling system capacity that is required to recover the affected hardware in the impacted zone. Some customers will continue to see their affected EC2 instances and EBS volumes as impaired until the affected racks are recovered. We continue to recommend that customers ...
May 8, 3:58 PM
Service impact: Increased Error Rate and Latency
Started: May 8, 1:51 PM
investigating
We continue working to resolve the impaired EC2 instances and degraded EBS volumes in a single Availability Zone (use1-az4) in the US-EAST-1 Region caused by a thermal event. During such an event, servers automatically shut down when the temperatures exceeded the operating thresholds in order to protect the hardware. We are actively working to bring additional cooling system capacity online, which will enable us to recover the remaining affected hardware in the impacted zone. Some customers w...
May 8, 1:51 PM
Service impact: Increased Error Rate and Latency
Started: May 8, 10:54 AM
investigating
We continue to make progress towards resolving the impaired EC2 instances and degraded EBS volumes in a single Availability Zone (use1-az4) in the US-EAST-1 Region. At this time, we wanted to provide some more details on the issue. Beginning on May 7 at 4:20 PM PDT, we began experiencing an increase in instance impairments within the affected zone due to the loss of power during a thermal event. Engineers were automatically engaged within minutes and immediately began investigating multiple m...
May 8, 10:54 AM
Service impact: Increased Error Rate and Latency
Started: May 8, 8:32 AM
investigating
Mitigation efforts remain underway to resolve the impaired EC2 instances and degraded EBS volumes in a single Availability Zone (use1-az4) in the US-EAST-1 Region. These EC2 instances and EBS volumes were impacted due to a loss of power during the thermal event. The work to bring additional cooling system capacity online, which will enable us to recover the remaining affected infrastructure in a controlled and safe manner, is taking longer than we had initially anticipated. Some services, suc...
May 8, 8:32 AM
Service impact: Increased Error Rate and Latency
Started: May 8, 6:38 AM
investigating
We continue to make progress in resolving the impaired EC2 instances in the affected Availability Zone (use1-az4) in the US-EAST-1 Region, and are working towards full recovery. We are actively working to bring additional cooling system capacity online, which will enable us to recover the remaining affected racks in a controlled and safe manner. In the impacted Availability Zone, EC2 Instances, EBS Volumes, and other AWS Services may continue to experience elevated error rates and latencies ...
May 8, 6:38 AM
Service impact: Increased Error Rate and Latency
Started: May 8, 5:11 AM
investigating
We are observing early signs of recovery. We continue to work towards restoring temperatures to normal levels and bring impacted racks back online in the affected Availability Zone (use1-az4) in the US-EAST-1 Region. We have been able to get additional cooling system capacity online, which has allowed us to recover some affected racks and are actively working to recover additional racks in a controlled and safe manner. In the impacted Availability Zone, EC2 Instances, EBS Volumes, and other A...
May 8, 5:11 AM
Service impact: Increased Error Rate and Latency
Started: May 8, 3:06 AM
investigating
We are actively working to restore temperatures to normal levels in the affected Availability Zone (use1-az4) in the US-EAST-1 Region, though progress is slower than originally anticipated. Since our last update we have made incremental progress to restore cooling systems within the affected AZ, which will not be visible to external customers but are required for the restoration of affected services. In the impacted Availability Zone, EC2 Instances, EBS Volumes, and other AWS Services are als...
May 8, 3:06 AM
Service impact: Increased Error Rate and Latency
Started: May 8, 1:47 AM
investigating
We continue to work towards mitigating the increased temperatures to its normal levels in the affected Availability Zone (use1-az4) in the US-EAST-1 Region. Other AWS services that depend on the affected EC2 instances and EBS volumes in this Availability Zone, may also experience impairments. We have weighed away traffic for most services at this time. We recommend customers utilize one of the other Availability Zones in the US-EAST-1 Region at this time, as existing instances in other AZ's r...
May 8, 1:47 AM
Service impact: Increased Error Rate and Latency
Started: May 8, 12:53 AM
investigating
We continue to investigate instance impairments to a single Availability Zone (use1-az4) in the US-EAST-1 Region. We have experienced an increase in temperatures within a single data center, which in some cases has caused impairments for instances in the Availability Zone. EC2 instances and EBS volumes hosted on impacted hardware are affected by the loss of power during the thermal event. Other AWS services that depend on the affected EC2 instances and EBS volumes in this Availability Zone, m...
May 8, 12:53 AM
Service impact: Increased Error Rate and Latency
Started: May 8, 12:25 AM
investigating
We are investigating instance impairments in a single Availability Zone (use1-az4) in the US-EAST-1 Region. Other Availability Zones are not affected by the event and we are working to resolve the issue.
May 8, 12:25 AM
April 2026
Service disruption: Increased Error Rates
Started: Apr 30, 7:25 AM
investigating
We are providing an update on the ongoing service disruption. The Middle East (UAE) Region (ME-CENTRAL-1) has suffered damage as a result of the conflict in the Middle East and is currently unable to reliably support customer applications. While some workloads continue to function normally, we strongly recommend customers migrate all accessible resources to other Regions and restore inaccessible resources from remote backups as soon as possible. Relevant billing operations are currently suspe...
Apr 30, 7:25 AM
Service disruption: Increased Connectivity Issues and API Error Rates
Started: Apr 30, 7:07 AM
investigating
We are providing an update on the ongoing service disruption. The Middle East (Bahrain) Region (ME-SOUTH-1) has suffered damage due to the conflict in the Middle East and is currently unavailable. Customers should recover their resources in other Regions from remote backups. Relevant billing operations are currently suspended while we restore normal operations in this AWS Region. This process is expected to take several months.
Apr 30, 7:07 AM
Service is operating normally: [RESOLVED] Increased Connectivity Issues
Started: Apr 27, 12:05 PM
resolved
Between 3:58 AM and 4:40 AM PDT, we experienced increased error rates and increased launch failures for EC2 instances in a single Availability Zone (euw3-az2) in the EU-WEST-3 Region. During this time, customers attempting to launch new EC2 instances in the affected Availability Zone would have experienced launch failures. Additionally, a subset of existing EC2 instances and EBS volumes in this Availability Zone were impacted and became unreachable.
We have identified the root cause to be a ...
Apr 27, 12:05 PM
Service impact: Increased Connectivity Issues
Started: Apr 27, 11:27 AM
investigating
We are investigating instance connectivity issues in a single Availability Zone (euw3-az2) in the EU-WEST-3 Region.
Apr 27, 11:27 AM