Imagine trying to log into Instagram to share your morning selfie, but the page simply won’t load. Or rushing to work, only for the Lyft app to throw an error, leaving you stranded in traffic. Perhaps you’re planning an evening Netflix binge, but the screen goes black mid-sentence. This isn’t the plot of a sci-fi movie—it’s the reality that struck millions around the world last night and this morning. The culprit behind this global chaos? Disruptions in Amazon Web Services (AWS)—the colossal cloud computing platform that underpins a massive chunk of internet infrastructure. The outage, which began around 00:11 Eastern Time (about 07:11 Kyiv time), quickly escalated into a full-blown crisis, crippling dozens of popular services from social media to financial apps.
According to monitoring services like DownDetector, complaints surged into the thousands within minutes. The peak hit Monday morning, when millions of users woke up to unexpected “dead zones” in the digital world. AWS officially acknowledged the issue on its service status page, reporting disruptions in 14 key components, primarily in the US East (Northern Virginia) region—one of the company’s busiest data centers, handling up to 30% of global internet traffic. “We are actively investigating the incident and working to restore service,” Amazon representatives stated in their first update. However, as of this writing, full recovery hasn’t occurred: some services are partially reviving, but localized disruptions persist in Europe, Asia, and the Americas.
Domino Effect: Which Services Were Hit?
The AWS outage isn’t isolated—it’s a chain reaction toppling entire sectors of the digital economy. Since thousands of companies, from startups to giants like Netflix and Disney, rely on Amazon’s infrastructure, issues in one region ripple out globally. Here’s a rundown of the key casualties from today’s “cyber-hurricane”:
| Category | Affected Services | Description of Issues |
|---|---|---|
| Social Media & Communication | Snapchat, Instagram, Signal | Login problems, photo uploads, and messaging failures. Users complain of an “eternal spinner.” |
| Finance & Payments | Venmo, Robinhood, Coinbase, Lloyds Bank (UK) | Transaction delays, inability to access accounts. Coinbase directly blamed AWS: “We know many users can’t log in due to the AWS outage. All funds are safe.” |
| Gaming & Entertainment | Fortnite, Roblox, Pokémon GO, Clash Royale | Server crashes, connection impossibilities. Players worldwide are “stuck” in lobbies or losing progress. |
| Streaming & Media | Netflix, Disney+, Prime Video | Video lags, playback interruptions. “Movies stop at the most exciting part,” users vent on social media. |
| Smart Home & Transport | Alexa, Ring, Lyft, McDonald’s app | Smart assistants go silent, security cameras go offline, rides can’t be hailed. |
| Education & Other | Duolingo, HMRC (UK tax authority) | Lesson glitches, access issues to government services. |
This list is far from exhaustive—Bloomberg estimates thousands of smaller apps and sites were also impacted, with a complaint peak at 07:30 London time. On Twitter (X), the situation turned meme-worthy: users quip that “X is the only service holding up on sheer willpower, since it doesn’t rely on AWS,” while others crash. One tweet reads: “AWS down, Coinbase down. Everything is absolutely fine 🥲 #AWS #internetdown”.
The exact cause remains unknown for now—AWS reports no signs of a hacker attack or DDoS, suggesting an “internal infrastructure failure.” Preliminary reports point to an issue in the DynamoDB database in the US East-1 region, critical for many services. Here’s the event timeline:
- 00:11 ET (07:11 Kyiv): First outage signals in AWS. Initial access issues with EC2 (virtual servers).
- 01:00 ET: Complaints on DownDetector hit thousands. Snapchat and Venmo fall first.
- 02:00 ET: Chain reaction—gaming and streaming join the fray. AWS issues first update: “Investigating.”
- Morning (09:00 Kyiv): Partial recovery in Europe, but the US and Asia remain in the “red zone.” Docker Hub users gripe about stalled deploys: “Docker Hub down. That means deploys worldwide stalled?”
Experts stress that US East-1 is AWS’s “Achilles’ heel,” bearing the heaviest load. “This is one of the biggest outages of 2025, comparable to those in 2021 and 2023,” writes Dataconomy.
For average users, it’s just an annoyance—no McDonald’s app for coffee or Fortnite sessions with friends. But for businesses, it’s a disaster. Rough estimates peg each minute of downtime at millions in losses: Netflix misses views, Coinbase skips trades, and banks like Lloyds risk client trust. In the UK, even the HMRC tax authority felt the blow, delaying declaration processing.
Globally, it highlights the fragility of the modern internet: 80% of Fortune 500 companies depend on AWS. “We’re seeing how one provider can paralyze the world,” comments tech evangelist Tal Barenboim on Twitter, referencing reliance on US East-1. In Europe, where GDPR regs demand resilience, firms are already discussing diversification—to Azure or Google Cloud. In Ukraine, where the fintech sector (Monobank, PrivatBank) partially uses AWS, there are no mass complaints yet, but local startups like Grammarly could feel the echoes.
Amazon Web Services isn’t new to causing global disruptions. In 2021, a 7-hour outage in the same US East-1 region knocked out Disney+, Hulu, and Twitch, costing Amazon hundreds of millions. In 2023, a similar incident crippled Slack and Zoom. This time, the scale is akin, but AWS’s response seems swifter—status updates every 30 minutes.
Experts like those at The Verge call it the “domino effect of monopoly”: AWS controls 33% of the cloud market, and any sneeze sparks an epidemic. At the same time, it’s a reminder of centralization risks: “Best we can do right now is touch grass,” jokes one X user, urging a screen break.
Today’s AWS outage isn’t just a tech glitch—it’s a mirror to our cloud dependency. When one service falls, the world tumbles. Amazon promises “swift recovery,” but the question lingers: Are we ready for the next? Companies must invest in redundancy, regulators in resilience standards, and users in patience. For now, as Twitter suggests, “touch grass”—step outside, because the internet can fail anytime.
This article is based on real-time events; AWS status updates here: AWS Status Page. If you’ve encountered issues, share in the comments—we’ll weather this “apocalypse” together.