**UPDATE Monday, 11:45 a.m. ET:** Amazon has confirmed that AWS is experiencing further issues late Monday morning, only hours after the initial problem seemed to be resolved. The company announced it is looking into “the underlying cause of the network connectivity problems affecting AWS services such as DynamoDB, SQS, and Amazon Connect,” in its latest communication on the [AWS status page](https://health.aws.amazon.com/health/status).
In the meantime, widespread service outages across the web continued. User-reported problems have escalated for several well-known services, according to [Down Detector](https://downdetector.com/), including FanDuel, Snapchat, Apple Music, Asana, Verizon, and numerous others. The renewed AWS troubles appeared substantial and once again affected a significant number of users.
A service interruption at Amazon Web Services (AWS), Amazon’s widely used cloud hosting and data service, created considerable issues for internet users beginning their workweek on Monday. Given that AWS powers large segments of the internet, the range of services and sites that experienced outages on Monday was vast.
Based on user-reported issues at the [Down Detector](https://downdetector.com/) website, impacted services included United Airlines, AT&T, Fortnite, Disney+, HBO Max, Signal, Snapchat, McDonald’s, Verizon, Venmo, among others. (Disclosure: Down Detector is owned by Ziff Davis, the same parent company as Mashable.) Amazon services, including Prime and Alexa, were affected as well. In summary: Almost everyone would have been impacted in some manner.
Almost everything we possess is connected to the internet — our refrigerators [act as WiFi-enabled advertisements](https://mashable.com/article/samsung-smart-fridge-advertisements) — which implies an AWS outage can disrupt large parts of daily life.
**SEE ALSO:** [AWS outage list: Roblox, Fortnite, Snapchat, Signal, and more](https://mashable.com/article/aws-outage-list-amazon-roblox-fortnite-snapchat)
As midday approached, it seemed the problem was resolved. However, the [AWS Health Dashboard](https://health.aws.amazon.com/health/status) signaled that issues had re-emerged.
“We have confirmed that multiple AWS services faced network connectivity problems in the US-EAST-1 Region,” stated an update around 10:30 a.m. ET. “We are observing initial signs of recovery for the connectivity issues and are continuing to investigate the underlying cause.”
It appeared AWS was experiencing problems again, although not at the level of the earlier outage. Certain services, such as [Venmo](https://downdetector.com/status/venmo/) and [Boost Mobile](https://downdetector.com/status/boost-mobile/), noted a correlating rise in user-reported issues on Down Detector.
Previously, Amazon indicated that the issue had been fully resolved or was in the process of being resolved. Mashable sought comment and was directed to the [AWS Health Dashboard](https://health.aws.amazon.com/health/status). At approximately 6:35 a.m. ET, the AWS Health Dashboard suggested that the primary issue was resolved, although problems might linger as systems came back online. This could potentially hint at the new challenges that arose.
“The fundamental DNS problem has been entirely mitigated, and most AWS service operations are functioning normally now,” the 6:35 a.m. ET update stated. “Some requests may be delayed while we continue working toward complete resolution.”
**What led to the AWS outage?**
The precise cause of AWS’s initial downtime remains unclear, but there are indications. Services relying on AWS were unable to access DynamoDB, an Amazon-operated database, due to a problem with the Domain Name System (DNS). The DNS essentially translates website names into IP addresses. Therefore, when Amazon announced on its Health Dashboard that the DNS issue had been “fully mitigated,” it implied that the core problem had been corrected.
“Amazon had securely stored the data, but no one could access it for several hours, leaving applications temporarily disconnected from their information,” Mike Chapple, an IT professor at the University of Notre Dame, [informed CNN](https://www.cnn.com/business/live-news/amazon-tech-outage-10-20-25-intl?t=1760968946687). “It’s like large sections of the internet experienced momentary amnesia.”
Rafe Pilling, the director of threat intelligence at Sophos, a cybersecurity firm, [stated to *The Guardian*](https://www.theguardian.com/technology/2025/oct/20/amazon-web-services-aws-outage-hits-dozens-websites-apps) that the event didn’t seem to be a cyberattack or anything malicious, which aligns with Amazon’s assertions.
“When incidents like this occur, concerns about it being a cyber event are understandable,” he conveyed to the U.K. outlet. “AWS has an extensive and complex footprint, so any issue can lead to significant disruptions.”
It is probable that Amazon will, at a later time, clarify what occurred.