Diablo IV lag and rubberbanding: causes and fixes

Diablo IV is always online, even when you play alone, so your connection is part of every dash and every skill. When it falters you rubberband: you move, then the world puts you back. Here's how to see your latency, what causes the snapping, and what helps.

Why an action game rubberbands

Your game shows your character moving the moment you press, and the server checks it. When the server's answers arrive late, or some never arrive, the server's version and yours drift apart. When the answer finally comes, the game puts you where the server says you are. That's rubberbanding: not a slow game, but a correction.

So Diablo IV punishes uneven connections more than slow ones. A steady, moderate latency plays fine. A low latency that jumps, or drops packets, snaps you back mid-fight.

See your latency in the game

On PC, press Ctrl + R. The first press shows your frame rate in the corner; press it again and it shows your latency; a third press hides it. Watch the latency when the rubberbanding happens:

• Latency high all the time: distance, or a long road from your provider to Blizzard.
• Latency that jumps at the moment you snap back: queueing on the way, often on your own line or Wi-Fi. What causes ping spikes shows how to find where.
• Calm latency, but the game stutters: switch the counter to frame rate. If that drops, it's the PC, not the network.

What helps

1. Use a cable. Rubberbanding is very often Wi-Fi. Wi-Fi or Ethernet explains why it matters more than the average ping suggests.
2. Keep the line quiet: game patches downloading in the background, cloud backups, streams.
3. Fix the router's queue if others share the connection: SQM, or QoS that's configured.
4. Watch the time of day. Snapping every evening and never in the morning is your provider's busy hours.
5. Change the route when your latency is higher than your distance to Blizzard's European servers explains.

Not all of it is yours: on busy days, Diablo IV's own servers can struggle, and then everyone rubberbands. If your latency counter stays calm while you snap back, that may be the case.

Where NoSpike fits

NoSpike's Diablo IV entry is a beta: its servers are still being mapped, so NoSpike may not carry all of a session's traffic yet. While you play, its page in the app says what it carries.

Where it does carry the game, it measures your own route and the routes through its relays in Europe, and routes Diablo IV only when a relay is faster. It checks again every minute and doesn't move a running session unless the route fails, because a moved connection is a disconnect.