Battle.net DDoS Attack: Kicked From WoW Forever at 2 a.m.

DDoS attack: kicked from WoW Forever at 2 a.m., a DDoS attack on Battle.net

Article by Kami

Around 2 a.m. in Paris, in the night of November 11 to 12, 2026, WoW Forever players were kicked out of the game, then left on the “Logging in to game server” screen. It was not a bug specific to Forever. A DDoS attack was hitting the whole of Battle.net, and Blizzard support confirmed it on its official forum.

A DDoS attack on Battle.net and every Blizzard game, confirmed by support

A DDoS attack (distributed denial of service) floods servers with connections from thousands of machines until they become unreachable. In general, this type of attack targets the availability of a service, not account data.

Message from Vrakthris, a Blizzard support agent, on the World of Warcraft forum, confirming an attack on all games
SourceOfficial Blizzard forum, November 12, 2026: Vrakthris’s message, which ends with “We are in the process of mitigating it, so things should be improving.”

The official fact fits in one message. At 01:23 UTC (02:23 Paris time (CET)), Vrakthris, a Blizzard support agent, answers a player in the thread “What are the solutions? Wow Forever” on the US forum: “we have been experiencing a DDOS for all games”. The message adds that the team is working to contain it and that the situation should improve.

Nine minutes later, a player in the same thread copies the alert message from the Battle.net launcher: “We are currently experiencing a DDoS attack, which may result in high latency and disconnections for some players.” This quote is secondhand: it comes from a player, not from an official page we read ourselves. It matches the message used during the March and April 2025 attacks on Battle.net.

For latency specific to Europe, another phenomenon exists: see our article on high ping in WoW Forever.

Advertisement
RestedXP Forever - Partenaire officiel -10%

Timeline of the night of November 11 to 12, in Paris time (CET)

Sources give UTC time; Paris is one hour ahead. The first reports, recorded in the Endgame Tools timeline, come in at 00:57 UTC. The symptoms repeat from one player to the next: disconnection, a hang at login, then another disconnection shortly after.

UTC timeline of the night of November 12 published by the Endgame Tools site
SourceEndgame Tools, Stowlen, November 14, 2026: the timeline of the night, in UTC.
Time in Paris (CET)EventType of source
1:57 a.m.First reports of disconnectionsPlayers, recorded by Endgame Tools
2:23 a.m.Vrakthris’s message on the forumOfficial (Blizzard support)
2:32 a.m.Battle.net launcher alert message copied into the threadSecondhand (a player)
2:52 a.m.First reconnectionsPlayers, third-party sites
5:05 a.m.Service “largely back”Third-party site reports
10:15 p.m., November 12Second wave of disconnectionsPlayers, “Servers down. AGAIN” thread

The site MMOHuts picked up the story on November 13, written by Kipp Stryxs, judging the problems “apparently resolved”.

What remains unanswered after the DDoS attack

That second wave is reported at 21:15 UTC (22:15 Paris time (CET)) in the thread “Servers down. AGAIN”. Support left no reply there, and nothing shows that it stems from the same DDoS attack.

First post of a World of Warcraft forum thread where a player complains about new disconnections
SourceOfficial Blizzard forum, November 12, 2026: the thread opened by a player during the second wave of disconnections, left without a reply from support.

The return to normal came with no official announcement: the recovery times come from players and third-party sites. On compensation, nothing has been announced. Our searches turned up no claim of responsibility, and Blizzard has given no cause. This night falls eight days after the game’s release on November 4, and its launch record.

Two other incidents that week are separate from this night: the November 9 outage and the maintenance on the 13th, caused by a server crash and not by an attack.