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.
Problems 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 (55%)
-
Online Play (25%)
-
Glitches (11%)
-
Game Crash (9%)
Live Outage Map
The most recent Diablo IV outage reports came from the following cities:
| City | Problem Type | Report Time |
|---|---|---|
| Online Play | ||
| Glitches | ||
| Sign in | ||
| Sign in | ||
| Online Play | ||
| Online Play |
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:
-
Alf moser
(@MoserAlf) reported
@jat0rz @Diablo cant enjoy anything .. 3 hours waiting to login.. than being logged in and getting corrupt file error after 2 mins ... just to rejoin login waiting line ..just to get disconectet again ...so yeah blizzard has 30 years of XP with betas and games they still dont deliver
-
ZeldoZ
(@Joe95_m) reported
@Asmongold @Diablo Looks like NA got ****** hard... on EU I waited 20min in queue and played for 11h straight, not once did it crash or any bullshit... 🤔
-
Celestia 🌱
(@celestia6) reported
Trying to play @Diablo beta, but any time there is a cinematic my game shuts down and my computer logs me off and resets. Graphics card problem or something? It’s.. weird.
-
Prince Daniel
(@PrinceDaniel420) reported
@Olirvagx @LushSlippers @Diablo Diablo 3 never had an offline mode on the PC and was nearly unplayable on launch because of this exact problem.
-
ShovelFighter
(@LushSlippers) reported
@dreadscape @ryanfisher122 @Diablo Yea, my interest has dropped massively after discovering this. I really want to play it, but ill probably just wait for a sale now. The amount of issues ive had between both weekends, that could easily be fixed by allowing offline play, but they just refuse to acknowledge it
-
Eric Stucky
(@stuccofficial) reported
@GH0STGANJ @jjstraka34 @Diablo Server capacity/performance/issues WILL ALWAYS be a thing. It’s a very tough thing to prepare for. Servers cost a lot of money. It doesn’t make sense for a business to “overload” on servers to help prevent these issues, it’s just not financially feasible.
-
John wu
(@LVHAXOR) reported
@IdodmgA @Diablo Think they just did a hot fix to fix this problem
-
𖤐 Ø₱ɆⱤ₳₮łØ₦: ⱠłⱠł₮Ⱨ 𖤐 - 50% off OF $3.33
(@TSWednesday) reported
i play Cyberpunk 2077 on High w/ Ray Tracing and have ZERO problems. its not my rig, @Diablo is just ******* ****. sorry not sorry, probably the worst first impression on someone trying to play a diablo game for the first time.
-
Ryan
(@RyanJ44S) reported
@darkthorian @jat0rz @Diablo Authenticator has never been more broken in wow than it is now, they fired all the dirt bags that kept the company running.
-
MattMadd22
(@drumerboi22) reported
@RyanJ44S @jat0rz @Diablo Maybe. All I know is it took 3-6 months before anyone could login without either getting error codes, being booted during games, or having to play at half visual quality to get the game to run right.
-
Brandon Ratliff
(@Brandon052986) reported
@Diablo keep getting error code 316703 every like 15 minutes and have to close the game an sit in que
-
who cares
(@JamieEd67663464) reported
@jat0rz @Diablo The issue is the stupid pointless queuing
-
Anthony Coates
(@Anthony_Coates) reported
@jat0rz @Diablo Stop using the fact it's a beta as an excuse. They are having issues as they have purposely sandbagged the servers, they say so themselves on the forums.
-
Orpheus Elene
(@OrpheusElene) reported
@KillerSPER @Diablo Yup, having the same problem on xbox one
-
Austin Purzak
(@austinpurzz) reported
@Diablo Didn't work fyi everyone, can't even adjust screen size when I got through the queue, the error still appears and can't press anything, hoepfully this reaches someone who can fix this or knows how to help resolve the issue, sad day lol
-
CONAN
(@COLOMAN88) reported
@LushSlippers @Diablo It would fix it but I think it’s kinda cool running into other players while exploring
-
gothaggis
(@gothaggis) reported
@alex_frostwolf @Diablo Yeah, queue for 45 minutes, play for 10 mins, disconnect, queue for 45 minutes repeat
-
Andrew Hammond
(@AndaxTech) reported
@Diablo super impressed by first impression of D4 - I can be a werebear again! Just got booted with `Error Code 316719` though 😨consistently errors and can't play or make new chars
-
Eleana
(@_AmaterasuSan) reported
@nia_acee @jat0rz @Diablo Yes and they will continue to fix the problem, this is nothing new all new games are like this because they're trying to work with the mass flow of people in the game that's why there is login queues etc etc. Don't complain about things not getting fixed the way you want.
-
Kevin Good
(@KevinGoodLR08) reported
@yazman666 @Diablo @Blizzard_Ent I’ve had a few issues here and there but nothing unexpected for beta. They specifically said they would be purposely stressing servers for testing. Hopefully it’s not the same at launch.
-
Blvck
(@blvck_1ne) reported
@bbarling @_BrianDaniels @Diablo Last week was smooth as a babies *** for me. No issues at all. I just got back online and it loaded right in so later is definitely better.
-
MattMadd22
(@drumerboi22) reported
@jat0rz @Diablo This is Blizzard we’re talking about. They won’t fix these issues for launch. Error 39 anyone?
-
Tom gavin
(@Tomgavin10) reported
@NikolasScratch @jat0rz @Diablo Disconnects aren't the problem, it's the error that causes you to have to quit the game and re-enter the 50 minute queue
-
Ryan
(@RyanJ44S) reported
@TKiyov @jat0rz @Diablo Yeah, beyond server issues is a plethora of issues that need fixing, but unless people get that far in AND report, this is releasing half baked.
-
Ian M
(@ianmcgrath21) reported
@Diablo hey any help getting passed error code 397006?
-
Rui Santos
(@ruiguia) reported
@jat0rz @Diablo new here? last week they said the queues were a problem they weren't expected, but this week they would be ready.... kkkk dude, you think the same dc's and queue wont happens on launch? you must be really new or blind, in WoW they did this for 20 yrs...
-
Azarri
(@SkinHunger55) reported
@KarlJakober @jat0rz @Diablo I mean, no one is forcing you to play the beta. To majority of people, Beta = a chance to try out the game. Not a way to help the devs find bugs and other issues.
-
Peter turns string into things 🏳️🌈
(@texaspenguin) reported
@CritsKrieger @Diablo I’ve had zero issues. Downloaded it, waited in queue for about 35-40 minutes around 2p central, played with some minor hiccups and sync issues, took a break, went right back in for another few hours without having to wait in queue again.
-
Azarri
(@SkinHunger55) reported
@Olirvagx @LushSlippers @Diablo It doesnt "NEED" an offline mode. If you guys dont like it, dont play Diablo 4. Problem solved. This is not Diablo 2 or 3. Its Diablo 4. Completely different game.
-
Skuffy 🇫🇷🏴
(@Skuf_AleLover) reported
@Ridicliousman @leobrjor @Diablo Europe is fine, no crash nothing