World of Warcraft has been running for 22 years, and even now Blizzard sometimes struggles to keep up with demand. Yesterday, the WoW: Forever beta launched and immediately broke under the weight of everyone trying to get in at once. How is this still happening when Blizzard has decades of experience with launching new MMO content? The devs themselves say they were genuinely taken aback by just how popular the Forever beta has been.
"Man, it was hard to sleep last night, I was so excited," senior game designer Josh Greenfield says on Twitter. "Beta has been... crazy. The craziest numbers I've seen in 17 years working at Blizzard and almost 8 years on classic. We've got something really special here."
Maybe that sounds hyperbolic, but senior game producer Tom Ellis has posted a more exhaustive technical breakdown of what went wrong for the opening hours of the Forever beta. "It's not a Production stack by a long, long, long, long, long, long shot," Ellis explains on Twitter. "Betas for WoW aren't usually huge meter movers so this environment just isn't that powerful."
Because "our little BETA environment only uses one REGIONAL realm," Ellis says, math on the servers started getting screwy as this one little connection point was suddenly having to funnel in so many players. This is why people kept getting disconnected after sitting through the lengthy login queues.
It took the devs "around half an hour" to figure out that this was the bottleneck, because the game and Battle.net services both showed very little load. "We all recognized we need more logging and notifications when this system is kicking in, but this is the first time anyone's seen it kick in when [there] wasn't an obvious CPU issue to go along with it," Ellis explains. "20 years, always something new."
Alright, now the dust has settled and you're just happily playing away, let's answer the most common question I've seen.1. AHMAGERD, this game is 20 years old, how do you still suck at this!?!a. Heh, fair enough, sort answer is, this is our BETA PTR environment stack, it's not…September 18, 2026
Ellis also addresses the long times players were experiencing while looting, accepting quests, and performing similar server-bound actions. "Our intrepid Oracle Database Engineers had to perform a manual analyze on all the tables and setup some automated jobs to periodically keep doing it," but because the servers were being hit so frequently, the typical rate wasn't sufficient. As soon as the devs addressed that, the database performance "cleared up instantly."
There were the restarts. "A few hours in, we noticed our WORLD pools that run, well, the game simulation you play on, were running crazy hot on CPU and almost out of memory," Ellis explains. Empty maps were not being correctly shut down, and those were slowly – or, actually, "not that slowly" – clogging up CPU and memory on the servers. The devs figured out a fix, but that fix needed restarts "to pick it up." Blizzard also took the opportunity to add additional worlds and expand the regional service for further stability.
Back in 2019, we interviewed numerous devs about why big online games always seem to break at launch, and it seems that all the same problems inevitably crop up. We heard one dev say "it's just impossible" to fully solve these kinds of launches, and WoW: Forever demonstrates how new issues crop up every single time. But hey, at least the fixes are coming faster. I'm old enough to remember when people were struggling to play Diablo 3 for weeks after launch…
