The Coalition linked Gears of War: E-Day disruptions to DDoS attacks, OpenCritic reports

In a report published October 12, OpenCritic says The Coalition attributed intermittent disconnects, login problems and other Gears of War: E-Day online-service disruptions to distributed denial-of-service attacks, or DDoS attacks. The report also says Xbox Support had announced a resolution 20 minutes before publication—a separate status update from the problems reported the day before.

What The Coalition said E-Day’s connection problems

On October 11, Gears Community posted that a login issue had been resolved and that it would continue monitoring services. Later that day, MP1st reported renewed login and save-synchronization problems. Its account describes a recurrence after the earlier resolution notice.

OpenCritic’s October 12 report attributes the disruptions to DDoS attacks targeting E-Day’s online services. A DDoS attack attempts to disrupt a service by overwhelming it with traffic from multiple sources, making access harder for legitimate users, according to CISA’s explanation of denial-of-service attacks .

What the PC test found offline play

James Lara’s report for MP1st says the outlet’s PC test could not access online mode because campaign save data failed to load amid synchronization errors. After launching offline mode, the test continued the campaign save. MP1st also reported that some other players had trouble loading their campaigns, so the test describes one PC experience rather than a universal result.

For separate estimates of campaign length, see our earlier Gears of War: E-Day campaign coverage .

What players said they lost

The login issue has been resolved, we'll continue to closely monitor our services. Thank you for your patience. — Gears Community (@Community_Gears) October 11, 2026

The login issue has been resolved, we'll continue to closely monitor our services. Thank you for your patience.

Individual posts describe different outcomes: some players said they could continue the campaign offline, while others reported access trouble. In a separate thread, one commenter said their team lost a 40-minute Horde Siege match with 17 weapon parts as it neared extraction. Other players described missing XP or rewards. These accounts capture individual experiences, not a count of affected players ( offline-play discussion , Horde Siege account , other reward reports ).

A player cannot mitigate an attack directed at a game provider’s services. Checking official service notices and whether other online games or devices connect can help distinguish a game-service problem from a local connection issue.