On Sundayhowever, D2R Items was clear that the work we'd accomplished on Saturday wasn't enough. We also saw an additional rise in traffic that caused us to hit another downtime. The game servers were watching the database's absence and then attempted to reconnect frequently, meaning that the database did not have the time to catch up on our work.

Because it was too busy dealing with a constant stream of connecting attempts from game servers. While we were at it, we also noticed that we could enhance our configuration for database event logging. This is vital to restore an ideal state of health in the event of a database malfunction, therefore, we made those improvements and conducted further investigation of the root causes.

It's not exactly the recipe for the perfect weekend, but it certainly was fun. This is also the reason why players had so many issues with progression, too. You'd choose your character, start a game, play for a while but the regional server wasn't able communicate with central database after an incident.

Therefore, it wasn't able to tell Diablo 2's source of "ground truth" regarding the new gear and XP gained that resulted, in frustration players losing some of their progress.

The issue only got more serious from that point on. Diablo 2 servers came back online. Diablo 2 servers came back on the internet, but they were not online during a time which saw the most players online. even though the servers returned quickly, they crashed almost immediately as soon as many thousands of Diablo 2 instances fired up.

And if the weekend was d2r items for sale What followed on Monday and Tuesday wasn't much better. will bring us to Monday the 11th of October, when we switched between the global databases.