VPN to Toronto, no packet loss early on, still lagging. Looks like 50% packet loss at one of Bell’s nodes. Seems like an ISP routing issue. Just wonder why it’s specifically Diablo 4 that’s the only game affected. Oh well. Might try switching to Rogers.
Tracing route to 40.230.170.34.bc.googleusercontent.com [34.170.230.40]
over a maximum of 30 hops:
1 5 ms 5 ms 5 ms 100.64.1.200
2 6 ms 7 ms 18 ms 149.57.28.29
3 7 ms 4 ms 6 ms be6332.nr01.b011027-7.yyz02.atlas.cogentco.com [38.32.158.65]
4 5 ms 7 ms 5 ms te0-0-1-2.agr13.yyz02.atlas.cogentco.com [154.24.51.45]
5 4 ms 7 ms 5 ms te0-9-0-9.ccr31.yyz02.atlas.cogentco.com [154.54.43.141]
6 20 ms 12 ms 15 ms be2993.ccr21.cle04.atlas.cogentco.com [154.54.31.225]
7 28 ms 23 ms 22 ms be2889.ccr41.jfk02.atlas.cogentco.com [154.54.47.50]
8 24 ms 24 ms 22 ms be3294.ccr31.jfk05.atlas.cogentco.com [154.54.47.218]
9 28 ms 23 ms 21 ms tata.jfk05.atlas.cogentco.com [154.54.12.18]
10 25 ms 27 ms 31 ms if-be-2-2.ecore1.n75-newyork.as6453.net [66.110.96.62]
11 31 ms 28 ms 25 ms 72.14.221.146
12 * * * Request timed out.
13 * * * Request timed out.
More often than not, most of these issues are something with the route. Which still sucks! But glad you did check the path. Its important to know for sure.
I’m trying to gather as many of these WinMTR reports I can to see how many are being affected by ISPs. So far as of this post I have 1 person that actually has no issues at their end or their ISP, but there is still something causing them issues apparently further down the line.
But the more of the reports I get, the more accurate we can pin it down.
same problem man! I noticed your activity on my topic with rubberband lags and high ping. Sorry for bothering you, but for me now, it seems, the best gameplay from Diablo 4 I am able to get, is to cry with others over the things that DO NOT WORK. My thoughts are this way - I understand, that after the launch, things can get pretty hectic. Not over just one problem… but with the experience from Diablo 3 when it was launched, why the hell was not Blizzard prepared? I could even be forgiving for that… if they fix the thing fast… My thoughts are, that the fixing problem is taking too much time, with the money-power behind the Blizzard behemoth… they should be able to optimize theese things way faster, than they are currently doing… so… final questions are - what is happening, and where to report it correctly, because noone seems to care about their game, which is generating really big income for next several years, to solve problems in the MOST CRITICAL STATE? If you readed the topic all the way down here, I wish you calm nerves, good luck and all happines that is needed for life. TY for reading. Roschwaldov
I wouldn’t say it wasn’t a matter of them not being prepared as it was being overwhelmed.
The issue here, is having enough data to correctly fix it. One of the reasons I have been pushing doing the WinMTR tests lately.
There has been no direct communication from Blizzard yet on latency and rubberbanding issues.
Technical thread where we are is good. You can also submit a ticket; But make sure you have some test data for both the hardware and network diagnostics as listed below:
This lists the test you can do and add to your ticket request, which you can do here:
i can play d3 on my pc with no issues or lag. d4 on my ps5 is a laggy, rubber banding nightmare.
both wireless, same bandwidth to both (300/20), low ping (7-100 via speedtest) same isp, it may not be d4 servers, but whatever the issue is, it’s localized to d4, i have no problems in other games.
I do see a bit of loss at your first hop here: (I have highlighted in bold the numbers we are looking at)
That shows a 2% loss. While that doesn’t sound like much, even a 1% loss can affect voice communication for example. It won’t affect normal web use much or watching video though. It can muck with gaming however.
That 2% is right at your router. Now it could be because you are using a wireless connection, but I’m guessing there.
However at your Comcast, you have a 42% loss. That’s nearly half the traffic!
I do see that the latency is a bit all over here as well and a bit high overall.
TraceRT doesn’t show the problems like the WinMTR did, nor did the pathping.
But there are obviously issues as WinMTR shows. So Comcast is causing an issue with your path while you are playing Diablo IV.
Thank you for taking the time to do these tests! And everyone else that can do them will help to narrow this down as well.
Please if you can, attempt to run these tests on your connection as well. My post is above:
I get massive rubberbanding now and then in EU. When I do a traceroute to the D4 EU IP that blizzard supplies (35.240.124.178) I get a hop to a US IP (209.85.174.232) and everything after that is nil. Why is there a US hop in there?
exactly the same, game is virtually unplayable, it has been for the past damn week, its ridiculous. 2 bad the first 2 hours worked perfectly, just so I cant refund lol
