Data Security

Amazon Web Service outage is impacting major websites

Amazon Web Service (AWS) is suffering a major service outage that is affecting popular platforms in regions where the company provides services.



The cloud service and hosting provider Amazon Web Service (AWS) is going through a service outage affecting popular platforms such as Netflix, Roku, Disney Plus, gaming platforms including PUBG, Valorant, and League of Legends. 

Some users have also reported issues accessing Coinbase, the largest cryptocurrency exchange in the U.S., stock trading app Robinhood, Venmo, Cash App, and Tinder, etc.

The outage has also affected Amazon.com where users have pointed out that they are having connectivity issues and/or unable to access the website. Other Amazon services affected by the disruption include Ring security cameras, Amazon Alexa, Amazon Music, and Kindle ebooks.

Amazon on the other hand has acknowledged the issue. On its Status Page, the company confirms instability in all regions where it provides AWS. The root cause of this issue is the impairment of several network devices, the company has confirmed.



The incident takes us back to Match 3rd, 2017 when AWS suffered a worldwide outage and took down almost the entire internet with it. The company later blamed an AWS engineer for their “minor typo” as the reason behind the outage.

As for the latest issues, at the time of publishing this article (9:35 PM Tuesday, December 7, GMT), AWS’ Status Page was displaying the following update:

[9:37 AM PST] We are seeing an impact to multiple AWS APIs in the US-EAST-1 Region. This issue is also affecting some of our monitoring and incident response tooling, which is delaying our ability to provide updates. We have identified the root cause and are actively working towards recovery.

[10:12 AM PST] We are seeing an impact to multiple AWS APIs in the US-EAST-1 Region. This issue is also affecting some of our monitoring and incident response tooling, which is delaying our ability to provide updates. We have identified the root cause of the issue causing service API and console issues in the US-EAST-1 Region, and are starting to see some signs of recovery. We do not have an ETA for full recovery at this time.

[11:26 AM PST] We are seeing an impact to multiple AWS APIs in the US-EAST-1 Region. This issue is also affecting some of our monitoring and incident response tooling, which is delaying our ability to provide updates. Services impacted include: EC2, Connect, DynamoDB, Glue, Athena, Timestream, and Chime and other AWS Services in US-EAST-1. The root cause of this issue is an impairment of several network devices in the US-EAST-1 Region. We are pursuing multiple mitigation paths in parallel, and have seen some signs of recovery, but we do not have an ETA for full recovery at this time. Root logins for consoles in all AWS regions are affected by this issue, however customers can login to consoles other than US-EAST-1 by using an IAM role for authentication.



[12:34 PM PST] We continue to experience increased API error rates for multiple AWS Services in the US-EAST-1 Region. The root cause of this issue is an impairment of several network devices. We continue to work toward mitigation, and are actively working on a number of different mitigation and resolution actions. While we have observed some early signs of recovery, we do not have an ETA for full recovery. For customers experiencing issues signing-in to the AWS Management Console in US-EAST-1, we recommend retrying using a separate Management Console endpoint (such as https://us-west-2.console.aws.amazon.com/). Additionally, if you are attempting to login using root login credentials you may be unable to do so, even via console endpoints not in US-EAST-1. If you are impacted by this, we recommend using IAM Users or Roles for authentication. We will continue to provide updates here as we have more information to share.

Hackread.com will update this article based on the information shared by AWS. Stay tuned…

Update (8:29 AM Wednesday, December 8th, GMT)

The issue with AWS has been solved however according to its status page, the company will work towards recovery of any impaired services. 


To Top

Pin It on Pinterest

Share This