This worked, but the very next day, an even higher surge in traffic caused the system to crash again. This led to a cascading series of failures that forced them to roll back their update and try to reestablish a stable network. Essentially, due to the way Blizzard’s regional servers link to the global database that saves your game progression, when the servers came under unexpectedly high load - as they describe it, a sudden surge in traffic they’d never experienced even when the game launched - just after they’d implemented an update that was intended to improve game performance around the creation of a game, the connection to the global database timed out. I’m not going to try and reproduce it all here, but the recap of what actually happened to the servers is simultaneously unprecedented and unsurprising. Now Blizzard has posted details on what the issues are and how they’re working to resolve them, and it’s pretty interesting reading. From losing character progression to simply being unable to play the game at all, server issues aren’t fun for anyone. Even if they haven’t affected you personally, they’re a hot topic of discussion - for understandable reasons, as these server issues have had some pretty drastic effect on players. If you have been playing Diablo 2: Resurrected, then you likely already know that the game has had some significant issues with its servers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |