Resurrected's server issues in the last few weeks have D2R Items gotten more severe. This culminated in several instances of downtime in the past week. the entire outage could be attributed to, Blizzard say, by an increase in traffic. "This was a new threshold that our servers hadn't encountered before, and not even at launch," reads the post on the Blizzard forums.
This was compounded due to an update that we implemented earlier that was designed to boost performance around game creation-these two factors combined led to a massive overload on our global database and caused it time out. We chose to roll back that Friday update we'd already deployed, hoping that would ease the burden on servers through Sunday while also giving us the space to dig deeper into the root cause."
It turned out that rolling back the patch wasn't enough. Sunday saw an even higher growth in traffic and servers again crashed. This time on Monday. This post is long and admirably thorough in its explanation of the reason for this.
But particularly Blizzard attribute the problem to the legacy code associated with creating and joining games and also to reading data from the database. "We did optimize this service in a variety of ways to conform to more technologically advanced technologies, but as we've said before, a lot of our problems stem from the game's creation," says the post.
This is the point where we can move to player behavior. "We discuss'modern-day player behavior" as it's an interesting point to think about. As of 2001 there weren't as much material on the internet about ways to buy diablo II resurrected items play Diablo II 'correctly' (Baal runs for XP, Pindleskin/Ancient Sewers/etc for magic find, etc).
