Amazon Web Services (AWS) has officially confirmed that its cloud infrastructure is back online after the major outage which disrupted hundreds of websites and apps across the internet. The company stated that the incident was caused by a combination of DNS resolution failures and internal load balancer degradation in its US-EAST-1 region, one of its busiest data centres. “There are no issues with AWS services, and all AWS services are operating normally. We are aware that an operational issue at another infrastructure provider may be impacting some customers’ applications and networks,” the company said on its status page. As per AWS’s post-event analysis, the disruption started with elevated error rates in DynamoDB API endpoints, triggered by a DNS issue. This was compounded by a failure in the internal health monitoring system for Network Load Balancers (NLBs), which led to cascading connectivity problems across services like EC2, S3, and Lambda. The outage affected major platforms including Snapchat, Reddit, Slack, Canva, and Amazon.com, with millions of users reporting issues via Downdetector. AWS engineers mitigated the DNS issue by 2:24 AM PDT and gradually restored services throughout the day.
AWS stated that all services were fully operational by 6 PM ET on October 29, and the company is now conducting a full review to prevent future incidents. Despite the scale of the disruption, no real-time updates were posted on the AWS Health Dashboard during the outage, drawing criticism from developers and enterprise clients.The outage rippled across industries, affecting:
- Cloud-hosted websites and applications
- Streaming platforms and smart home devices
- Enterprise tools and e-commerce systems
Experts say the incident underscores the fragility of centralized cloud infrastructure and the risks of over-reliance on a single provider. AWS powers over 30% of the global cloud market, making even short outages highly disruptive
