Diablo IV

Diablo IV Outage Map

The map below depicts the most recent cities worldwide where Diablo IV users have reported problems and outages. If you are having an issue with Diablo IV, make sure to submit a report below

Loading map, please wait...

The heatmap above shows where the most recent user-submitted and social media reports are geographically clustered. The density of these reports is depicted by the color scale as shown below.

Diablo IV users affected:

Less
More

diablo Hero Image

Diablo 4 is a hack and slash action role-playing game developed and published by Blizzard Entertainment, and is the fourth main installment in the Diablo series. It is available on PlayStation, Xbox and Microsoft Windows.

Map Check Current Status

Most Affected Locations

Outage reports and issues in the past 15 days originated from:

Location Reports
Round Rock, TX 2
Gmunden, Oberösterreich 1
Hamilton, Scotland 1
Vienna, Wien 1
Augsburg, Bavaria 1
Ljubljana, Mestna Občina Ljubljana 1
Sacramento, CA 1
Viby, Region Midtjylland 1
Uberlândia, MG 1
Los Angeles, CA 1
Galion, OH 1
Indianapolis, IN 1
Anápolis, GO 1
Sofia, Sofia-Grad 1
Sorocaba, SP 1
Bologna, Emilia-Romagna 1
Ashburn, VA 1
Watford, England 1
Seaforth, England 1
Florissant, MO 1
Tucson, AZ 1
Colorado Springs, CO 1
Lebanon, TN 1
Santa Clara, CA 1
Montréal, QC 1
Melbourne, VIC 1
Râmnicu Vâlcea, Judeţul Vâlcea 1
Columbus, OH 1
Pilar, BA 1
Lohn, TX 1

Community Discussion

Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.

Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.

Diablo IV Issues Reports

Latest outage, problems and issue reports in social media:

  • cal64233805 Josh Caldwell (@cal64233805) reported

    @Diablo Database issues are no fun. Good luck on refactoring, definitely not as easy as people think to address a backed up DB and not lose or corrupt data.

  • Shotslol Shotslol (@Shotslol) reported

    @Diablo Posted on yet another day of server issues.

  • minustongue Martin Bellicose (@minustongue) reported

    @Diablo Can you fix the Fkey bug and then I will tell you?

  • JessiBear_2115 Jessibear (@JessiBear_2115) reported

    @julesx416 @TommyWierper @Diablo Again that sounds like a Blizzard problem, not a player problem. If your database server couldn't handle the load then you shouldn't have sold so many game copies. They were all too happy to take everyone's $40 knowing the infrastructure couldn't handle it.

  • jaime_banno kïtsune (@jaime_banno) reported

    @Diablo Thank you finally for some communication. Better late than never. I still believe ppl should have the option to refund with all the problems, it would've gone a long way to mending the relationship with your player base. But glad that you're finally addressing the issues

  • FFactor5 Chris Flowers (@FFactor5) reported

    @jkranz119 @Diablo It isnt broken it is actually too successful of a launch.

  • Barsonik21 Spencer (@Barsonik21) reported

    @riotdanhonks @Diablo Yeah this is more what i was trying to allude to, but I guess its fairly easy to overlook something if you don't view it as being a possible issue

  • holgoid EntropyZero (@holgoid) reported

    @Diablo One single multi purpose service placed before a single point of truth database. Reads like bad backend architecture, @Diablo @Blizzard_Ent.

  • RostenSchweiger Raegna (@RostenSchweiger) reported

    @Diablo I get the excuses, everytime you came up with those, since launch. What I really don't get is how does a company like Blizzard, with several exp on high server stress launches can't foresee this types of issues about a game the community has been requesting for years.

  • JayefsiED Kayefsi (@JayefsiED) reported

    @Y0vrFace @TheEthylon @Diablo It does not explain separate console specific issues, however it does show they are communicating as they investigate and figure out what’s going on

  • riotdanhonks dan honks, but spooky (@riotdanhonks) reported

    @Barsonik21 @Diablo Which is not surprising - All of these things were not really problems back in 2001 but *are* problems now, and Blizzards response is to take the services that are bricking it and breaking them into smaller services which can be better scaled and are more resilient

  • Murquis Murquis | Marcos - 🎲-🌑 (@Murquis) reported

    @Diablo Nice work with the database, all the problems are because old game, LOL! Put more servers to attend all the players, you recognise that's the problem, too many request in short time “We hit another concurrent player high, with a few hundreds of thousands of players in one region”

  • Wraithskiller Marc lapointe (@Wraithskiller) reported

    @Diablo What about this broken online system on console ? I cant even do public baal run it keep sending me into the same game even if baal is dead and ppls are farming somewhere else.... its truly a joke how you made this

  • riotdanhonks dan honks, but spooky (@riotdanhonks) reported

    @Barsonik21 @Diablo Now, you could argue, and you ought to, that Blizzard probably should have seen this coming, but maybe they didn't anticipate how popular Diablo was and (iirc) they didn't have significant issues with WoW classic when that was launched, so, hindsight is 20/20 i guess

  • Mandyleh Eliézer Ian (@Mandyleh) reported

    @Diablo Are these serves issues the reason why items in my shared stash are dissapearing/not saving?

Map Check Current Status