A wide interruption in Amazon Web Services (AWS) This morning, the virus has caused large-scale failures in dozens of applications, websites, and digital services around the world. The first warnings have been recorded. from 08:40-09:00 (peninsular time), with particular impact on services dependent on the US-EAST-1 region.
The drop is not limited to a single product: it ranges from voice assistants and streaming to productivity tools, social networks and video games. In Spain, incidents have also been reported in the card payments and Bizum, along with problems with data phones and some ATMs, an impact that has left many businesses temporarily resorting to cash.
What's happening right now
Amazon has recognized in its status panel a anomalous increase in errors and latencies in various services hosted in the region US-EAST-1 (Northern Virginia)The company assures that its technical teams are working to restore normality and that, as the hours pass, significant signs of recovery are observed in most of the requests.
Throughout the morning there have been several updates: first the incident was confirmed (minutes after 09:00), then it was communicated that Most operations should start processing successfully, and it was later indicated that the origin of the problems was linked to the DNS resolution associated with DynamoDBMitigating that point has improved the situation, although residual errors may still appear.
For those who continue to encounter errors when connecting to specific services, AWS has recommended retry requests and, in specific cases, flush the DNS cache, especially if issues persist with DynamoDB endpoints in the affected region.
Reports from incident tracking platforms have shown a sustained decline in reports as midday progressed, which points to a gradual and phased recovery depending on the service and location.
Services and platforms with incidents
The range of impacted services is broad and heterogeneous. Among the most mentioned by users and companies are Alexa and Prime Video. Amazon ecosystem, as well as multiple third-party applications that rely on the AWS infrastructure.
- Entertainment and games: Fortnite, Roblox, Clash Royale, PUBG, Rainbow Six Siege, Crunchyroll and Prime Video have reported connection errors and intermittent drops.
- Productivity and creation: Canva, Duolingo, Trello, Slack, Zoom and Dropbox have shown unstable access and high response times.
- Networks and messaging: Reddit and Snapchat have racked up reports for loading failures and momentary blockages.
- AI and assistants: Perplexity and Alexa-enabled devices and Amazon Generative AI, and cameras and doorbells of the Ring ecosystem, have experienced feature outages.
- Payments and Commerce: incidents in dataphones, Bizum and some gateways have forced the suspension of specific operations; Ticketmaster It even delayed ticket sales, such as those planned for La Oreja de Van Gogh.
Where it has been most noticeable and why it affects people outside the US.
The incidents have been concentrated on the east coast of the United States (with peaks in New York, Los Angeles, San Francisco and Seattle), but problems have also been reported in the United Kingdom (London and Manchester) and several European countries. Although the epicenter is in US-EAST-1, many global services depend on that region for critical parts of their operations.
In practice, this means that some applications They remain accessible but with limited functions, or do not update content in real time. This distributed architecture explains why a localized failure can have a domino effect on other regions, even when European or Asian data centers remain operational.
Indicative chronology of the incident
• Among the 08:40 and 09:00 hrs. (peninsular time) the first peaks of reports arise. • About 09:30, AWS confirms problems that increase error rates and latencies in various services. • Around the 11:00, Amazon indicates that it has identified the possible cause and is working on mitigation. • After 11:30, communicates clear signs of recovery. • At midday, reports decrease and most services are gradually restored.
Even so, the company warns of possible residual incidents in certain operations and recommends retries until normality is complete on all fronts.
How it affects you and what you can do
If you notice that a website is not loading, Alexa is not respondingIf an online game isn't connecting, or a work app is experiencing issues, it's likely that the service is dependent on AWS and is in the recovery phase. In these cases, Restarting routers or devices usually doesn't help.; the most effective thing is to wait and try again later.
In professional environments, it is advisable to plan critical tasks with margin and, if possible, enable retries and timeouts more generous in integrations that depend on AWS endpoints. In very specific scenarios, emptying the DNS cache may speed up reconnection to certain services that have already been restored.
A reminder of cloud dependence
With a market share exceeding 30% Globally, AWS is the backbone of thousands of digital businesses. When an incident hits a key region like US-EAST-1, the shock wave It is evident in applications used daily by millions of people, from streaming and gaming to banking and e-commerce.
Today's episode brings back to the table the need for resilient architectures (multiregion, multilayer and with controlled degradation), in addition to clear communication strategies to manage the expectations of users and customers when major interruptions occur.
After several hours of mitigation work by Amazon, the situation points to a gradual recovery in most services, with visible improvements in access and latency. There may still be small shocks, but the trend is positive and everything indicates that traffic is returning to normal in some sections as adjustments are completed in the affected region.
