For everyone having connection issues of various types: UPDATE 6-9-24

Technical Support
202

If i understand correctly, these days you can no longer track the whole path - you can only see whether something is wrong on the first few steps and then it is internet soup and untrackable.

203

Yeah, you are showing a small amount of loss as it moves through the network. I look at how many packets sent and received as they move through. You see it drops 8-9 packets before it goes to the end.

Remember, it doesn’t take much loss to cause issues. 1-2% is capable of causing problems for things like games, voice & video calls, etc.

But overall, that doesn’t look bad, but those are probably nodes at your ISP. And as I noted above, I think some ISPs don’t like D4’s traffic.

Your trace to battlenet shows a spike in latency when reaching them, that’s for sure.

The rest looks good.

How long did you run the test? I usually recommend for at least 5 minutes. And if you did run it 5 minutes, yikes. Assuming that, something is blocking you at the beginning. But if you only ran this for a short few seconds, then it only sent 10 packets and that means its working fine, as it shows 10 packets till the servers stop responding.

But run it longer and while playing the game, especially when having issues.

Its not stuck so much as not getting a response. This is actually normal. Most of these tools aren’t modern enough for IPv6, and many servers are configured not to respond to these requests.

These can show problems, but have to take some of it with a grain of salt.

At face value your tests looks ok.

204

this is exactly what happens to me also. started around the same time posting. had no issues during beta and launch. only this game.

205

this forum is for collecting info you guys all know is a server issue on you guys side also you guys not listen to people they want play the game and want a offline mode and you guys are not listen or fix the issue there is some info for youand im not alone

1 Like
206

Then by all means, start your own thread.

So far you have:

  • Not contributed to this thread by doing any testing to show where your problems might be.
  • Posted with somewhat blame ridden replies. (And I understand you are frustrated)
  • Continuing to disrupt the thread, despite my requests to either help out or start your own thread.

So by all means, please do so.

Thank you.

1 Like
207

So today i tried two different things - VPN and lowering security on my router firewall since you mentioned that some ISPs don’t like how D4 acts - i have to say that while i did eventually disconnect, i was able to play for longer stretches of time (couple of hours) without disruption with each method. I don’t know if it’s coincidence or a “solution”.

208

Well, those are two things that some have tried that have helped, so I would call it a work around if nothing else.

I still think there is just something about the D4 connection traffic that some stuff just doesn’t want to get along with.

1 Like
210

