I uninstalled the game and reinstalled without the High-resolution assets and haven’t had any issues since.
Again, your experience is your experience and it does not mean others will have the same. If you are a little bit technical, you would know that in a client-server architecture of this scale, there will be a lot of servers serving different regions and the one you are connecting may be fine while others are experiencing problem.
Figured I’d try that for funsies…and nope, nothing 
no dice
I seriously hope Blizz can figure this out because it absolutely seems like a massively widespread issue, and not a region thing (really? Only texas affected? I’m in virginia…that’s not close, and I think I read someone in Ireland getting a similar experience?)
I’ve said it before, and I’ll say it again, I had a near flawless experience connection-wise during the so-called server slam
1 Like
I wish I could believe your beliefs but “belief” is not “proof”, it is in fact the furthest thing from it. I’ve been playing from day 1 (pre-release) and issue has been there. Game DC’ed and crashed multiple times every day. This is not a one off.
For me having my apple tv on will cause rubberbanding which makes the game unplayable. Once the apple tv is off there are zero issues.
In Ireland with good internet, no issues in any other games with the tv on or off. Tried everything to solve it on my side.
Obviously not ideal cause others in my house wanna use the tv which means I can’t play when the tv is on!
bro what you talking about I have LINE connection to internet. I had no issues whatsoever for past 2 weeks and last 3 days it went crazy.
I’m at constant 100-250ms now and it spikes to 1700…
Twitch stream full HD, youtube, my download and upload speed is perfect.
It’s definitely server issue on Blizzard side 100%
2 Likes
Actually there is no way to know this 100%. But when you are angry, its easy to blame what you think is the cause.
Did you run a WinMTR? See where the ping hike occurs?
Use this tool to help troubleshoot the error. Lets make SURE its on Blizzard’s servers.
1 Like
WITH VPN:
Trace route logs:
Tracing route to 40 .230. 170 .34. bc .googleusercontent. com [34. 170. 230 .40]
over a maximum of 30 hops:
0 [redacted]
1 100 .64 .1 .226
2 199 .217. 105 .225
3 br01-ae0. brdr .bos01 .xcelx .net [192. 34. 87 .1]
4 packetsurge. lga .net .google .com [206 .53. 143 .6]
5 * * *
Computing statistics for 100 seconds…
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 GALAXY [100. 103. 30. 162]
6/ 100 = 6% |
1 39ms 6/ 100 = 6% 0/ 100 = 0% 100 .64 .1 226
1/ 100 = 1% |
2 37ms 7/ 100 = 7% 0/ 100 = 0% 199. 217 .105 .225
1/ 100 = 1% |
3 35ms 12/ 100 = 12% 4/ 100 = 4% br01-ae0. brdr. bos0 1 .xcelx .net [192.34.87.1]
0/ 100 = 0% |
4 45ms 8/ 100 = 8% 0/ 100 = 0% packetsurge .lga .net .google .com [206.53.143.6]Trace complete.
Tracert logs:
Tracing route to 40.230.170.34 .bc .googleusercontent .com [34 .170 .230. 40]
over a maximum of 30 hops:1 37 ms 34 ms 44 ms 100.64.1.226
2 40 ms 34 ms 31 ms 199.217.105.225
3 35 ms 31 ms 34 ms br01-ae0 .brdr .bos01 .xcelx. net [192.34.87.1]
4 36 ms 35 ms 42 ms packetsurge. lga. net .google. com [206.53.143.6]
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18
WinMTR logs:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
Host - % Sent Recv Best Avrg Wrst Last 100.64.1.226 - 6 304 286 29 40 165 32 199.217.105.225 - 10 276 251 30 41 183 33 br01-ae0 .brdr. bos01. xcelx. net - 10 272 246 30 41 210 50 packetsurge .lga. net. google. com - 6 304 286 35 45 183 38 No response from host - 100 76 0 0 0 0 0 No response from host - 100 76 0 0 0 0 0 No response from host - 100 76 0 0 0 0 0 No response from host - 100 76 0 0 0 0 0 No response from host - 100 76 0 0 0 0 0 No response from host - 100 76 0 0 0 0 0 No response from host - 100 76 0 0 0 0 0 No response from host - 100 76 0 0 0 0 0 No response from host - 100 76 0 0 0 0 0 No response from host - 100 76 0 0 0 0 0 No response from host - 100 76 0 0 0 0 0 No response from host - 100 76 0 0 0 0 0 No response from host - 100 76 0 0 0 0 0 No response from host - 100 76 0 0 0 0 0 No response from host - 100 76 0 0 0 0 0 No response from host - 100 76 0 0 0 0 0 No response from host - 100 76 0 0 0 0 0 No response from host - 100 76 0 0 0 0 0 No response from host - 100 76 0 0 0 0 0 No response from host - 100 76 0 0 0 0 0 No response from host - 100 76 0 0 0 0 0 No response from host - 100 76 0 0 0 0 0 No response from host - 100 76 0 0 0 0 0 No response from host - 100 76 0 0 0 0 0 No response from host - 100 76 0 0 0 0 0 No response from host - 100 76 0 0 0 0 0 ________________________________________________ ______ ______ ______ ______ ______ ______ WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
WITHOUT VPN:
Pathping logs:
over a maximum of 30 hops:
0 GALAXY.home [192.168.2.26]
1 mynetwork.home [192.168.2.1]
2 toroon0268w_coreloop.net.bell.ca [142.124.37.177]
3 * * *
Computing statistics for 50 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 GALAXY.home [192.168.2.26]
5/ 100 = 5% |
1 3ms 5/ 100 = 5% 0/ 100 = 0% mynetwork.home [192.168.2.1]
1/ 100 = 1% |
2 9ms 6/ 100 = 6% 0/ 100 = 0% toroon0268w_coreloop.net.bell.ca [142.124.37.177]
Trace complete.
Tracert logs:
Tracing route to 40.230.170.34.bc.googleusercontent.com [34.170.230.40]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms mynetwork.home [192.168.2.1]
2 6 ms 11 ms 9 ms toroon0268w_coreloop.net.bell.ca [142.124.37.177]
3 * * * Request timed out.
4 * * * Request timed out.
5 6 ms 6 ms 5 ms tcore3-toronto63_39.net.bell.ca [64.230.59.202]
6 * * 6 ms cr01-toroonxnhe9-bundle-ether4.net.bell.ca [142.124.127.165]
7 * 8 ms 17 ms bx3-torontoxn_hundredgige0-1-0-0.net.bell.ca [64.230.97.145]
8 5 ms 7 ms 5 ms google_bx3-torontoxn.net.bell.ca [184.150.181.147]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
WinMTR logs:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| mynetwork.home - 3 | 454 | 442 | 0 | 3 | 29 | 6 |
| toroon0268w_coreloop.net.bell.ca - 2 | 481 | 476 | 0 | 9 | 43 | 7 |
| No response from host - 100 | 100 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 100 | 0 | 0 | 0 | 0 | 0 |
| tcore3-toronto63_39.net.bell.ca - 4 | 432 | 415 | 0 | 7 | 37 | 5 |
|cr01-toroonxnhe9-bundle-ether4.net.bell.ca - 61 | 148 | 59 | 3 | 8 | 46 | 8 |
|bx3-torontoxn_hundredgige0-1-0-0.net.bell.ca - 2 | 477 | 471 | 0 | 6 | 35 | 7 |
| google_bx3-torontoxn.net.bell.ca - 2 | 473 | 466 | 0 | 6 | 32 | 4 |
| No response from host - 100 | 100 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 100 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 100 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 100 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 100 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 100 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 100 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 100 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 100 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 100 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 100 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 100 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 100 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 100 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 100 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 100 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 100 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 100 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 100 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 100 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 100 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 100 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Wow, you are showing 6-8% packet loss early in your traffic.
Also noted here:
So this shows that you are appearing to get a lot of packet loss. Anything above 1-2% can cause network disruption.
BUT.
I just realized something. You have a 61% loss at the Bell:
This looks really bad here. But your VPN may be circumventing it somewhat, however that small loss early on is going to cause issues as well.
These appear to be very early in your network, possibly before or after your router/modem. The VPN one shows it a bit later in the hops, but the same hardware may be causing it.
This also may help to understand how to read these tests:
1 Like
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.
WinMTR logs:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 100.64.1.200 - 0 | 133 | 133 | 2 | 4 | 23 | 2 |
| 149.57.28.29 - 4 | 118 | 114 | 2 | 5 | 49 | 4 |
|be6332.nr01.b011027-7.yyz02.atlas.cogentco.com - 2 | 125 | 123 | 3 | 6 | 47 | 5 |
|te0-0-1-2.agr13.yyz02.atlas.cogentco.com - 5 | 114 | 109 | 3 | 6 | 40 | 4 |
|te0-9-0-9.ccr31.yyz02.atlas.cogentco.com - 0 | 133 | 133 | 3 | 6 | 23 | 6 |
| be2993.ccr21.cle04.atlas.cogentco.com - 1 | 129 | 128 | 9 | 14 | 56 | 13 |
| be2889.ccr41.jfk02.atlas.cogentco.com - 7 | 103 | 96 | 21 | 24 | 62 | 28 |
| be3294.ccr31.jfk05.atlas.cogentco.com - 3 | 122 | 119 | 21 | 24 | 48 | 45 |
| tata.jfk05.atlas.cogentco.com - 3 | 121 | 118 | 21 | 24 | 93 | 21 |
| if-be-2-2.ecore1.n75-newyork.as6453.net - 8 | 102 | 94 | 21 | 24 | 69 | 21 |
| 72.14.221.146 - 1 | 129 | 128 | 22 | 26 | 76 | 24 |
| No response from host - 100 | 26 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 26 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 26 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 26 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 26 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 26 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 26 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 26 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 26 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 26 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 26 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 26 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 26 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 26 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 26 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 26 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 26 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 26 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 26 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Tracert logs:
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.
Pathping logs:
Tracing route to 40.230.170.34.bc.googleusercontent.com [34.170.230.40]
over a maximum of 30 hops:
0 GALAXY [100.76.28.103]
1 100.64.1.200
2 149.57.28.29
3 be6332.nr01.b011027-7.yyz02.atlas.cogentco.com [38.32.158.65]
4 te0-0-1-2.agr13.yyz02.atlas.cogentco.com [154.24.51.45]
5 te0-9-0-9.ccr31.yyz02.atlas.cogentco.com [154.54.43.141]
6 be2993.ccr21.cle04.atlas.cogentco.com [154.54.31.225]
7 be2889.ccr41.jfk02.atlas.cogentco.com [154.54.47.50]
8 be3294.ccr31.jfk05.atlas.cogentco.com [154.54.47.218]
9 tata.jfk05.atlas.cogentco.com [154.54.12.18]
10 if-be-2-2.ecore1.n75-newyork.as6453.net [66.110.96.62]
11 72.14.221.146
12 * * *
Computing statistics for 275 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 GALAXY [100.76.28.103]
0/ 100 = 0% |
1 4ms 0/ 100 = 0% 0/ 100 = 0% 100.64.1.200
0/ 100 = 0% |
2 7ms 1/ 100 = 1% 1/ 100 = 1% 149.57.28.29
0/ 100 = 0% |
3 5ms 0/ 100 = 0% 0/ 100 = 0% be6332.nr01.b011027-7.yyz02.atlas.cogentco.com [38.32.158.65]
0/ 100 = 0% |
4 6ms 3/ 100 = 3% 3/ 100 = 3% te0-0-1-2.agr13.yyz02.atlas.cogentco.com [154.24.51.45]
0/ 100 = 0% |
5 6ms 2/ 100 = 2% 2/ 100 = 2% te0-9-0-9.ccr31.yyz02.atlas.cogentco.com [154.54.43.141]
0/ 100 = 0% |
6 14ms 1/ 100 = 1% 1/ 100 = 1% be2993.ccr21.cle04.atlas.cogentco.com [154.54.31.225]
0/ 100 = 0% |
7 24ms 0/ 100 = 0% 0/ 100 = 0% be2889.ccr41.jfk02.atlas.cogentco.com [154.54.47.50]
0/ 100 = 0% |
8 25ms 0/ 100 = 0% 0/ 100 = 0% be3294.ccr31.jfk05.atlas.cogentco.com [154.54.47.218]
0/ 100 = 0% |
9 23ms 51/ 100 = 51% 51/ 100 = 51% tata.jfk05.atlas.cogentco.com [154.54.12.18]
0/ 100 = 0% |
10 24ms 3/ 100 = 3% 3/ 100 = 3% if-be-2-2.ecore1.n75-newyork.as6453.net [66.110.96.62]
0/ 100 = 0% |
11 24ms 0/ 100 = 0% 0/ 100 = 0% 72.14.221.146
Trace complete.
Yeah, that’s what I was seeing.
Damn.
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.
1 Like
GearUp Booster is supposed to help with routing, but I’m not noticing any difference. I may try changing ISPs.
Well keep us posted.
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.
Thanks for helping out so far!
1 Like
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:
Bro I’m in Mississauga and with ROGERS. I have highest package unlimited data highest download speed Ignite.
I have the same issues for the last 3 days.
I don’t think changing ISP will fix the issue.
1 Like
I went through there 2 days ago on my way back from Ottawa.
Any chance you got to try to run those tools I linked above? Curious to see what you are getting with your connection.
TraceRT:
WinMTR:
Thanks for your help with everything. Rogers will be installing 1.5GB/s Fibre on Sunday. Will keep you posted.
The crazy hoops we go through to play a game eh? Good luck!