Skip to content
wowforever.ninja

News

What broke on beta launch day

Tom Ellis explained the beta's rough first night: a PTR-sized setup, choked logins and a slow database.

Confirmed Published Updated How we tag claims
  • community
  • beta

Senior Game Producer Tom Ellis posted a lengthy account on X explaining the rough opening hours of the World of Warcraft: Forever beta, which launched with disconnects, long queues and slow loot and quest interactions.

Ellis said the beta runs on a PTR-scale environment, not a production one, which was the root of several issues. Players were disconnected after passing the Battle.net login queue because the beta used a single regional realm whose two connections were overwhelming a Battle.net service-protection system, even though CPU and memory looked fine; Blizzard scaled that up to eight connections to fix it. Slow looting and quest interactions traced back to the beta’s database needing a manual analysis pass and new automated jobs to keep up with heavy new-table activity. Later in the day, Blizzard restarted the beta to fix a bug where empty zone instances weren’t shutting down properly and were slowly consuming server memory, and added extra world server capacity at the same time.

Why it matters: the launch-day problems came from beta-scale infrastructure rather than a fundamental issue with the game, and Blizzard says the fixes hold going forward.

Tracked on everything we know.

Sources

  1. Wowhead — Tom Ellis's X thread on the beta launch issues https://www.wowhead.com/news=382993