Skip to content
WOW FOREVERBuilds • Guides

WoW Forever News · beta · servers · known-issues · wow-forever

Why the WoW Forever beta broke: one regional realm, a choking database and 'the craziest numbers in 17 years'

Senior game producer Tom Ellis has explained why the WoW Forever beta kept disconnecting players on day one. The beta runs on a small test environment with a single regional realm, which became the bottleneck. Slow loot and quest actions came from database tables that needed manual tuning, and the rolling restarts fixed empty maps that were eating server memory. Josh Greenfield called the turnout the craziest numbers he has seen in 17 years at Blizzard. Blizzard also added five new known issues.

By the WoW Forever Builds News Desk ·

Dwarf and gnome engineers struggling with an overheating giant machine beneath Ironforge while adventurers queue outside
AI-generated illustration, not in-game footage.

The queues and disconnects that greeted the WoW Forever beta on September 17 now have an official explanation. Senior game producer Tom Ellis posted a technical breakdown on social media, reported by GamesRadar+. The short version: Blizzard ran the beta on hardware sized for a normal beta, and this was not a normal beta.

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

Senior game designer Josh Greenfield set the tone: “Beta has been… crazy. The craziest numbers I’ve seen in 17 years working at Blizzard and almost 8 years on classic.”

Ellis explained why that hurt. The beta runs on Blizzard’s test environment, which he said is “not a Production stack by a long, long, long, long, long, long shot.” In his words, “Betas for WoW aren’t usually huge meter movers,” so the environment was never built for this kind of crowd.

Three problems, three fixes

Ellis described three separate issues, which match what players saw in the first hours.

1. Disconnects after the queue. The beta uses one regional realm, and that single connection point could not handle everyone logging in. That is why players who got through a long queue were often disconnected right away. The game servers and Battle.net services showed almost no load, so it took the team about half an hour to find the cause. Ellis said they need better logging for this system: “20 years, always something new.”

2. Slow looting and quest turn-ins. Server-side actions such as looting and accepting quests lagged because the database could not keep up. Blizzard’s database engineers ran a manual analyze on every table and set up automatic jobs to repeat it. Once that was in place, Ellis said, performance “cleared up instantly.”

3. The restarts. A few hours in, the world servers were running very hot on CPU and nearly out of memory. Empty maps were not shutting down properly and kept using resources. The fix needed server restarts to take effect. Blizzard used those restarts to add more world servers and expand the regional service.

What it means for the EU lag

The “one regional realm” detail also explains the other big complaint. It is more evidence that the beta runs from one location in North America, which is why European players saw 2,000 ms spikes that a US VPN fixed. Ellis did not mention EU routing, so that remains a player workaround.

It also matters for November. Launch will run on the production stack with regional realms, not this test setup, so this weekend’s problems do not tell us much about launch day. The beta’s size does, though. Blizzard now knows how many people want to play, and says it has been expanding capacity.

Five new known issues

Kaivax updated the official known issues list on September 18 with five additions:

  • The Cooldown Manager is a work in progress and varies from class to class.
  • Bear Form multiplies armor bonuses from consumables and buffs, so Druid tanks are sturdier than intended for now.
  • Queueing an on-next-attack ability (Heroic Strike, Cleave, Raptor Strike) disables your spell queue window.
  • Taking damage while channeling Arcane Missiles fires a full-damage bolt instead of a shortened one.
  • Resurrection sickness lasts the wrong length of time at low levels.

The Bear Form and Arcane Missiles bugs both make those classes stronger than intended. Keep that in mind if you are judging class balance at level 20.

Not on the list yet

Two player-reported problems are worth knowing about:

  • Addon and UI settings reset on every restart. Players report that the client writes SavedVariables files but never reads them back, on Windows and Linux, even with no addons installed. Every addon’s configuration is lost between sessions. If an addon seems to forget its setup, this is why. The same applies to our WoW Forever Builds addon.
  • “Overtuned and Too Fast.” The biggest feedback thread of the day, with more than 120 replies and 260 likes, adds to the day two debate about leveling. It argues that new abilities, talents and re-itemized gear have made characters too strong for the original world, and asks for slower leveling and no experience-boosting buff food. Not everyone agrees; some Classic players say leveling was always too slow. Blizzard has not replied yet.

Developer quotes from GamesRadar+, which reported posts by Josh Greenfield and Tom Ellis on September 18, 2026. Known issues from the official beta forum; player reports from the SavedVariables and “Overtuned and Too Fast” threads.

Sources

How this article was made: drafted with AI from the sources listed above, then checked and edited by the WoW Forever Builds team before publishing. WoW Forever Builds is a fan site and not affiliated with Blizzard Entertainment.

More WoW Forever news

All news →