Intense Lag and Rubberbanding that started 3 weeks ago

Technical Support
1

Ive played diablo 4 since its release and have never had any sort of lag issues. About 3 weeks ago, which was a few weeks into season 14, Ive started getting intense rubberbanding to the point of it being unplayable. Its comes and goes at random and has sometimes actually disconnected me. And it happens whether im in a dungeon alone or in Temis with other around me. Im still on the same PC, but tried minimizing graphics. Ive reset my router, replaced the ethernet cord (i was already wired), reinstalled the game, done driver updates and nothing has worked. Im not having issues with any other online games at all and internet speed tests are good. I cant figure out what the issue is. Anyone else having this recently?

Edit/Update: I could be wrong but it seems to be tied to entire zones or maps Im loaded in to. I did an escalation where the first dungeon was fine, the second was incredibly awful with rubberbanding and sliding around. I tried waiting it out but it didnt get better at all. I ended up struggling thru it, getting the the 3rd dungeon where i had no issues, and no issues with the astaroth fight either. Upon returning to Temis I couldnt interact with any NPCs, stash or do anything but exit the game.

2

Have you tried power cycle your internet router?

3

Yes I tried that already

4

I was actually glad to see this post as its been happening to me for past 5 days or so. I have 2 gig internet but I never play anything else so couldn’t tell if its isolated to server side. Its not traditional lag, its like a 5 second lag where you can move around. Then when it corrects, it rushes through everything that happened during the lag , usually resulting in death. It makes PIT a no go. Also seems to happen every 7-10 min. I assumed it was server testing for the switch 2 release this week but who knows.

5

Been experiencing the lag and rubberbanding as well, but it’s only when teleporting to Temu or changing zones on the overworld. Corrects itself fairly quickly.

No issues in other towns or instances areas like dungeons.

6

https://us.forums.blizzard.com/en/d4/c/technical-support/9

7

Well I guess the game is working as intended. Remember guys they left rubberbanding in the game because D2 had it and they wanted D4 to have that same experience/feel.:roll_eyes: Lmao!

8

I see many others are having this issue and nothing seems to be getting done with it. Worrying Im not going to be able to finish the extra reliquaries I paid for

9

I’ve experienced this since the expansion release in Season 13. Sometimes it gets a bit better but not anywhere near what the perf was prior to the expansion. I even blew away my HD and reinstalled the minimal set of software on my gaming machine. No better what so ever…

10

Just figuring out now there seem to be absolutely no way of speaking to any type of blizzard support on here. Just useless automated messages that dont help at all.

11

Hey SpecialK057-1208,

Thanks for the detailed write-up, especially the edit — that’s the key piece here. The pattern you’re describing (fine in some dungeons, awful in others, breaking entirely on zone re-entry to Ториs) lines up closely with what a few others in this thread are reporting too: Kyba-11291 mentioned a similar delayed “rubberband correction” happening on a recurring interval, and righthere-11972 is seeing it specifically on zone transitions and Temu teleports. That consistency across different setups is a strong indicator this is server-side, not something happening on your end.

Given that you’ve already covered the standard client-side checklist — router reset, fresh ethernet cable, reinstall, driver updates, clean speed tests, no issues in other online games — there’s honestly not much more to rule out locally. At this point, further troubleshooting on your side is unlikely to move the needle.

The most useful thing right now is getting this in front of the team as a confirmed, reproducible pattern rather than a one-off. If you haven’t already, submitting a ticket with your system/network specs plus the zone-specific detail from your edit gives them something concrete to act on — general forum reports are easy to lose in the noise, but a specific “X zone/transition consistently causes Y” report is much easier to escalate.

Sorry you’re dealing with this, especially with reliquaries on the line. Hopefully getting more eyes on the pattern helps push it toward a fix.

12

Im actually having a hard time figuring out how to even open a ticket. Sorry if im being stupid but everything i go thru ends up just redirecting me to these forums or giving me an automated message

13

Hey SpecialK057-1208,

My mistake on the ticket suggestion — I dug into it after your reply, and it turns out Blizzard’s support flow routes connection/latency/lag issues to self-help articles and then, by design, to the forums rather than to a live ticket. So you weren’t missing a button or doing anything wrong; there’s just no ticket path for this particular category of issue. Sorry for sending you down that road.

Given that, the more useful next step is actually building a data-backed case here in the thread rather than through support. Rubberbanding means your client has lost sync with the server and gets snapped back to the last position it confirmed — the question is where in the path that desync is happening.

