Diablo III: Error 37 brings down Lord of Terror

Well, Diablo III has been in the wild for a full 24 hours now, and Blizzard is only now starting to recover from bringing the entire internet to a screaming, violent halt yesterday at midnight Pacific.

Apparently, when you have more than 2 million pre-orders (Diablo III is officially Amazon's most pre-ordered game ever, by the way), it's understandable that many of them may want to get online and play the game immediately - and Blizzard's hardware just wasn't able to cut it, promptly falling over as soon as the game went live.

Blizzard CEO and cofounder Mike Morhaime's glowing launch presentation rings a little hollow now, following the events which took place:

This launch is a culmination of many years of hard work by our development team, and many years of passionate, dedicated support from gamers around the world. We’re grateful for the enthusiasm of our players, and for the help of our beta testers in getting the game ready for release.

Now that Diablo III is live, we hope everyone’s ready to have a hellishly good time slaying demons and collecting loot in Sanctuary.

The failure to launch was so comprehensive that, for a while, there were three Diablo III error codes in the trending topics on Twitter, with #error37 the most prevalent.

Traditionally with this situation, when a game's servers don't cope well with initial strain, fans simply load up the single-player mode to slog through that until demand lessens.

The problem with Diablo III? Even the single-player requires a connection to the Blizzard Battle.net servers, so that wasn't an option either.

Diablo III

Diablo III

Apparently, after nearly a full day of trouble, Blizzard's engineers have gotten on top of the problem with all three server regions back online. How long they remain is a different question.

If you'd still like to check out what all the fuss is about, head to the game's official website and grab a digital copy. From all reports, once you're actually able to play, it's been worth the (12 year!) wait.

Why not check out our latest vidcast!
Player Attack TV: September 25 2015, SE3 EP30 or subscribe to our YouTube channel.

  • Twitter
  • Facebook
  • email
  • Delicious
  • Google Bookmarks
  • Myspace
  • Digg
  • Reddit
  • StumbleUpon
  • N4G
  • Follow us on Twitter or like us on Facebook

Get The Latest Episode News
Email Address

4 Responses to “Diablo III: Error 37 brings down Lord of Terror”

  1. […] logging into EVE Online have been faced with an unusual error code, just like the ones plaguing the somewhat bumpy launch of Diablo III this […]

  2. […] the dust now settling after Diablo III's rocky launch, intrepid fans are starting to find bits and pieces tucked within the game – and the upcoming 1.0.3 […]

  3. […] also fair to say that Torchlight 2 enjoyed a happier, more satisfying launch. Some would argue that Diablo's launch woes actually drove eager gamers into the waiting arms of Torchlight 2, which was timed to offer […]

  4. […] has been one year since Diablo III hit shelves – and from a shaky, unpleasant start, we've seen Blizzard hack'n'slash rise up to become one of the highest-selling PC games of all […]

Leave a Comment

Player Attack Fri 9pm, Aurora

Article Details

Author Bio:

I like video games and music and cups of tea and noodles and beagles and colour-cycling LEDs.
Like me on Facebook?

Popular Articles

Subscribe to our Youtube channel and get all the latest TV episodes.