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.