Diablo 3 server status upsets fans
The current Diablo 3 server status is not going down well because not being able to play a game that has been years in the making has not surprisingly upset fans. We are not that shocked that Blizzards servers crippled under the pressure, because demand would have been immense, something that we know only too well with some of the Call of Duty titles when they first launch.
Players hoping to take their copy of Diablo 3 home and then start playing (after downloading and installing patch 1.0.1) would have received a “error37” message, which as we know means that the connection has failed. Looking at the Diablo III server status it’s clear to see that there are still a few issues, not with the game servers themselves but the Auction House for each region.
It’s no surprise that #error37 was a trending topic on Twitter and as such brought with it a multitude of negative comments regarding Blizzard; this makes us wonder what Blizzard would do if they released Diablo III on consoles like they are rumored too, as demand would be much higher than it currently is on the PC?
You would have thought that Blizzard would have had their house in order, because the game has been over a decade in the making and they knew that demand would be huge. If memory serves us well during April beta tests servers were also causing error37 for many of those who took part.
While it may not come as any comfort Blizzard has apologized and said that the issue should fade over the next 48 hours, as demand will not be as high like it is now on launch day.