Skip to content

WoW Forever newsNov 14, 20262 min read

WoW Forever down? The Battle.net DDoS of November 12

Blizzard confirmed a DDoS on all its games on November 12, 2026: WoW Forever players stuck on Logging in to game server. What happened, what Blizzard said.

By Stowlen

Endgame Tools · Published

In this article

On November 12, 2026, from about 00:57 UTC (the evening of November 11 in the Americas), a DDoS attack on Blizzard's games disconnected WoW Forever players and left them stuck on "Logging in to game server". At 01:23 UTC, Blizzard's Customer Support confirmed on its forums "a DDOS for all games"; players wrote that they were back in the game from 01:52 UTC. A second wave of disconnections began at about 21:15 UTC the same day, and Blizzard has not said what caused it.

What happened, hour by hour (UTC)

  • 00:57: the first reports on Blizzard's North American forums. Players were thrown back to the login screen, then stuck on "Logging in to game server", in every version of WoW at once; one of them could still play Hearthstone.
  • 01:23: Vrakthris, of Blizzard's Customer Support, answered a WoW Forever player: "we have been experiencing a DDOS for all games. We are in the process of mitigating it, so things should be improving."
  • 01:32: a player quoted the warning the Battle.net app showed: "We are currently experiencing a DDoS attack, which may result in high latency and disconnections for some players. We are actively working to mitigate this issue."
  • 01:52 to 01:54: players wrote on the forums that they were back in.
  • 21:15: new disconnections, the afternoon of November 12 in the Americas, with the thread "Servers down. AGAIN" on the same forums. In the threads we read, no Blizzard post explained this second wave.

What Blizzard said

Only the Customer Support answer and the Battle.net app's warning above. Blizzard did not say who was behind the attack, nor why, and its Customer Support account on Bluesky posted nothing about it (read on November 13 at 15:46 UTC). Reasons given by players on the forums are guesses, and we do not repeat them.

The same night, about gold lost in an earlier crash, Customer Support also wrote that it "is generally unable to provide compensation/restoration in the event of a crash or roll back": do not count on getting back what a disconnection cost you.

What to do when you are stuck on "Logging in to game server"

  • Check first whether the problem is Blizzard's. Our server status gathers Blizzard's posts on the realms and leads to Blizzard's own status page, which shows each realm live.
  • During an attack, nothing on your side fixes it. Repairing or reinstalling the game changes nothing: wait for the servers to come back, then log in again.
  • An error code at login? Our error codes page explains WOW51900309 and the other messages of WoW Forever's login screen.

What we don't know

  • Who attacked Battle.net, and why.
  • Whether the disconnections of the evening of November 12 came from the same attack.
  • Whether it is over: Blizzard has posted no all-clear. The previous outage, on November 9, is in our article on it.

TagsWoW ForeverDDoSBattle.netservers downLogging in to game serverserver status

Frequently asked questions

Was WoW Forever hit by a DDoS attack?

Yes. On November 12, 2026, at 01:23 UTC, Blizzard's Customer Support confirmed "a DDOS for all games". WoW Forever players were disconnected from about 00:57 UTC and wrote that they were back in from 01:52 UTC.

Why am I stuck on "Logging in to game server" in WoW Forever?

During the attack, Blizzard's servers could not let players in: nothing on your side fixes it, and repairing or reinstalling the game changes nothing. Check our server status page, wait for the servers to come back, then log in again.

Did Blizzard explain the disconnections of the evening of November 12?

Not in what we read. No Blizzard post in the forum threads, nor on its Customer Support account on Bluesky, explained the wave of disconnections that began at about 21:15 UTC.

Will Blizzard give back what I lost in a disconnection?

Do not count on it. On November 12, Blizzard's Customer Support wrote that it "is generally unable to provide compensation/restoration in the event of a crash or roll back".

Sources

  1. Blizzard Forums (Americas) — What are the solutions? Wow Forever: Vrakthris (Customer Support) confirms "a DDOS for all games" (November 12, 2026, 01:23 UTC)
  2. Blizzard Forums (Americas) — Disconnected in WoW Forever and Cannot Log Back In (players, November 12, 2026, 00:57 to 01:54 UTC)
  3. Blizzard Forums (Americas) — a player quotes the Battle.net app's DDoS warning (November 12, 2026, 01:32 UTC)
  4. Blizzard Forums (Americas) — Servers down. AGAIN (the second wave, November 12, 2026, 21:15 UTC)
  5. Blizzard Forums (Americas) — I want my gold back!: Customer Support on compensation after a crash or rollback (November 12, 2026, 02:11 UTC)

Also inDeutschEspañolEspañol (México)FrançaisItalianoPortuguês (BR)Русский한국어简体中文繁體中文

  1. WoW Forever servers down on November 9: what we know

    WoW Forever's servers went down in the Americas and Europe at about 21:45 UTC on November 9, murlocs blamed in game: what players saw and when they got back in.

    Nov 10, 20261 min read

  2. WOW51900309, WOW51900337: WoW Forever error codes and fixes

    No realms available (WOW51900309), no valid license (WOW51900337), no game time, a full queue: WoW Forever's login errors as the game writes them, with fixes.

    Nov 5, 20265 min read

  3. Playable Ogres in WoW Forever? What Blizzard actually said

    In episode 7 of the WoW Forever podcast, Blizzard called the Riverglades ogres the Horde's new allies. No playable race announced: the exact quote and minute.

    Nov 14, 20262 min read