Early Diablo III gamers plagued with Error 37
Diablo fans flocked to their nearest game store today, or downloaded the digital version days before, to be among the first to play Diablo III. Unfortunately to a lot of these gamers, they can’t even get past the login screen with Blizzard giving them an Error 37.
The Error 37 messages is given when your connection times out after 40 seconds due to the overwhelming volume of users attempting to authenticate the game. All you can do is keep trying until successful.
“Due to high concurrency the login servers are currently at full capacity,” Blizzard said in a statement. “This may cause delays in the login process, account pages and web services. We apologise for any inconvenience this may cause and thank you for your patience while this is being resolved.”
Please note that due to a high volume of traffic, login and character creation may be slower than normal. If you’re unable to login to the game or create characters, please wait and try again. We’ve temporarily taken our Battle.net websites offline and launched more servers to accomodate for the traffic. We hope to resolve these issues as soon as possible and appreciate your patience.
It’s unfortunate that this has to happen again given that it also happened during the first few hours of Diablo II back in 2000. Fortunately before, players can play the single player mode offline to allow Blizzard to sort their servers out. With Diablo III, players need to be connected online whether playing alone or with friends since characters are only stored online.