Lead: On Dec 25, 2025 at 10:50 am IST multiple online gaming services experienced a widespread outage that disrupted play for thousands worldwide. Titles affected include ARC Raiders, Fortnite, Among Us, Rocket League and other Epic Games properties; Downdetector recorded more than 35,000 reports for ARC Raiders and about 4,000 reports linked to AWS. Epic’s status page and player reports indicate login failures, ART00004 and EAC-related errors, and interrupted in-game purchases for some users. As of the latest update, Epic lists several services as down while AWS said its systems were operating normally.
- Scale: Downdetector logged over 35,000 complaints for ARC Raiders and roughly 4,000 AWS-related reports at peak disruption on Dec 25, 2025.
- Core services affected: Fortnite, Rocket League, Fall Guys and Epic Online Services (EOS) were listed as down on Epic’s status page.
- Specific errors: ARC Raiders players reported persistent ART00004 errors; other users saw EAC and ‘Servers Not Responding’ login failures.
- Broader impact: Titles outside Epic’s ecosystem—Among Us, Dead by Daylight, Elden Ring, Palworld and Amazon games Throne and Liberty and Lost Ark—also reported interruptions.
- Company response: Epic acknowledged outages on its status page; AWS issued a statement saying its services were operational and pointed users to the AWS Health Dashboard.
- User guidance: Advisories recommend monitoring official status pages, avoiding repeated login attempts and waiting for server-side fixes rather than local troubleshooting.
- Traffic factor: Developers cited heavy traffic from events such as the Cold Snap activity in ARC Raiders as exacerbating failures.
Background
Online game outages are typically caused by infrastructure failures, authentication system problems, or sudden traffic surges tied to in-game events. Epic Games relies on Epic Online Services (EOS) and third-party hosting providers to authenticate players, matchmake and handle purchases; any degradation in these subsystems can cascade across multiple titles. ARC Raiders launched recent content events that increase concurrent users—Cold Snap was specifically cited by players as a traffic spike that coincided with ART00004 errors.
Downdetector and similar crowd-sourced monitors compile user reports to highlight outages in real time; while these sites do not confirm root causes, they often reflect the geographic and temporal contours of disruptions before companies post formal updates. Historically, large outages affecting multiple major publishers have been traced to either cloud-provider incidents, DNS or routing problems, and in rare cases central authentication failures. Game developers typically respond with status updates, rollback of recent changes, or scaling actions at cloud providers.
Main Event
The outage emerged on Wednesday morning local time and quickly escalated into a multi-title disruption. Epic’s status page began showing degraded or unavailable services, with login and matchmaking failing for Fortnite players and store purchases intermittently blocked. ARC Raiders communities reported ART00004 errors upon attempting to connect, and players noted that matches started but could not be rejoined, risking item loss.
Among Us developer Innersloth had not posted a direct update at the time of reporting, while multiple other titles—Rocket League, Fall Guys, Dead by Daylight, Elden Ring and Palworld—showed elevated problem reports. Amazon-hosted MMORPGs including Throne and Liberty and Lost Ark also registered complaints, suggesting a broadly distributed disruption affecting several ecosystems. AWS posted a public statement denying a platform-wide outage and directing customers to the AWS Health Dashboard for authoritative status information.
On social platforms, players described repeated login attempts, intermittent connections and concerns about progress or item loss during interrupted matches. Some users successfully entered matches but reported persistent reconnection failures. Developers and platform operators urged patience and discouraged repeated login attempts to prevent account flags and further load spikes.
Analysis & Implications
When multiple major titles experience simultaneous failures, the immediate economic and reputational costs for developers and platform providers can be substantial. Lost revenue from blocked purchases, disrupted events and frustrated players compounds as social chatter amplifies perceived severity. For games running live events—like ARC Raiders’ Cold Snap—downtime during scheduled activities amplifies player complaints and can drive short-term churn.
From a technical standpoint, cascading failures often reflect interdependencies: authentication, matchmaking and anti-cheat layers (such as EAC) frequently touch many products. If a central service degrades—whether due to a provider routing issue, certificate failure, or overloaded API endpoints—titles that rely on that service will surface similar symptoms (login failures, timeouts, ART/EAC error codes).
Operationally, the incident underscores the need for multi-region redundancy, robust incident communication and player protections (such as match-state persistence and safe rollback options). For cloud providers, such events raise scrutiny over transparency and status tooling; AWS’ emphasis on its Health Dashboard reflects a push to centralize authoritative information amid social-media speculation.
Comparison & Data
| Service | Peak reports (Downdetector) | Common symptom |
|---|---|---|
| ARC Raiders | 35,000+ | ART00004 login failures |
| AWS (related reports) | ~4,000 | Various connectivity/response issues |
| Fortnite / EOS | Varied, thousands across regions | Login errors, store purchase failures |
The table above aggregates crowd-reported volumes at peak disruption and the most commonly mentioned failure modes. While Downdetector totals are useful to measure user impact, they do not determine root cause; company status pages and official incident reports are required for a definitive timeline. The pattern here—high user reports across independent titles and an official denial of a cloud outage—suggests a complex incident involving cross-provider dependencies or targeted regional network issues rather than a single obvious cause.
Reactions & Quotes
Game communities reacted rapidly on social platforms, sharing troubleshooting steps and reporting loss of progress. Below are representative statements tied to institutional sources and player posts, with context provided.
No, that’s false. AWS services are operating normally today, but an event elsewhere on the internet has prompted some inaccurate speculation on social media.
AWS (official statement)
Amazon’s message emphasized the AWS Health Dashboard as the authoritative system for service availability, pushing back on claims of a provider-wide outage.
Fortnite, Rocket League, Fall Guys and EOS are listed as down while we investigate.
Epic Games Status Page (official)
Epic’s status entries confirmed degraded availability across multiple services and advised players to monitor updates while engineers examine root causes.
I managed to launch the game and join a match but keep getting the same error and can’t reconnect.
Player report on X (community)
Players relayed intermittent successes followed by reconnection failures—behavior that points to session-authentication or matchmaking instability rather than a purely client-side bug.
Unconfirmed
- Reports that a single cloud-region routing change caused the outages are unconfirmed; no provider has published a root-cause analysis yet.
- Claims that user accounts were broadly compromised during the outage remain unverified; developers have not reported a security breach.
- Allegations tying the incident to a coordinated attack lack corroborating technical evidence at this time.
Bottom Line
The Dec 25, 2025 outage disrupted dozens of thousands of players across multiple major titles and highlighted the fragility that comes with complex cross-service dependencies. While crowd-reporting sites captured the scale of user impact—notably 35,000+ ARC Raiders reports—official diagnosis is pending; AWS and Epic have provided differing messages about the locus of the problem.
For players: monitor official status pages, avoid repeated login attempts that can exacerbate load, and back up any client-side settings where possible. For operators: the incident reinforces the value of transparent incident timelines, multi-region failover, and protective measures for live events to reduce player loss when outages occur. Expect follow-up postmortems from affected companies in the days after the incident.
Sources
- Hindustan Times — News media report summarizing user impact and company statements
- Epic Games Status Page — Official service status and incident updates
- Downdetector — Crowd-sourced outage reporting and incident volume
- AWS Health Dashboard — AWS official availability and incident reporting (official)
- @ARCRaidersGame on X — Developer social account; no update posted at time of reporting (developer account)
- @AmongUsGame on X — Innersloth social account; no formal outage message posted at time of reporting (developer account)