Repeated Diablo IV desync/disconnects; packet capture included

I (EU player) have been experiencing repeated Diablo IV connection failures over the last couple of days, including several cases where I have lost valuable content/loot because of the disconnect.

The behaviour is very consistent and unusual:

  • The game does not immediately freeze or disconnect.
  • My character can still move around normally.
  • However, server-side interactions suddenly stop working.
  • I cannot pick up items.
  • Clicking/interacting with objects no longer works.
  • Skills/actions that depend on server acknowledgement stop behaving normally.
  • After some time, the session eventually disconnects.

Because movement continues to work, it is sometimes not immediately obvious that anything has gone wrong. The easiest way I have noticed it is when I click dropped loot and nothing happens.

Over the last few days this has happened multiple times. I have lost dropped Ancestral items and, most recently, an entire Mythic Tribute run because of it.

Today I deliberately ran Wireshark while playing and finally captured one of these failures.

The affected Diablo IV TCP connection was:

Remote IP: 34.185.184.232
Remote port: 6112

At approximately 11:56:38.706 CEST on 2 October 2026, something goes wrong with that connection.

A 4-byte TCP segment from the server appears and is then retransmitted repeatedly. The retransmissions continue with increasing intervals:

11:56:38.706
11:56:38.741
11:56:38.762
11:56:38.796
11:56:39.021
11:56:39.497
11:56:40.425
11:56:42.249
11:56:45.961
11:56:53.386
11:57:07.981
11:57:36.905
11:58:36.302
12:00:33.039

My PC never appears to acknowledge that segment successfully.

What makes this particularly interesting is that the connection becomes effectively one-way:

  • My PC continues sending packets to the Diablo server.
  • The server continues acknowledging traffic sent by my PC.
  • But incoming application data appears to become stuck behind this repeatedly retransmitted segment.

That seems to fit the in-game behaviour extremely well: the client continues to render movement locally and can apparently send information, while it stops receiving usable game-state updates from the server.

At the same time, my general internet connection remains operational. Other connections in the capture continue normally, including traffic to Google, Cloudflare and other services. There is no obvious general WAN outage coinciding with the Diablo failure.

Wireshark also flags the repeatedly retransmitted 4-byte segment with an incorrect TCP checksum. I am aware that checksum offloading can sometimes cause misleading checksum warnings in packet captures, so I am not claiming the checksum warning alone proves where the fault lies. What seems more significant is that the same segment is repeatedly retransmitted and never advances the TCP stream while unrelated network traffic continues functioning.

The .pcapng capture is available if Blizzard staff want it.

This has now happened enough times that it is becoming a serious gameplay problem, particularly because Diablo IV consumes keys, Tributes and other resources when activities are started.

I would be very interested to know whether other EU players are seeing the same specific pattern:

character can still move → interactions/pickups stop → eventual disconnect.

It is not only happening in EU, but it is also happening in the US as well. Log in to the game on PS5, play for maybe 10 minutes, and traffic no longer received from Blizzard servers. The character can move around with no problem, but all server-side functions are nonexistent. Could someone maybe post back and let people know what is going on? The frustration is real!

It has actually been manageable here over the weekend, but today, it’s craxy. 6 occurences so far.

@blizzard please let us know what is going on here. This is vexing!

Follow-up: I captured the same failure again today, and the packet-level pattern is essentially identical.

This time the affected Diablo IV connection was:
Server: 34.62.142.147:6112

At approximately 20:32:25 CEST on 5 October 2026, the inbound TCP stream stalls on a 3-byte segment. My client never advances its ACK beyond that sequence number (2283189494), and the server repeatedly retransmits the same segment with increasing intervals.

The important part is that this is now the second independent capture showing the same type of failure:

  • different day
  • different Diablo IV server IP
  • different session
  • same effective one-way stall

My PC continues sending game traffic to the server, and the server continues acknowledging that outbound traffic, but the inbound stream does not progress past the missing/corrupt segment. Eventually the server resets the connection.

As before, unrelated internet traffic continues normally during the incident, so this does not look like a general loss of connectivity.

Wireshark also flags the repeatedly retransmitted inbound segment with an invalid TCP checksum. I am aware that checksum offloading can make packet captures misleading, especially for outbound packets, so I am not treating the checksum warning alone as proof of root cause. What seems significant is that the same retransmitted inbound segment repeatedly fails while the TCP stream remains stuck at the same sequence number.

In-game, the symptoms again match the network trace:

character can still move → pickups/interactions stop working → session eventually disconnects

This is now reproducible enough that I no longer think the first capture was a one-off anomaly.

I’d actually leave it at that. It is short enough that people will read it, but technical enough that anyone with networking experience will immediately understand why the second capture matters.

I experience the same pattern.
And it gets worse as more players join in – in other words, the closer it gets to peak playing times, the worse the connection problems become.

Im having the same issue on Playstation

Yeah I finally get into a rare echoes of hatred and guess what…disconnect. They try to fix things and break other things.

I am seriously baffled by the lack of communication here.

Blizzard, you have multiple people here describing similar or at least related symptoms. All are inconvenienced by the problems and yet you completely ignore us, even though we provide you with information, that should put you in a position where you can do actual investigations.

It might be that the problem is not on your end. Fine. Communicate that. It might be that even with the information you have, investigation is not possible. Fine…then communicate that. It might be that the issues are under investigation, but you don’t have a status update yet. Then communicate that.

People are willing to put up with a lot, if there is active communication - as I am sure your Communications Director will tell you.

But I’ll tell you what no communications look like from a customer perspective: It looks like you don’t care!

Yes, the lack of communication bothers me too. Because, actually, you’ve explained very clearly what’s going on. As for me, I’ve made the decision that, even though the season is really good in terms of content, I can’t play it with like this (with the permanent disconnects).
I’m for my par will quit this season and hope that S16 will be better (from technical point of view).

The Mrs and I have experienced the same issues multiple times. As of writing this, I was just disconnected again after an Escalation run and missed at least one mythic drop. When I finally managed to log in, I was teleported back to town, unable to use any kind of chat and the spinning “Reconnecting-To-Diablo” hovering constantly. I decided to restart the game and was met with an error 7 and have not been able to connect since. EU, on PC.

I had to change all my settings to low to get it to even be playable, it is still choppy and jumpy with movement but it is at least playable and not locking up…

Both the Mrs and I did the same and we also had the same results as you. Then today we did a Mephisto run in T12 and the Mrs got DCed on the first wave. We decided to just go until she could reconnect, then I got DCed too. Now we both get error 7s. Brilliant.

I’m having what is probably the same issue. Random disconnects. It is getting frustrated because I have lost so much progress in the Pit and Kurast. Tell me again why forcing us to play online is a good thing?

Status after a weekend with 6-8 daily disconnects due to this issue.

Can we please pretty please have just some sort of indication whether this is being looked at?

I’m also having the same symptoms of issues for days now… it’s so frustrating of having to play a game with unstable servers… :sob:

Cant play it at all. also getting error codes 1016 30001 300008. was fine last week. only this game..

I have the same issue here in Asia realm.

The Mrs and I, again, got DCed while doing a mythic undercity run. Error 7’s once again. The hell is going on Blizzard?

Keeping this thread alive I’m afraid. We just lost 2 undercity runs - using a mythic tribute, mind you - but at least there were no error 7’s. Still though..

I’m experiencing the same issue on my SteamDeck. Still no response from Blizzard?

This is a major glitch making the game unplayable. Can someone at blizzard at least provide some response that its being looked into?

American Player. Being disconnected frequently enough that I don’t want to play.