"On Friday morning Pacific time we had a global outage due to an abrupt increase in traffic with D2R Items. This was a first-time threshold which our servers have never ever experienced, in fact, not even prior to the launch," Blizzard explained.This was amplified by an update we'd made available earlier in the day with the intention to improve performance during game creation. Both factors together overloaded our database globally, causing it to crash. We were able to reverse the Friday update, which we'd previously rolled out in the hope of easing the burden on our servers leading into Sunday while also giving us the space to look into the root of the problem.

On Sunday, however it was clear that what we had done on Saturday was not enough-we saw an even higher volume of traffic, which caused us to hit another interruption. The game servers were monitoring the disconnect from the database and attempted to reconnect repeatedly, which meant the database didn't have time to complete the work we'd completed since it was busy taking care of a constant stream of requests to connect by game servers. In this period, we also saw we could modify our configuration to improve our logs of events in the database, which is essential to restore the health of the database in case in the event of a database failure. So we completed those, and conducted further investigation to determine the root cause.

This isn't exactly the recipe for having a great time, that. It's also why the players were experiencing lots of issues with playing progress. It was easy to pick a character, begin a game and then play for some time but the regional server could not communicate with the central database because of an downtime. This meant it wasn't able to tell Diablo 2's source of "ground truth" about the latest gear and XP you'd earned, making frustrated players lose some of the progress they'd made.

The problem only got worse as time went on. There was an issue when the Diablo 2 servers came back up and running, but they did so at a time when most players were online--so although the servers re-established rapidly, they crashed nearly immediately after hundreds of thousands of Diablo 2 instances fired up.

If the weekend went badly it was followed by a miserable Tuesday and Monday wasn't much better. We're currently on Monday, October 11 in which we made changes to the global databases. The result was another outage as our backup database was incorrectly continuing to run its backup process. That means that it was spending most of its time trying to copy from the other database , while it should have been handling requests from servers.

During this time, we discovered further issues, and we made further improvements-we found a since-deprecated-but-taxing query we could eliminate entirely from the database, we optimised eligibility checks for players when they join a game, further alleviating the load, and we have further performance improvements in testing as we speak. We also believe we've fixed the problems with database reconnects that we were experiencing, as we didn't see it occur on Tuesday.

This is the time when I'm constantly hearing my brother's advice: "Never get into networking."Diablo 2 Resurrected down to Maintenance on May 17th, 2017 If you're trying logging in for Diablo 2 Resurrected and aren't be able to, it's not because Blizzard has started Diablo 2 Resurrected Items Resurrected down, and this is scheduled maintenance on May 17.Diablo 2 Resurrected Down Status and Updates for May 17:The delay is expected to run for two hours, though this may last longer (as they do sometimes).