While we’re waiting for the servers to come back up (again), Blizzard has announced that there were over 2 million pre-orders made for Diablo III with over 8,000 launch events across the world. Blizzard is reporting that Diablo III was their largest pre-order success to date and Amazon is backing that claim as well saying it was their most pre-ordered game of all time. I’ve always been a huge fan of the Diablo Universe, but I’m surprised to see the massive amount of attention the game is getting from the mainstream public. There’s always been a fairly large following for Diablo, but this launch has taken it to an entirely new level.
With all of that attention, all of those pre-orders, and all of those midnight launches I expected there to be issues when it came time to log into the game for the first time. It seems I was right (not exactly a psychic pick) and there have been errors since the very moment the servers came online. We’re catalogueing all of the Diablo III Launch Error Codes as we learn more about them, and Error 37 has even been seen trending on Twitter world wide it’s been so common. Unfortunately there’s no real solution for Error 37 so just keep trying.
As of 2:16 PM PST on launch day, Blizzard took the servers offline to perform emergency maintenance and continue to deploy more servers. They’re expecting to see the servers back online around 3:30 PST, and they’re hoping to be prepared for the onslaught of log ins this time.
Update: The servers are still causing problems and have gone down again around 8:30 PST.