In 2001, there wasn’t nearly as much content on the internet around how to play Diablo II 'correctly' (Baal runs for XP, Pindleskin/Ancient Sewers/etc for magic find, etc).

'We mention 'modern player behavior' because it’s an interesting point to think about. Which is where we move into player behaviour. 'We did optimize this service in many ways to conform to more modern technology, but as we previously mentioned, a lot of our issues stem from game creation,' says the post.

The above linked post is long and admirably detailed in its breakdown of why this happening, but in particular Blizzard place the blame on some legacy code related to creating and joining games, and reading characters from the database. Sunday saw an even higher surge in traffic and the servers fell over again.

We decided to roll back that Friday update we’d previously deployed, hoping that would ease the load on the servers leading into Sunday while also giving us the space to investigate deeper into the root cause.'Īs it turned out, rolling back the patch wasn't enough. 'This was exacerbated by an update we had rolled out the previous day intended to enhance performance around game creation–these two factors combined overloaded our global database, causing it to time out. 'This was a new threshold that our servers had not experienced at all, not even at launch,' reads the post on the Blizzard forums. This culminated in several instances of downtime in the past week, where a global outage was caused, Blizzard say, by a surge in traffic.

Resurrected's server issues over the past couple of weeks have seemed to get worse. Today, a Blizzard community manager offered some insight into the nature of the problem - and it's partly some 20-year-old code, and partly some modern player behaviour. Diablo II: Resurrected launched to widespread and ongoing server issues.

Diablo 2 resurrected private servers