May 15, 2012
After 12 years of waiting, it looks like Diablo 3 players still need a bit more patience on their return trip to Tristram.
Unbelievably, the hashtag #Error37 has been trending worldwide on Twitter. Many Diablo 3 players have sought refuge on social media websites after the horrible error has appeared countless of times on the login screen. Error 37 is a typical error that pops up whenever the game is unable to login your account after more than 40 seconds, prompting it to time out.
As stated in the Diablo 3 Launch Day Preparation Guide officially released by Blizzard, they did imply login delays are a possibility and the likelihood of Error 37 is always nearby. Players experiencing the error are advised to re-login when the error appears. Blizzard also states this in a sudden press release:
Welcome to Diablo III! The fight for Sanctuary has begun.
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.
Blizzard is now taking the hit for the login-related problems, stating that “they haven’t learned from World of Warcraft’s release.”
For Diablo players, their quest has already begun with the conquering of Error 37.
Head on to the official Diablo 3 forums for guidance on how to escape the wrath of Error 37. Or if you’re patient enough, wait a bit more until Blizzard’s servers become stable enough to let you in.
What other Errors are you encountering? Share it to us on the comments below, and tell us how you were able to solve it!
UPDATE: @BlizzardCS (from Twitter) sent in this link, briefly explaining what to do when encountering Errors 37, 3005, 3006 and the character creation bug.
Official Diablo 3 Website