Well. I’ve been having really bad lag for weeks now (it wasn’t always this bad, it worked PERFECTLY in open beta/server slam but since the game went live I haven’t been able to play the game without spiking to 500+ ms consistently. Did a server trace and it looks a lot different from the others I see on here.

1 <1 ms <1 ms <1 ms BroadcomHome [0]
2 12 ms 13 ms 12 ms 0
3 27 ms 27 ms 27 ms e0-49.switch2.stl2.he.(net) [184.105.38.181]
4 44 ms 31 ms * port-channel14.core3.chi1.he.(net) [184.104.197.241]
5 33 ms 33 ms 32 ms eqix-ch-200g-1.(google.com) [208.115.136.21]
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 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

I’ve done it on both the West and Central US servers with the same results. Any help would be appreciated.

Had to put ( ) around some of them cause it wouldn’t let me post anything with links lol

1 Like
211

Well, that just shows primarily your latency/ping. And it looks good here to be honest.

Have you tried any of the other tools in the first post?

If you do, use the Export HTML to clipboard and just paste into your reply, it will format it correctly.

Anytime you run into an issue with website names in results and not letting you post, highlight and use the </> button in the reply box menu, or put these around it → ` ← This is from the key to the left of number 1.

213

And you are posting hate filled replies all over the forums. You are now ignored. Thanks and have a nice day.

214

I am having serious network issues with diablo IV, Ran MTR, ran ping test I average 74ms, when I play world of warcraft and can select my server my ping is 60-70s I am currently averaging 144ms to 1000ms with spikes. I believe the issue is with the auto connect server switching in Diablo IV. Maybe something to do with the cross play function with consoles?? Blizzard auto feature that won’t allow us to connect to a proper server is hurting a lot of people

WinMTR statistics |

Host - % Sent Recv Best Avrg Wrst Last
GT-AX6000-8050 - 1 752 751 0 0 15 0
142-254-190-073.inf.spectrum. - 1 752 751 0 11 32 12
lag-62.wphuhi0501h.netops.charter. - 1 745 742 0 33 201 22
lag-39.milnhixd01r.netops.charter. - 1 752 751 0 12 34 12
lag-31.lsancarc01r.netops.charter. - 1 752 751 0 85 597 81
lag-16.lsancarc0yw-bcr00.netops.charter. - 1 752 751 0 73 146 81
74.125.48.188 - 1 752 751 0 76 148 77
No response from host - 100 153 0 0 0 0 0
No response from host - 100 153 0 0 0 0 0
No response from host - 100 153 0 0 0 0 0
No response from host - 100 153 0 0 0 0 0
No response from host - 100 153 0 0 0 0 0
No response from host - 100 153 0 0 0 0 0
No response from host - 100 153 0 0 0 0 0
No response from host - 100 153 0 0 0 0 0
No response from host - 100 153 0 0 0 0 0
No response from host - 100 153 0 0 0 0 0
No response from host - 100 153 0 0 0 0 0
No response from host - 100 153 0 0 0 0 0
No response from host - 100 153 0 0 0 0 0
No response from host - 100 153 0 0 0 0 0
No response from host - 100 153 0 0 0 0 0
No response from host - 100 153 0 0 0 0 0
No response from host - 100 153 0 0 0 0 0
No response from host - 100 153 0 0 0 0 0
No response from host - 100 153 0 0 0 0 0
No response from host - 100 153 0 0 0 0 0
No response from host - 100 153 0 0 0 0 0
No response from host - 100 153 0 0 0 0 0
No response from host - 100 153 0 0 0 0 0
________________________________________________ ______ ______ ______ ______ ______ ______
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Tracing route to battle.net [137.221.106.104]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms GT-AX6000-8050 [192.168.50.1]
2 9 ms 10 ms 8 ms 142-254-190-073.inf.spectrum [142.254.190.73]
3 24 ms 31 ms 22 ms lag-62.wphuhi0501h.netops.charter [24.25.228.145]
4 10 ms 11 ms 10 ms lag-39.milnhixd01r.netops.charter [72.129.47.116]
5 78 ms 81 ms 82 ms lag-31.lsancarc01r.netops.charter [72.129.45.0]
6 * * 100 ms lag-36.lsancarc0yw-bcr00.netops.charter [66.109.6.92]
7 71 ms 69 ms 71 ms lag-0.pr2.lax10.netops.charter [66.109.5.135]
8 81 ms 68 ms 71 ms 24.30.201.95
9 300 ms 412 ms 219 ms ae1-br01-eqla1.as57976 [137.221.68.33]
10 * * * Request timed out.
11 78 ms 78 ms 81 ms et-0-0-0-pe03-swlv10.as57976 [137.221.83.85]
12 75 ms 74 ms 75 ms las-swlv10-ia-bons-03.as57976 [137.221.66.21]
13 73 ms 75 ms 76 ms 137.221.105.13
14 77 ms 74 ms 76 ms 137.221.106.104

Trace complete.

C:\Windows\System32>tracert 34.105.4.61 (Diablo IV)

Tracing route to 61.4.105.34.bc.googleusercontent [34.105.4.61]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms GT-AX6000-8050 [192.168.50.1]
2 10 ms 11 ms 10 ms 142-254-190-073.inf.spectrum [142.254.190.73]
3 28 ms 22 ms 21 ms lag-62.wphuhi0501h.netops.charter [24.25.228.145]
4 10 ms 10 ms 11 ms lag-39.milnhixd01r.netops.charter [72.129.47.116]
5 222 ms 84 ms 80 ms lag-31.lsancarc01r.netops.charter [72.129.45.0]
6 71 ms 74 ms 69 ms lag-16.lsancarc0yw-bcr00.netops.charter [66.109.6.102]
7 73 ms 73 ms 75 ms 74.125.48.188
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.

215

Honestly, this looks really good. You are only showing 1 packet lost. So yeah, nothing wrong in your vicinity, or your hardware, according to that.

Ok, on the next test, I see a bit of latency added at Charter, but its not horrible.

This looks worse:

So whatever that is, it may be causing some loss for sure, and that’s with you pinging battle.net

You might try using that with other websites, like google or twitter, or something, see if you see that same node give you the same hit with latency. If so, that’s why you are having some issues.

Let me amend that.

This is showing a potential source for issues, but it also may be falsely showing this.

216

These are from the past 2 nights. I randomly lag out for 5+ seconds, some nights being longer than 10 seconds.

ISP: Comcast; Hardwired connection
VPN: None

Ping to battle.net

Ping statistics for 137.221.106.104: Packets: Sent = 556, Received = 554, Lost = 2 (0% loss), Approximate round trip times in milli-seconds: Minimum = 25ms, Maximum = 50ms, Average = 38ms

WinMTR Statistics

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
192.168.1.1 0 3160 3160 0 6 18 2
10.60.232.195 1 3103 3088 12 41 181 46
96.110.179.253 1 3103 3088 9 22 61 21
96.108.99.69 1 3103 3088 11 22 54 13
68.85.86.173 1 3103 3088 9 22 47 13
ae-199-rar01.santaclara.ca.sfba.comcast.net 1 3068 3044 11 23 419 13
be-39911-cs01.sunnyvale.ca.ibone.comcast.net 2 3003 2962 11 28 110 30
be-1112-cr12.sunnyvale.ca.ibone.comcast.net 1 3078 3056 11 27 54 30
be-303-cr12.9greatoaks.ca.ibone.comcast.net 1 3103 3088 11 27 65 32
be-1412-cs04.9greatoaks.ca.ibone.comcast.net 1 3103 3088 10 27 143 23
be-2412-pe12.9greatoaks.ca.ibone.comcast.net 68 863 279 11 24 36 17
66.208.233.94 68 863 279 12 25 45 28
No response from host 100 641 0 0 0 0 0
No response from host 100 641 0 0 0 0 0
No response from host 100 641 0 0 0 0 0
No response from host 100 641 0 0 0 0 0
No response from host 100 641 0 0 0 0 0
No response from host 100 641 0 0 0 0 0
No response from host 100 641 0 0 0 0 0
No response from host 100 641 0 0 0 0 0
No response from host 100 641 0 0 0 0 0
No response from host 100 641 0 0 0 0 0
No response from host 100 641 0 0 0 0 0
No response from host 100 641 0 0 0 0 0
No response from host 100 641 0 0 0 0 0
No response from host 100 641 0 0 0 0 0
No response from host 100 641 0 0 0 0 0
No response from host 100 641 0 0 0 0 0
No response from host 100 641 0 0 0 0 0
No response from host 100 641 0 0 0 0 0
WinMTR Statistics

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
192.168.1.1 0 2517 2517 0 6 18 10
10.60.232.195 1 2498 2493 13 41 171 25
96.110.179.253 1 2498 2493 11 23 322 14
96.108.99.69 1 2498 2493 11 22 46 12
68.85.86.173 1 2494 2488 11 23 46 14
68.87.192.162 1 2501 2497 11 22 42 17
68.87.193.177 1 2498 2493 11 28 91 25
be-39921-cs02.9greatoaks.ca.ibone.comcast.net 1 2498 2493 11 27 53 33
be-2212-pe12.9greatoaks.ca.ibone.comcast.net 1 2498 2493 12 27 56 27
66.208.233.94 1 2498 2493 11 27 53 25
No response from host 100 511 0 0 0 0 0
No response from host 100 511 0 0 0 0 0
No response from host 100 511 0 0 0 0 0
No response from host 100 511 0 0 0 0 0
No response from host 100 511 0 0 0 0 0
No response from host 100 511 0 0 0 0 0
No response from host 100 511 0 0 0 0 0
No response from host 100 511 0 0 0 0 0
No response from host 100 511 0 0 0 0 0
No response from host 100 511 0 0 0 0 0
No response from host 100 511 0 0 0 0 0
No response from host 100 511 0 0 0 0 0
No response from host 100 511 0 0 0 0 0
No response from host 100 511 0 0 0 0 0
No response from host 100 511 0 0 0 0 0
No response from host 100 511 0 0 0 0 0
No response from host 100 511 0 0 0 0 0
No response from host 100 511 0 0 0 0 0
No response from host 100 511 0 0 0 0 0
No response from host 100 511 0 0 0 0 0
217

While you’re averages here look good, you have gotten some really high spikes with Comcast as shown here:

There is a bit of loss to the first hop as well. But this doesn’t mean your ISP is completely at fault.

Your symptoms are in-line with others on Comcast. Meaning there is something about the D4 traffic that Comcast doesn’t like.

However, I will also admit that Comcast can be problematic at times for everything else too.

218

This a tracert to google then to the diablo IV ip address supplied by blizzard then to twitter

C:\Windows\System32>tracert www.google.com

Tracing route to <www.google.com.> [142.250.188.228]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms GT-AX6000-8050 [192.168.50.1]
2 10 ms 10 ms 9 ms 142-254-190-073.inf.spectrum [142.254.190.73]
3 26 ms 20 ms 22 ms lag-62.wphuhi0501h.netops.charter [24.25.228.145]
4 10 ms 9 ms 11 ms lag-39.milnhixd01r.netops.charter [72.129.47.116]
5 78 ms 79 ms 78 ms lag-31.lsancarc01r.netops.charter [72.129.45.0]
6 71 ms 71 ms 70 ms lag-16.lsancarc0yw-bcr00.netops.charter [66.109.6.102]
7 71 ms 71 ms 71 ms 24.30.201.155
8 71 ms 71 ms 69 ms 142.251.226.191
9 72 ms 72 ms 70 ms 142.251.60.129
10 72 ms 70 ms 68 ms lax31s15-in-f4.1e100 [142.250.188.228]

Trace complete.

C:\Windows\System32>tracert 34.105.4.61 (d4 server)

Tracing route to 61.4.105.34.bc.googleusercontent [34.105.4.61]
over a maximum of 30 hops:

1 * <1 ms <1 ms GT-AX6000-8050 [192.168.50.1]
2 14 ms 16 ms 8 ms 142-254-190-073.inf.spectrum [142.254.190.73]
3 24 ms 31 ms 28 ms lag-62.wphuhi0501h.netops.charter [24.25.228.145]
4 13 ms 9 ms 9 ms lag-39.milnhixd01r.netops.charter [72.129.47.116]
5 81 ms 84 ms 79 ms lag-31.lsancarc01r.netops.charter [72.129.45.0]
6 71 ms 70 ms 74 ms lag-16.lsancarc0yw-bcr00.netops.charter [66.109.6.102]
7 75 ms 74 ms 73 ms 74.125.48.188
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 * ^C

Tracing route to twitter [104.244.42.129]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms GT-AX6000-8050 [192.168.50.1]
2 11 ms 14 ms 9 ms 142-254-190-073.inf.spectrum [142.254.190.73]
3 28 ms 21 ms 33 ms lag-62.wphuhi0501h.netops.charter [24.25.228.145]
4 11 ms 9 ms 8 ms lag-39.milnhixd01r.netops.charter [72.129.47.116]
5 79 ms 78 ms 107 ms lag-31.lsancarc01r.netops.charter [72.129.45.0]
6 79 ms 72 ms 70 ms lag-26.lsancarc0yw-bcr00.netops.charter [66.109.3.230]
7 70 ms 80 ms 69 ms lag-3.pr2.lax10.netops.charter [107.14.19.41]
8 69 ms 69 ms 69 ms r-199-59-151-94.twttr [199.59.151.94]
9 * * * Request timed out.
10 93 ms 91 ms 94 ms 104.244.42.129

C:\Windows\System32>tracert 137.221.105.2 (US. West WoW server)

Tracing route to 137.221.105.2 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms GT-AX6000-8050 [192.168.50.1]
2 10 ms 10 ms 10 ms 142-254-190-073.inf.spectrum [142.254.190.73]
3 23 ms 26 ms 27 ms lag-62.wphuhi0501h.netops.charter [24.25.228.145]
4 10 ms 11 ms 10 ms lag-39.milnhixd01r.netops.charter [72.129.47.116]
5 78 ms 78 ms 79 ms lag-31.lsancarc01r.netops.charter [72.129.45.0]
6 103 ms 72 ms 73 ms lag-46.lsancarc0yw-bcr00.netops.charter [209.18.43.62]
7 71 ms 71 ms 78 ms lag-3.pr2.lax10.netops.charter [107.14.19.41]
8 71 ms 70 ms 69 ms 24.30.201.95
9 265 ms 594 ms 219 ms ae1-br01-eqla1.as57976 [137.221.68.33]
10 * * * Request timed out.
11 77 ms 77 ms 76 ms et-0-0-0-pe02-swlv10.as57976 [137.221.83.83]
12 77 ms 73 ms 74 ms las-swlv10-ia-bons-02.as57976 [137.221.66.19]
13 75 ms 74 ms 74 ms 137.221.105.2

219

Yeah, overall, that looks good.

Here is the only one I saw, during your WoW test:

I mean, that looks horrible, but that may not mean anything. If you look past it, the latency to the rest is normal.

220

I’ve been going back and forth with Blizzard customer support for 2 weeks in a ticket. Today their “answered” response was to link me articles from 6 years about about modems that are the same make but not model and claiming it’s my modem’s fault and my ISP’s fault. I sent them all the info that they requested and even told them about the tech that came out to specifically test if the modem was blocking traffic and was the cause of the issues my husband and I have been having for weeks now. We even replaced the modem as well.

They claim that since it isn’t a widespread issue that it must be on my end and not D4’s end, which is absolute garbage as there have been players like myself that have been having these issues for weeks now. They also suggested a hotspot which isn’t a fix at all as well as the fact that my pc doesnt even have a wireless card so I can’t even do that. If it was my modem (which again I sent them my model number and got 6 bs links about other model numbers dating back to 2016) and isp then I would be having issues with more than just Diablo 4 but I’m not and have not had any issues aside from this game.

They clearly don’t care about those of us having these lagging and disconnect issues.

221

Yeah, despite the fact we have a lot of evidence to the contrary, I’m not surprised at all. They have had no acknowledgment of these issues since they started being discovered.

222

It was the complete “there is no widespread issue” not to mention sending me links about modems that aren’t even mine. Imo you asking people for test results and telling people what they mean has done more to help than anything blizzard has so far.

223

I can’t play game due to lag for 4 days. thanks blizz

1 Like