WoW Forever Beta Overwhelms Blizzard’s Servers as Devs Marvel at ‘the Craziest Numbers’ in 17 Years

World of Warcraft has been running for 22 years, and Blizzard still got caught off guard. The WoW: Forever beta went live and immediately buckled under the crowd trying to get in, with long login queues and players getting booted right after they finally connected. The twist is that the devs were not annoyed by it. They were stunned by how many people showed up.

“The craziest numbers I’ve seen in 17 years”

Senior game designer Josh Greenfield summed up the mood on Twitter. He said it was hard to sleep, that the beta had been “crazy,” and that these were “the craziest numbers I’ve seen in 17 years working at Blizzard” and almost eight years on Classic. His read: “We’ve got something really special here.”

That reaction lands differently when you remember what Forever actually is. This is not a small patch, it is a whole new way to play the vanilla era, a fresh WoW game due to launch in November. A beta breaking records months ahead of release is the clearest signal yet of how much pent-up demand is sitting behind it.

Why the servers kept breaking

Senior game producer Tom Ellis, who posts as @FwoiblesWoW, followed up with an unusually detailed breakdown of what actually went wrong, and it is a great look under the hood of a live MMO.

First, the beta does not run on Blizzard’s full production hardware. As Ellis put it, “betas for WoW aren’t usually huge meter movers,” so the environment simply is not that powerful. The beta also uses only one regional realm, and that turned out to be the real problem. The Battle.net system that meters logins to protect itself from overload got thrown off by so many players funnelling through that single connection point, even though the actual CPU and memory were barely being touched. That mismatch is why people sailed through the queue and then got disconnected. It took the team around half an hour to find, because every dashboard looked idle. Scaling that connection from two up to eight opened the floodgates again.

Next came the database. Looting, accepting quests and anything else that touched the database started crawling, so Blizzard’s Oracle engineers had to manually re-analyse the tables and set up jobs to keep doing it, because brand-new tables were being hammered with far more activity than usual. Then the world servers that run the actual game simulation started running hot on CPU and nearly out of memory, because empty maps were not shutting down properly. That one needed a full restart to fix, and Blizzard used the downtime to add more world servers for good measure. Ellis’s summary of the whole night: “20 years, always something new.”

A very good problem to have

A launch that breaks the servers is never the plan, but a beta that breaks them is close to the best news Blizzard could ask for right now. It means the interest in Forever is real and large, and it means the team gets to find and fix these bottlenecks now instead of on launch day in November. As Ellis noted, by the end of the night things were running smoothly for the first hours of a public beta, which is not something you could always say about a big Blizzard launch.