Diablo III’s Error 37: "Don’t Call It A Comeback!"


Last Night, Diablo III‘s Error 3003 may have been hot, but tonight, it looks like Error 37 is making a comeback!

Like Derek Zoolander himself, Error 37 has risen from the ashes of last night’s failed walkoff with so-hot-right-now upstart Error 3003 and emerged once more as the dominant Diablo III error. The original and best, as it were.

At least now, Blizzard has set up a helpful server-status page so you can know for sure that you really and truly can’t play the game right now.

Which you can’t. For the third night in a row.


The Cheapest NBN 1000 Plans

Looking to bump up your internet connection and save a few bucks? Here are the cheapest plans available.

At Kotaku, we independently select and write about stuff we love and think you'll like too. We have affiliate and advertising partnerships, which means we may collect a share of sales or other compensation from the links on this page. BTW – prices are accurate and items in stock at the time of posting.

Comments


39 responses to “Diablo III’s Error 37: "Don’t Call It A Comeback!"”

Leave a Reply

Your email address will not be published. Required fields are marked *