Server traffic increased the following day, causing another outage. Blizzard says the spike in traffic on October 9 was bigger than that of the game’s launch, and that when combined with an update rolled out for the game just a day before, caused Diablo II: Resurrected’s global database to time out. As highlighted last weekend, large spikes in player numbers, and the amount of in-game lobbies they were creating, caused a global server outage. In a new post on the official forums, Blizzard explains what exactly is going on with Diablo II: Resurrected’s recurring server issues, and what the team is doing to fix it–including login queues and a limit on rapidly creating and joining games. Server issues and locked characters were common in the days following the launch, but server outages and authentication issues have persisted since then. Diablo II: Resurrected released weeks ago, and it didn’t exactly go as planned.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |