Christmas outage, AWS linked interrupts Fortnite and multiple gaming platforms

Players across multiple gaming ecosystems woke up on December 25 to disrupted sessions, failed logins and stalled matchmaking after an internet event that coincided with concentrated reports of Amazon Web Services related issues. Epic Games services including Fortnite, Rocket League, Fall Guys and the Epic Games Store reported widespread problems with authentication, matchmaking and timeouts, and an independent outage tracker recorded a series of large spikes in complaints stretching from December 24 into the following day.

The most extreme single service surge was for ARC Raiders, where Downdetector logged nearly 35,000 reports at peak. Steam users reported prolonged slowness and partial outages affecting the Steam Store, community pages and online play. PlayStation Network experienced partial interruptions that complicated cross platform gaming, and other digital services from social apps to payment platforms showed intermittent disruptions in some regions. Outage trackers indicated more than 4,000 U.S. users reporting AWS related problems at peak, while complaint counts in India remained far lower by comparison.

The timing of the incident aligned with heavy holiday traffic, amplifying the user impact as millions of players attempted to log in or join multiplayer sessions. Community channels and platform status pages filled with reports of service unavailability, and outage maps showed clusters of complaints concentrated in North America and parts of Europe. Advisories circulating in forums urged players to monitor official status pages such as the Epic Games status site and the AWS Health Dashboard, to avoid repeated login attempts that can trigger account flags, and to wait for server side fixes rather than cycling credentials.

Amazon Web Services publicly denied a platform wide outage, stating that its services were functioning normally and that the AWS Health Dashboard should be treated as the authoritative source for service availability. The company framed public claims as linked to an unrelated internet event and did not provide a detailed technical root cause or confirm involvement of specific AWS components. Platform operators and outage monitors said services were restored after several hours, and many affected games returned to normal play later on December 25.

The disruption highlighted continuing vulnerabilities in a digital ecosystem that increasingly relies on centralized cloud infrastructure. Engineers and industry observers noted the episode echoes an October 2025 disruption that similarly affected major platforms, underscoring the cascading effects an internet incident can have across gaming, commerce and communication services. Precise user counts remain difficult to verify because public telemetry depends on third party trackers and self reported complaints, and some outlet characterizations of affected populations vary widely.

For now, operators are urging patience while they complete internal reviews and restore full confidence in system stability. Key unresolved items include a detailed public root cause analysis from AWS and definitive cross platform telemetry that would quantify the full scale of impact on player populations and third party services.