Your character didn't die and your connection didn't drop — you're just staring at the "Logging into game server" spinner. On the afternoon of November 9 Beijing time, a wave of WoW: Forever US players hit exactly that at the same moment, and someone on the official forums came right out and said it: WORLD SERVER DOWN. Between 15:56 and 16:01 Beijing time (07:56-08:00 UTC, 2:56-3:00 a.m. Eastern), five separate threads appeared in the forums' Forever category within five minutes — none of them quoting each other. It was day 5 after the game's global launch on November 5.

Five threads, five minutes, every ruleset hit

The first two posts set the tone. One is titled "Riverglades is crashing peoples clients on atleast 1 layer," with the opener reporting that players simply cannot log back in; the other is called "Wtf blizz you made with server." Four minutes later, the WORLD SERVER DOWN thread and a thread named Constant Lag followed.

The symptoms fall into three buckets: lag, chain disconnects, and failed relogs. One player who had not had a single connection issue since launch logged about 11 disconnects in the 30 minutes after landing in the Barrens. A player running Blackfathom Deeps dropped three times and got stuck on the login screen on every retry. The Constant Lag opener described lagging all day, 5-6 disconnects, and chat so broken that messages sat silently and then all appeared at once in a half-second gap.

The blast radius was wider than one server type: PvP, PvE, RP-PvP and the normal ruleset all had reporters, and the locations span Ohio, New Jersey, Rhode Island and the West Coast. But not everyone was hit — "this is happening to me and 2 of my friends," the PvP thread's opener wrote, noting that some players never disconnected at all. In that BFD group, only the one player had trouble.

Riverglades: one layer, crashing clients

The most specific of the five threads points at Riverglades: its opener says the zone crashes clients on at least one layer, and that players who get hit can't log back in. The timing lines up — another player disconnected mid-flight from Riverglades to Stormwind and sat stuck at the login screen, and a PvE player suspected he had glitched out inside Riverglades.

But someone in the same thread pushed back immediately: it's not the location, it's the server itself misbehaving — and that skeptic had been dropped three times in ten minutes. Whether Riverglades is the epicenter is something even the players there couldn't settle. The zone is Forever's own content: Wowhead's November 6 hotfix roundup lists it zone-by-zone (fixing Krek the Noxious's loot), and Blizzard's own interview circuit has described The Riverglades as a storyline interplaying with Warcraft II.

No word from Blizzard, but some players got back in

As of writing (16:12 Beijing time), none of the replies across the five threads came from Blizzard staff — checked thread by thread at the time and re-checked later against a full 60-post archive. Wowhead, MMO-Champion and Massively Overpowered carried nothing on the outage — Wowhead's newest Forever item was still the dungeon experience buff. No cause, no scope assessment, no fix timeline: all not announced. One player relayed a Reddit claim that EU Classic servers were going through the same thing; that remains unverified forum hearsay.

What is confirmed: people were getting back in. At 16:06 a player posted that they had just logged in with their character alive, and at 16:10 the WORLD SERVER DOWN opener made it back into the game. Both waited a few minutes before their login went through.

This is the third strike of launch week: day 2 brought duplicated NPCs and mobs across layers, day 4 (November 8) the half-merged harpy cave layers in Thousand Needles, and now this. Whether layering is involved this time, Blizzard has not said.

Stuck at the login screen? Wait a few minutes first

Don't hammer the login button. The two players who got back in both succeeded only after waiting several minutes — retrying nonstop against a downed world server just burns time.

Three smaller things: chat messages arriving in a burst aren't lost, so don't retype them; your connection and PC are probably fine — one reporter was dropped repeatedly at 23 ms; and if you're in a dungeon group, don't bail — you may be the only one in the party who got dropped.

Cause, scope and fix timing are all unannounced. The first blue post or service notice will be the real signal that this is being fixed — until then, the newest threads in the forums' Forever category are the most live outage map there is.