Blizzard says WoW: Forever beta demand overloaded its smaller test setup

The WoW: Forever beta hit trouble shortly after opening, with players running into long queues, disconnects, loot lag, and server restarts. Blizzard says the main issue wasn’t a normal live-service launch meltdown, but a beta environment that was far smaller than what the demand required.

Senior game designer Josh Greenfield said on X that the beta produced “the craziest numbers” he’s seen in 17 years at Blizzard. Senior game producer Tom Ellis followed with a more technical explanation, saying the beta stack “isn’t a Production stack” and wasn’t built for this many players trying to get in at once.

According to Ellis, WoW betas usually don’t move numbers like this, so the Forever beta was running on a limited regional setup. That caused Blizzard’s login metering to behave badly even though Battle.net and the game services didn’t appear to be under heavy CPU load. The team eventually found the bottleneck and increased the number of regional connections, which let more players through.

Blizzard also had to deal with slow server actions, including looting and accepting quests. Ellis said database engineers manually analyzed the PTR database tables and set up recurring jobs to keep them updated. Once that was handled, the database performance improved quickly.

The restarts came from a separate problem. Empty maps weren’t shutting down correctly, which pushed the world servers toward high CPU usage and low memory. Blizzard deployed a fix, added more world capacity, and expanded the regional service to stabilize the beta.

It’s another reminder that even a 20-plus-year MMO can still run into new launch-day problems, especially when a test environment suddenly gets treated like a live release. The good news for players is that Blizzard has already identified the major issues behind the rough opening stretch.