Is Diablo IV down?
No problems detected
If you are having issues, please submit a report below.
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.
Full Outage Map
Sign inProblems in the last 24 hours
The graph below depicts the number of Diablo IV reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.
At the moment, we haven't detected any problems at Diablo IV. Are you experiencing issues or an outage? Leave a message in the comments section!
Most Reported Problems
The following are the most recent problems reported by Diablo IV users through our website.
-
Sign in (76%)
-
Online Play (14%)
-
Glitches (5%)
-
Game Crash (4%)
-
Matchmaking (1%)
Live Outage Map
The most recent Diablo IV outage reports came from the following cities:
| City | Problem Type | Report Time |
|---|---|---|
 São Paulo |
Game Crash | |
 Kempten (Allgäu) |
Online Play | |
| Aracaju |
Glitches | |
 Canet-en-Roussillon |
Online Play | |
 Bexleyheath |
Glitches | |
| Petrolina |
Online Play |
Full Outage Map
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:
-
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
-
bivermayn
(@bivermayn) reported
@McKercherAndrew @jkranz119 @Diablo The only reason they are upfront now is because they have no fix right now and the problems will continue. So better save some face while they can.
-
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.
-
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
-
dan honks, but spooky
(@riotdanhonks) reported
@Barsonik21 @Diablo My read on the issue is that it's not individual lines of code that are the problem, it's a systemic issue with how services are structured, how they can be scaled and how they respond to failures to prevent a failure cascade
-
Tj
(@Plunkplounk) reported
@McKercherAndrew @jkranz119 @Diablo Yes I to like paying for a broken product. I think I'm gonna go buy a new car but don't worry if it doesn't run I won't blame them for not putting in an engine
-
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.
-
Steve C
(@DarkHorrorChi) reported
@McKercherAndrew @jkranz119 @Diablo It's broken for sure. The amount of lost items is crazy. The amount of deaths because server issues is mad. The option for a refund should be there pure junk
-
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.
-
dal
(@ramalad) reported
@McKercherAndrew @jkranz119 @Diablo It is not like they beta tested things or anything. They knew about the issues in beta and did nothing.
-
Jessibear
(@JessiBear_2115) reported
@toroltir @atlcanadiangmr @Diablo Blaming Nvidia for Blizzard's failures is pure copium. Just like how Blizzard blamed the Windows gaming bar for causing their game to crash 20 times every play session. Time for Blizzard to take responsibility for their poor products.
-
Nord Troll Gaming
(@toroltir) reported
@atlcanadiangmr @Diablo Hei. This is a Nvidia driver issue, not the game. Download an earlier driver 471.96 or 472.12 can't remember exactly. Then you won't have this issue anymore <3
-
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
-
Nikolay Minchev
(@erasera666) reported
@Diablo Another excuse post. You sell broken console game. Far far from the original. Your servers are mess, you refuse refunds. You take our money. I dont care your bla bla excuses. I already payed its not my fault that you screw again. Why i have to pay for your mistake
-
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
-
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.
-
Homerjnick
(@homerjnick) reported
@Diablo Very good info but given offline chars on Console lose progression when you save and exit correctly and shared stash goes missing what is the recommendation? Play online but suffer server issues or just not play till you sort it all out?
-
Chris Flowers
(@FFactor5) reported
@jkranz119 @Diablo It isnt broken it is actually too successful of a launch.
-
dan honks, but spooky
(@riotdanhonks) reported
@Barsonik21 @Diablo IOW: Legacy code is not the problem so much as a lack of resiliency measures put in place, which is completely fair when it comes to games from 2001
-
Eliézer Ian
(@Mandyleh) reported
@Diablo Are these serves issues the reason why items in my shared stash are dissapearing/not saving?
-
Fred Saase
(@FredSaase) reported
@McKercherAndrew @jkranz119 @Diablo Nah see the caveat to GaaS is if the game is sold as a live service, then the infrastructure to provide said service is an integral part of the product. If they have server issues then the product is broken.
-
Shotslol
(@Shotslol) reported
@Diablo Posted on yet another day of server issues.
-
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”
-
Ryan Lewis
(@RyanLew85702475) reported
@Diablo props for finally explaining to us all the issues. keeping us in the dark was extremely frustrating. but anywho, better late then never. amazing remaster, but terrible launch.
-
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
-
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...
-
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
-
Martin Bellicose
(@minustongue) reported
@Diablo Can you fix the Fkey bug and then I will tell you?
-
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
-
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