This legacy code affects things like game creation and joining, basic functionality, reading character data, updating/reading/filtering game lists, verifying server health, and more. Large portions of the game’s code, at least for certain processes, are essentially the same as they were when the original was released two decades ago. With more players logging in now than when the game launched, Blizzard’s servers are having a hard time keeping up.īut by far the biggest problem that Blizzard points out has to do with how Diablo 2: Resurrected was made. Diablo 2: Resurrected is still hitting new high watermarks for player-count as recently as last week. One problem that might seem surprising is the sheer number of players that Blizzard is dealing with. After more than a week of crashes and outages, Blizzard has released a long and in-depth blog post describing the issues, what’s causing them, and how its team plans on fixing them.Īll of the Diablo 2 remake’s server problems are being caused by a series of smaller issues stacked on top of each other, Blizzard’s post explains, which means there isn’t just one solution to fixing them.

Diablo 2: Resurrected has had server issues since it launched last month, but recently they’ve gotten even worse.

Error 22 diablo 2