Massive AWS Outage Knocks Fortnite, Roblox, Nintendo and More Offline — Widespread Service Disruptions

Early on Monday morning, a problem at Amazon Web Services (AWS) caused major interruptions to several popular online games and other web services. The issue started in AWS’s US-EAST-1 datacenter and, as a result, players and users saw outages across multiple platforms. Most services recovered within a few hours, according to AWS.

  1. What happened
  2. Affected games and services
  3. What stayed up
  4. Wider impact and recovery

What happened

Amazon Web Services reported an operational issue in its US-EAST-1 datacenter. Consequently, many services that rely on AWS saw outages early Monday. AWS later said it was observing recovery across most affected services by 6 a.m. EDT.

Affected games and services

Several major game services posted outage notices or reported problems. For example, Fortnite, Roblox, Nintendo’s online services, and a variety of other titles showed interruptions.

Fortnite posted a status update on its official account:

Roblox’s status page also listed service issues; the company logged the outage in its history and provided updates on availability.

More details are available on Roblox’s status page.

Nintendo reported its online services were unavailable and pointed users to its network information page for updates.

Check Nintendo’s notice on this page.

Other games that reported problems included titles like Clash Royale and Palworld.

The Epic Games Store also experienced issues during the outage window.

What stayed up

Not every gaming network was affected. For instance, Steam, PlayStation Network, and Xbox online services did not appear to suffer the same disruptions. In short, the outage had a big reach, but it wasn’t universal.

Wider impact and recovery

Because AWS is the world’s largest cloud provider, the outage extended beyond games. Sites and services such as Amazon itself, Reddit, Snapchat, Duolingo, and Ring reported problems or degraded service. However, AWS’s status updates indicated improving conditions by early morning.

For the official AWS health information, see their status page. AWS said the issue was operational in US-EAST-1 and that recovery was underway by 6 a.m. EDT.

Leave a Reply

Your email address will not be published. Required fields are marked *

    This website uses cookies to provide the best possible service. By continuing to use this site, you agree to their use. You can find more information in our Privacy Policy.