Senior game designer Josh Greenfield called the turnout “the craziest numbers I've seen in 17 years working at Blizzard,” describing a level of beta participation far beyond the team's forecast.
What happened at launch
Players encountered crowded login services, queues, unstable world connections and repeated disconnects after the beta opened on September 17. European players were among those reporting very high world latency during the first day. Blizzard applied server-side changes, and later reports indicated that the worst regional connection problems had eased.
The beta environment is built for testing rather than launch-scale traffic. Blizzard expected participation to grow over the test, but the immediate concentration of players put account services and game worlds under pressure at the same time.
“The craziest numbers I've seen in 17 years working at Blizzard.”
Josh Greenfield, senior game designer
Why the problems matter
Queues and disconnects are disruptive, but they also expose capacity limits before launch. Login flow, world stability and regional network routing can now be tested under unusually heavy load while the game is still in beta.
A separate Server Slam has been announced as part of the testing plan. Its purpose is to concentrate players and stress the infrastructure again. No exact date or start time has been announced, so players should wait for the in-game launcher or an official schedule before planning around it.
What players can do
- Check the Battle.net launcher and beta forum for service notices before changing local settings.
- Expect queues during peak hours while population and capacity are adjusted.
- Report repeatable disconnects with region, time and error details through the beta channels.
- Do not treat beta stability as a forecast of final launch performance; the infrastructure and software are still being tested.