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
Slagelse, Region Sjælland 1
Mission Viejo, CA 1
Flagstaff, AZ 1
Paris, Île-de-France 1
Lansing, MI 1
Cincinnati, OH 1
Jerez de la Frontera, Andalucía 1
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

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:

  • 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

  • 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.

  • 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.

  • SuperZheroK kev_vun_lux90🇱🇺 (@SuperZheroK) reported

    @Diablo Well anyway I did freeze the game this far and I'm playing other games instead while Blibli is fixing there issues. Cause I wanna enjoy my game when coming home after work, instead of raging every day because of the issues

  • 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.

  • 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

  • piggyjohn stygian (@piggyjohn) reported

    @Diablo and the most ridiculus thing is that you still have no idea to 100% solve the problem, and that means ppl still would lose their long-time progress. BEST TECH TEAM EVER, DO YOU GUYS NOT HAVE ENGINEERS?

  • becripps Blake Cripps (@becripps) reported

    @Diablo I hate the login queue. It's never felt good - not in WoW, not in any of the expansions... it won't if it comes up here in D2. I understand that it is necessary right now based on the shortcomings you have identified, but it shouldn't be the permanent plan. @RodFergusson

  • 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

  • kinamochi3 テン (@kinamochi3) reported

    @Diablo Does this mean LOBBY for CONSOLE? _____ and also planned for larger projects, like new microservices (for example, a GameList service that is only responsible for providing the game list to players). _____

  • damnnigf damns (@damnnigf) reported

    @MikePuc87293605 @jkranz119 @Diablo not bootlicking... just stating my own experience with the game, as well as the experience ive observed from all my close friends playing the game... that of course doesnt mean it doesnt have problems, im sure you could have bugs and be big ones like what you say...

  • Mandyleh Eliézer Ian (@Mandyleh) reported

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

  • jayhew647 Jamie Hewett (Jamie Barber) (@jayhew647) reported

    @Diablo If people think the problems for this are hard, they clearly never played Friday the 13th on release. That was a learning curve for most of the devs from a very small team. This is an easy wait in comparison. You waited 20 odd years for this, few days more will not kill you.

  • 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

  • JessiBear_2115 Jessibear (@JessiBear_2115) reported

    @McKercherAndrew @jkranz119 @Diablo I don't have a problem with patches. I have a problem with developers releasing games in an unfinished state, and patching them after release. This is becoming common in the industry and it's unacceptable. Your game release shouldn't be a large scale beta test

Map Check Current Status