Diablo III’s Error 37 has gained much notoriety following the game’s launch back in 2012 but newer players that joined the Nephalem ranks later might be wondering what it’s all about.
Here’s everything you need to know about what Diablo III’s Error 37 means and whether or not there’s a fix or any sort of workaround for it.
Diablo III Error 37
Diablo III’s Error 37 plagued a large part of the hack-and-slash RPG’s playerbase when the title first launched. Its full error text reads as follows: “The Servers are Busy at this time. Please try again later. (Error 37)”.
As the message suggests, Error 37 is caused by the Diablo III servers struggling under the weight of too many players trying to log in. Back in 2012, this led to long queues which many players still remember to this day.
The bad news is that if you’re encountering Error 37 now, you’ll have to do what veterans did during Diablo III’s launch and simply wait it out.
It’s not an elegant solution but sooner or later you’ll be able to jump in and show Hell’s denizens just how much you despised the wait.
Diablo III is out now on PC, Xbox One, PS4 and Nintendo Switch.
