Skip to main content

Blizzard offers explanation for Diablo 2: Resurrected server issues so far

Diablo 2 Tyrael
Diablo 2 Tyrael (Image credit: Blizzard Entertainment)

What you need to know

  • Diablo 2: Resurrected launched in September earlier this year and is still undergoing some server problems.
  • Developer Blizzard Entertainment is offering an explanation for why these issues are still happening.
  • Steps are being taken to fix these issues but there's no timeframe for when it may be fully resolved.

Blizzard Entertainment is offering an explanation for the ongoing Diablo 2: Resurrected server errors and problems so far. In a blog post, Blizzard explained that long story short, the server issues are not due to one problem but a combination of issues affecting everything. The servers are apparently struggling to implement changes while also dealing with spikes of traffic, leading to outage issues.

Additionally, Blizzard claims there is one piece of a "legacy service" that handles a lot of important server data and is also struggling with the changes implemented so far. Blizzard is currently writing new code to help offload these issues, but there's no exact timeframe for when players should expect to see this issue resolved.

Another step Blizzard is taking to fix these issues is rate limiting, but only in specific situations. Players doing Pindleskin runs are noted to likely receive error messages due to the vast rate of opening and closing new games. This isn't because the game is having issues but instead rate limiting to help prevent some of the ongoing server strain.

In the meantime, if you have yet to get started in this remaster compilation, we've got a beginner's guide to classes in Diablo 2: Resurrected to help set you off on the right path.

Samuel Tolbert is a freelance writer covering gaming news, previews, reviews, interviews and different aspects of the gaming industry, specifically focusing on Xbox and PC gaming on Windows Central. You can find him on Twitter @SamuelTolbert.

1 Comment
  • Not surprised but I do want to thank the "have to be first" community for ensuring that my experience is top notch.