Amazon cloud computing outage disrupts Snapchat, Ring and many other online services
Summary
Early on Monday a major Amazon Web Services (AWS) outage caused widespread disruption to dozens of popular online services. A DNS-related problem in the US-EAST-1 region led to increased error rates and latencies across around 64 internal AWS services, affecting apps and platforms such as Snapchat, Roblox, Fortnite, Signal, Coinbase, Robinhood, McDonald’s app, Ring doorbells, Alexa devices and Kindle downloads.
AWS first reported investigating the issue at about 03:11 Eastern Time and said recovery was under way roughly three hours later, with most affected services showing recovery by about 06:30 ET. AWS and experts said the incident appears to be a technology fault rather than a cyberattack, and cited the concentrated dependency on a small number of cloud providers as the reason outages have broad impact.
Key Points
- The outage originated in AWS’s US-EAST-1 region and was linked to domain name system (DNS) issues that prevented services resolving addresses properly.
- Dozens of consumer-facing apps and services were affected, including social, gaming, finance and smart-home platforms (Snapchat, Roblox, Fortnite, Signal, Coinbase, Robinhood, Ring, Alexa).
- AWS reported increased error rates and latencies at ~03:11 ET and began to see recovery across most services by around 06:00–06:30 ET.
- AWS said 64 internal services were impacted; engineers were actively working on full resolution during the incident.
- Experts emphasised the risk of centralised cloud dependency — when a major provider has issues many downstream services appear to fail.
- Historical context: AWS has had notable incidents before (2021, 2023, 2020, 2017) that also disrupted a wide range of industries and consumer services.
Context and relevance
Cloud providers like AWS underpin huge parts of the modern internet — from government sites and newsrooms to apps you use every day. When a primary region or core service has problems, the effects cascade quickly across industries. This outage highlights ongoing resilience and redundancy challenges for companies that rely heavily on third-party cloud infrastructure, and it serves as a reminder that contingency planning (multi-region deployments, fallbacks, clear incident communications) remains essential.
For businesses and IT teams, the incident is relevant to risk assessments and architecture decisions; for general users it explains sudden app failures and why many unrelated services can go offline at once.
Why should I read this?
Short and blunt: if you use any major apps or smart-home gadgets, this explains why they suddenly stopped working and how that could happen again. Saves you the hassle of chasing dozens of status pages — and gives a quick steer on what companies should fix next (hint: less single-region reliance).