The likelihood that it’s weak hardware on Blizzard’s end is low. More likely, the issue is routing between you and their servers, so that’s what’s worth isolating. Can you run a WinMTR to North America (Americas): 137.221.106.88 (or US Central: 24.105.62.129)? WinMTR is a free tool (https://winmtr.net/) — let it run for 5-10 minutes, then post the results here using the pre-formatted text or </> function.

With your results alongside what Kyba and right here are seeing, that’s a much stronger, reproducible pattern to point to than any of us posting individually — and it’s the kind of concrete data that’s more likely to get traction than a support ticket would have anyway.

14

Im in upstate NY so not sure which one id be connecting to by default but these are results.

24.105.62.129

WinMTR Statistics

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
www.routerlogin.com 0 577 577 0 0 14 0
lo0-100.ALBYNY-VFTTP-302.verizon-gni.net 0 577 577 0 4 84 2
G4-0-3.PITBPA-VFTTP-39.verizon-gni.net 0 577 577 8 10 27 9
No response from host 100 117 0 0 0 0 0
customer.alter.net 90 127 13 7 8 11 8
bost-b5-link.ip.twelve99.net 1 573 572 8 11 30 10
nyk-bb5-link.ip.twelve99.net 10 421 381 14 15 31 14
chi-bb1-link.ip.twelve99.net 2 550 543 28 30 46 32
chi-b23-link.ip.twelve99.net 81 138 27 0 30 33 29
blizzard-ic-348622.ip.twelve99-cust.net 0 577 577 30 36 117 50
No response from host 100 117 0 0 0 0 0
et-0-0-1-pe01-evch1.as57976.net 0 577 577 31 33 75 32
24.105.62.129 0 577 577 32 34 48 33

137.221.106.88

WinMTR Statistics

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
www.routerlogin.com 0 564 564 0 0 4 0
lo0-100.ALBYNY-VFTTP-302.verizon-gni.net 0 564 564 0 4 73 3
G4-1-2.PITBPA-VFTTP-39.verizon-gni.net 0 564 564 6 9 23 9
No response from host 100 113 0 0 0 0 0
customer.alter.net 77 139 32 0 7 10 7
bost-b5-link.ip.twelve99.net 0 564 564 7 10 32 11
nyk-bb5-link.ip.twelve99.net 0 564 564 13 14 17 15
chi-bb1-link.ip.twelve99.net 1 549 545 28 29 37 29
chi-b23-link.ip.twelve99.net 0 563 563 28 30 93 29
blizzard-ic-348622.ip.twelve99-cust.net 0 564 564 29 35 115 33
No response from host 100 113 0 0 0 0 0
No response from host 100 113 0 0 0 0 0
et-0-0-0-pe03-swlv10.as57976.net 0 564 564 69 71 105 69
No response from host 100 113 0 0 0 0 0
No response from host 100 113 0 0 0 0 0
No response from host 100 113 0 0 0 0 0
No response from host 100 113 0 0 0 0 0
No response from host 100 113 0 0 0 0 0
No response from host 100 113 0 0 0 0 0
No response from host 100 113 0 0 0 0 0
No response from host 100 113 0 0 0 0 0
No response from host 100 113 0 0 0 0 0
No response from host 100 113 0 0 0 0 0
No response from host 100 113 0 0 0 0 0
No response from host 100 113 0 0 0 0 0
No response from host 100 113 0 0 0 0 0
No response from host 100 113 0 0 0 0 0
No response from host 100 113 0 0 0 0 0
No response from host 100 113 0 0 0 0 0
No response from host 100 113 0 0 0 0 0
15

Hey SpecialK057-1208,

Thanks for running that — let’s walk through what it actually shows, because a couple of numbers in there look scarier than they are.

The 90% and 81% “loss” you see at two hops in the first trace isn’t real packet loss. The giveaway is that the hop right after each one drops back down to 0-1%. If packets were actually being dropped at that point, every hop after it would show loss too — a lost packet can’t continue further down the path. What’s actually happening is those specific routers are just deprioritizing replies to ping probes when they’re busy, while still passing your real traffic through fine. It’s a known false alarm with this kind of tool, not a fault.

Past that, your latency to Blizzard is clean — around 32-34ms, no big spikes. The second trace reaches Blizzard’s own network in Las Vegas at a normal ~71ms and then goes to a wall of “no response,” which is Blizzard’s servers refusing to answer traceroute pings past that point (common security practice), not a broken connection.

So the short version: this run doesn’t point to a routing or ISP problem. Your path looks healthy.

That actually lines up with what I said earlier — the pattern across multiple people in this thread (different regions, different ISPs, same symptom, same rough timeframe) still points to something server-side rather than in any one person’s connection. Since local network diagnostics aren’t turning up anything, let’s shift the troubleshooting angle: instead of tracing the path, let’s build a timeline.

If you can, start logging the exact time (down to the minute) each time you get hit with lag/rubberbanding, plus what you were doing when it happened — normal open-world, Helltide, a boss fight, Pit, etc. Content that spikes server population or load (Helltides, world bosses, group content) is a common trigger for server-side tick issues, so if we can find a pattern there, or in time of day, that’s something concrete to point to rather than “it’s been bad for 3 weeks.”

If others in the thread are willing to do the same, cross-referencing timestamps across multiple players is a much stronger signal than any one person’s network trace.