In the end, all of these servers have their own regional databases which store the information of the characters playing on them. This is because there are too many people playing D2R Items to just continually upload all of their data to one central, single point.

"Most of your game actions are carried out against this regional database as it's more efficient, and your character is 'locked by the regional database to preserve the individual character record integrity. The global database also includes backups in case the main database fails,"These regional databases periodically send info back into the central database so that way Blizzard has a singular record (with backups) of your thicc Level 88 Barbarians, Necromancers and many more. Which sounds all well and well until that central database is overwhelmed and the entire system, just like those who are working in it, demands rest.

"On Sunday morning Pacific time, we had an outage throughout the world because of a sudden, significant surge in traffic. This was a brand new level which our servers have never ever experienced, not even when they were launched," Blizzard explained.This was further exacerbated by an upgrade we'd made available earlier that day to improve performance during game creation-these two factors combined overloaded our database worldwide, causing it to time out. We made the decision to roll back the Friday update, which we'd previously rolled out in the hope of easing the load on servers over the course of Sunday while also giving us the time to study the root of the problem.

However, on Sunday it was evident that what we'd accomplished on Saturday wasn't enough. We noticed a larger volume of traffic, which caused us to hit another interruption. Our game servers were observing the database's inability to connect and then attempted to reconnect, several times and the database did not have the time to catch up with the work we'd accomplished because it was too busy handling a continuous stream of connection attempts made by game servers. We also discovered that we could enhance our configuration for logs of events in the database, that is required to restore the state of health in the event in the event of a database failure. So we completed those, and then conducted a further analysis of the root causes.

Not exactly the recipe for having a great time, that. It also explains why players had numerous issues with their progress, too. You'd select your character, begin a game, play for a while however the local server could not communicate with the central database because of an interruption. This meant it wasn't able to tell Diablo 2's sources to tell the "ground truth" about the brand new equipment and XP gained, resulting in frustrated players losing some of the progress they'd made.

The issues only got worse from there. There was an issue when the Diablo 2 servers came back in operation, but did so at a time where the majority of players were online. So although the servers re-established rapidly, they crashed nearly immediately as soon as millions of buy diablo 2 resurrected items instances fired up.