On October 20, 2025, Amazon Web Services (AWS) experienced a widespread outage that impacted thousands of websites, apps and services around the world, underscoring the fragility of modern cloud-based infrastructure. According to monitoring site Downdetector, more than 6.5 million error reports were logged across over 1,000 companies during the incident.
What happened
AWS’s announcement on its status dashboard noted “increased error rates and latencies for multiple AWS Services in the US-EAST-1 Region.”
The root cause was traced to a Domain Name System (DNS) failure affecting the DynamoDB database service in the US East 1 region, located in northern Virginia.
Who was affected
Major platforms across gaming, social media, payments and enterprise tools reported disruptions—examples include Snapchat, Fortnite, Venmo, Signal and multiple airline and banking services.
The outage also affected AWS-hosted services such as Ring doorbell cameras and its Alexa smart-assistant ecosystem.
Broader implications
The incident revealed how concentrated the internet’s architecture is: when a single region of a dominant cloud provider fails, the ripple effects can disable entire ecosystems of apps and services. Experts say this points to a need for greater system redundancy and diversification.
Recovery and outlook
AWS reported that the main issue had been “fully mitigated” by early evening Eastern Time, though some services continued to experience “elevated error rates” while back-logs were cleared. The episode is now adding renewed urgency to discussions about cloud resilience, decentralisation of infrastructure, and risk management in the digital economy.
As the digital economy deepens its reliance on a handful of cloud providers, this outage serves as a sharp reminder: infrastructure failures at one major node can cascade globally. Companies, governments and users alike may need to rethink how critical services are architected—and whether single points of failure can be avoided.
