Is AWS Down?
AWS outage history and incident tracker. 73 incidents analyzed.
Total Incidents
73
Uptime
100.000%
Avg Resolution
N/A
Top Cause
api
AWS Outage Timeline
Outages by Year
Incident Severity
Recent AWS Incidents
View all →Service is operating normally: [RESOLVED] Elevated Packet Loss
Between 9:42 AM and 11:44 AM PDT, we experienced elevated network packet loss impacting AWS Direct Connect connectivity in the AP-SOUTH-1 Region. Our engineering team was automatically engaged at 9:46 AM to begin investigating. By 10:51 AM, we understood the root cause to be a configuration change made to a system responsible for assigning routes to devices. As we gained confidence in our mitigation steps, we parallelized our efforts to further reduce the packet loss. The issue is resolved and t
Service impact: Elevated Packet Loss
We have identified the root cause to be related to a change made to a configuration system responsible for assigning routes to the devices. We have begun the work to reduce the packet loss that is impacting AWS Direct Connect in the AP-SOUTH-1 Region, and we expect recovery to take place gradually over the next 30 minutes. As we gain confidence in these efforts, we will seek to parallelize our efforts to speed recovery. We will provide another update by 12:00 PM PDT.
Service impact: Elevated Packet Loss
We can confirm elevated network packet loss, impacting AWS Direct Connect connectivity in AP-SOUTH-1 Region. Our engineering team was automatically engaged at 9:54 AM to begin investigating the issue. There are no workarounds available at this time. We will provide another update by 11:30 AM PDT.
Service is operating normally: [RESOLVED] Connectivity Issues
Between 3:55 AM and 4:15 AM PDT, we experienced connectivity issues that impacted connectivity to the US-WEST-2 Region. This impacted multiple AWS services in the Region. Some customers may have also experienced issues accessing the AWS Management Console, with connection timeouts and unresponsive pages. Connectivity within the Region was not affected. Our engineers were automatically engaged at 4:01 AM PDT, and immediately began investigating this issue. We identified the root cause as an issue
Service impact: Connectivity Issues
We continue to see significant signs of recovery as a result of our mitigation efforts for the connectivity issues impacting multiple AWS services in the US-WEST-2 Region. We have identified the root cause as an issue with a networking device responsible for network routing from the Region to the Seattle Metro. Engineers have finished all mitigation work. As routes continue to be restored, customers should see a continued reduction in error rates and timeouts when connecting to affected services
Service impact: Connectivity Issues
We are seeing initial signs of recovery and continue to work toward full recovery.
Service impact: Connectivity Issues
We are investigating connecivity issues impacting multiple AWS services in the US-WEST-2 Region.
Service impact: Connectivity Issues
We are investigating connecivity issues impacting multiple AWS services in the US-WEST-2 Region.
Service is operating normally: [RESOLVED] Inaccurate Estimated Billing Data
Between July 16 at 7:38 PM PDT and July 18 at 6:00 AM PDT, we began displaying incorrect estimated billing data in the Billing and Cost Management Console, including the Cost and Usage Report. Customers may have received erroneous budget and cost anomaly detection alerts, and observed inflated estimated cost and usage data. On July 16 at 7:46 PM PDT, our alarms detected cost anomalies but failed to halt the estimated bill generation process or alert our engineering teams. We were alerted to thi
Service impact: Inaccurate Estimated Billing Data
We continue to make substantial progress toward resolving the issue affecting estimated cost and usage data displayed in the Billing and Cost Management Console. Our mitigation efforts are working as expected and we are seeing an increasing number of accounts reflecting correct cost and usage data. We expect all affected accounts to be fully recovered by July 19, 12:00 AM PDT. Until the backfill is complete, some customers may still observe incorrect cost and usage data in the Billing and Cost M
Incident Severity Distribution
Frequently Asked Questions
Is AWS down right now?▾
How often does AWS have outages?▾
What is AWS's uptime percentage?▾
What are the most common causes of AWS outages?▾
How long do AWS outages typically last?▾
How does AWS's reliability compare to other cloud providers?▾
Related Resources
Get Notified When AWS Goes Down
Subscribe to outage alerts via webhook or Slack and be the first to know about AWS incidents.
Set Up Alerts