All of them have their own databases for each region which contain the data of the characters who play on them D2R Items. This is necessary because there's more than enough players enjoying Diablo 2 to just continually upload everyone's data to a single, central point.
"Most of your game-related actions take place on this local database due to it being more speedy, and your character is locked there to keep the personal character record's integrity. It also has a back-up in case the primary database fails. fails,"These regional databases periodically send data back to central databases in this way Blizzard is able to keep a single record (with backups) of your thicc Level Necromancers, Barbarians, and other characters. This sounds great and great until the central database becomes overloaded and the whole system, like the engineers who work in it, demands to take a break.
"On Sat. morning Pacific time we suffered a global outage as a result of a sudden, significant surge in traffic. This was a brand new threshold that our servers had never experienced at all, even before launch," Blizzard explained.This was exacerbated by an update we'd rolled out earlier that day to improve performance during game creation. These two factors together strained our global database, causing it to go out of service. We took the decision to reverse that Friday update we'd earlier deployed in the hope of easing the load on the servers leading into Sunday while also giving us the chance to look into the root cause.
However, on Sunday it became apparent that what we'd done on Saturday wasn't enough. We also saw an additional number of requests, which led us to experience another downtime. The game servers were watching the disconnect from the database and tried to reconnect repeatedly, which meant that the database didn't have time to catch up with the work that we'd done due to the fact that it was dealing with a constant stream of connection attempts by game servers. At this point, we also discovered that we could enhance our configuration for data event logging. This is essential to return the database to an optimal state in the event of database failure, so we completed these and then conducted a further analysis of the root of the problem.
This isn't exactly the recipe for having a great time, that. It's also the reason players were experiencing so many issues with playing progress. You'd select your character, play and then play for some time and then the regional server couldn't communicate with the central database following an outage buy D2R ladder items. This meant it wasn't able to tell Diablo 2's source for "ground truth" about the latest gear and XP you'd earned, resulting in frustrated players losing some of the progress they'd made.