High Ping Spikes

Technical Support
I ran the looking glass tests, don't really know what the issue is because I don't know how to read/interpret the test itself.

TRACEROUTE:
traceroute to 75.66.194.39 (75.66.194.39), 15 hops max, 60 byte packets
1 Blizzard Blizzard 1.198 ms 1.189 ms 1.188 ms
2 24.105.18.3 (24.105.18.3) 2.163 ms 2.164 ms 2.165 ms
3 137.221.105.12 (137.221.105.12) 2.220 ms 2.250 ms 2.250 ms
4 137.221.66.16 (137.221.66.16) 2.167 ms 2.198 ms 2.198 ms
5 137.221.83.66 (137.221.83.66) 6.963 ms 6.967 ms 6.968 ms
6 * * *
7 137.221.68.32 (137.221.68.32) 6.194 ms 6.230 ms 6.544 ms
8 te-0-1-0-2-8-pe02.600wseventh.ca.ibone.comcast.net (50.242.151.165) 6.017 ms 6.029 ms 5.833 ms
9 be-11587-cr02.losangeles.ca.ibone.comcast.net (68.86.83.17) 7.157 ms 7.168 ms 7.163 ms
10 be-11523-cr01.houston.tx.ibone.comcast.net (68.86.87.174) 33.445 ms 32.928 ms 32.915 ms
11 be-12324-cr02.dallas.tx.ibone.comcast.net (68.86.84.110) 34.315 ms 32.910 ms 32.468 ms
12 be-7922-ar02.dannythomas.tn.malt.comcast.net (68.86.93.94) 41.046 ms 40.948 ms 40.912 ms
13 96.108.172.162 (96.108.172.162) 40.863 ms 40.882 ms 40.892 ms
14 96.110.140.22 (96.110.140.22) 41.054 ms 41.192 ms 41.067 ms
15 c-75-66-194-39.hsd1.tn.comcast.net (75.66.194.39) 57.099 ms 55.733 ms 53.565 ms

22/06/2019 18:02:38 UTC
--------------------

PING:
PING 75.66.194.39 (75.66.194.39) 56(84) bytes of data.
64 bytes from 75.66.194.39: icmp_seq=1 ttl=52 time=50.7 ms
64 bytes from 75.66.194.39: icmp_seq=2 ttl=52 time=51.0 ms
64 bytes from 75.66.194.39: icmp_seq=3 ttl=52 time=55.7 ms
64 bytes from 75.66.194.39: icmp_seq=4 ttl=52 time=53.6 ms

--- 75.66.194.39 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2999ms
rtt min/avg/max/mdev = 50.769/52.799/55.727/2.032 ms

22/06/2019 18:02:38 UTC
--------------------

MTR:
Start: Sat Jun 22 18:02:38 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.8 0.2 5.1 1.4
2.|-- 24.105.18.3 0.0% 10 0.7 1.0 0.4 3.0 0.7
3.|-- 137.221.105.12 0.0% 10 0.7 0.6 0.6 0.8 0.0
4.|-- 137.221.66.16 0.0% 10 0.5 0.7 0.5 0.8 0.0
5.|-- 137.221.83.66 0.0% 10 5.8 6.3 5.7 9.5 1.1
6.|-- 137.221.65.68 90.0% 10 12471 12471 12471 12471 0.0
7.|-- 137.221.68.32 0.0% 10 6.0 11.5 5.8 50.1 13.9
8.|-- te-0-1-0-2-8-pe02.600wseventh.ca.ibone.comcast.net 0.0% 10 6.1 5.8 5.6 6.1 0.0
9.|-- be-11587-cr02.losangeles.ca.ibone.comcast.net 0.0% 10 6.6 7.3 6.6 8.2 0.0
10.|-- be-11523-cr01.houston.tx.ibone.comcast.net 0.0% 10 33.4 33.3 32.8 34.3 0.3
11.|-- be-12324-cr02.dallas.tx.ibone.comcast.net 0.0% 10 33.4 33.4 32.4 34.6 0.5
12.|-- be-7922-ar02.dannythomas.tn.malt.comcast.net 0.0% 10 41.1 41.0 40.8 41.4 0.0
13.|-- 96.108.172.162 0.0% 10 41.0 40.9 40.8 41.0 0.0
14.|-- 96.110.140.22 0.0% 10 41.3 41.2 41.1 41.3 0.0
15.|-- c-75-66-194-39.hsd1.tn.comcast.net 0.0% 10 68.9 56.6 50.6 68.9 6.7

22/06/2019 18:02:38 UTC
--------------------



Anything I can do here to fix this issue? Diablo is beginning to become unplayable for me and my wife.
Hi :
06/22/2019 11:14 AMPosted by KGBINC
Diablo is beginning to become unplayable for me and my wife.
On 2 different computers but same router ? or both playing on the same computer ?

The Looking-Glass test results look normal to me.

Start with the troubleshooting here :
https://us.battle.net/support/en/article/112206 including Advanced troubleshooting. The words in blue are links you can click to get more information and procedures that you could find useful.

If the high ping issue continues after going through the troubleshooting, pls run a WinMTR test... see https://us.battle.net/support/en/article/27780 for details. Once you have captured some high ping events while playing with WinMTR running for a minimum of 5 minutes or so, stop it and post the results here.

Join the Conversation

Return to Forum