Diablo III's #error37 trending on Twitter

Ben Parfitt
Diablo III's #error37 trending on Twitter

The world of PC gaming was jubilant last night as Blizzard’s Diablo III finally hit the High Street… only for the developer’s servers to crash almost immediately.

And is there anything more indicative of modern PC gaming than owners of a high-profile single player release being unable to play their title because of a server failure?

Error 37 is the message presented to players attempting to start the game when, in Blizzard’s words, “your connection [to the Diablo III servers] doesn’t succeed in 40 seconds”.

And despite the studio’s preparations, the number of playing trying to log on has brought the servers to their knees.

It’s all the more frustrating, of course, as Diablo III is not an online title. The game is simply trying to authenticate itself on the official servers.

“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.”

At the time of writing #error37 is a trending topic on Twitter worldwide, and one canny interneter has already opened a @error37 account.

MCV’s advice? Give it a couple of days and all will be well.

Advertisement

Tags: blizzard , servers , diablo iii , Login , error 37 , #error37

Follow us on

  • RSS