AWS Outage Cripples Fortnite, Alexa, and Snapchat
▼ Summary
– AWS is experiencing a major outage affecting online services like Amazon, Alexa, Snapchat, and Fortnite across multiple regions.
– The outage is causing increased error rates and latencies, primarily in the US-EAST-1 Region, according to AWS status reports.
– Services such as Perplexity, Airtable, Canva, and the McDonald’s app are impacted due to their reliance on AWS’s cloud network.
– The cause of the outage remains unconfirmed, and there is no clear timeline for when regular service will be restored.
– Amazon first reported issues at 3:11 AM ET and is actively working to mitigate the problem and determine the root cause.
A significant disruption to Amazon Web Services (AWS) is causing widespread outages for a host of popular online platforms and applications. Services including Fortnite, Alexa, and Snapchat are currently experiencing major operational failures due to this incident. The AWS status page confirms that multiple services are affected by operational problems, noting that the company is actively looking into increased error rates and performance delays primarily within the US-EAST-1 Region, with reports of disruptions also occurring in other global regions.
On social platforms like Reddit, numerous users have confirmed that the Alexa smart assistant is non-responsive, failing to answer questions or carry out commands. Personal testing reveals that even scheduled routines and preset alarms are not working. The cloud computing failure is also impacting a wide array of other platforms that depend on AWS infrastructure. Companies such as Perplexity, Airtable, Canva, and the McDonald’s mobile application are all reporting service interruptions. The exact origin of the outage remains unknown, and there is no official timeline for when full service might be reinstated.
Perplexity CEO Aravind Srinivas publicly addressed the situation on the social media platform X, stating, “Perplexity is down right now. The root cause is an AWS issue. We’re working on resolving it.”
The first indication of trouble appeared on the AWS service health dashboard at 3:11 AM Eastern Time, pinpointing issues in the US-EAST-1 Region. In a subsequent update posted at 3:51 AM ET, Amazon communicated that their teams were fully engaged in efforts to mitigate the problem and determine the underlying cause. They committed to providing another update within 45 minutes, or sooner if more information became available. The situation remains fluid as engineers work to restore normal operations.
(Source: The Verge)
