Diablo 2 Woes

Over 9 years ago, Blizzard launched Diablo 3. I was there at launch, and for over a month there was the dreaded Error 37, preventing all play. A few months after that, SimCity launched with a similar model and collapsed almost entirely under it’s own weight with the same issue. 9 years ago the interwebs were dealing with the inability to scale their servers.

This is 2021 and Diablo2 servers have been up and down for a month since launch. No skin off my back, I’m done with Blizzard for the foreseeable future, but I also don’t live in a cave to ignore a behemoth like Blizzard not figuring this stuff out. And to be clear, it’s not like Blizzard wants to disappoint players.

I did post a while back about cloud architecture, and how Blizzard runs a hybrid model to manage peak load, for non-sensitive components. Authentication is one of the sensitive bits, for a billion reasons, and not something a AAA company would want to put in a “public” cloud. There are “private” cloud offerings, which are an interesting conversation on their own. I am not a Blizzard network engineer, so this is all speculation here based on prior experience. I am not at all saying this is easy, even less so when you are trying to re-jig (*checks notes*) 21 year old-code.

And yet, this reads like more bad news on a company that can’t really seem to find much positive to report. In some alternate world I’d feel bad for kicking a company while it’s down… but this is really all self-inflicted.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s