Higher ping after switching to cable

Technical Support
1

I switched from 6 Mbps DSL to 100 Mbps cable.
My ping has gone from an average of 40 on DSL to an unstable 55-85 (with higher random spikes going into 3 digits.)
I’m playing on PC and have done all of the recommended troubleshooting.

I’ve done the looking glass with MTR, Traceroute, Ping.
I don’t really know what to make of it though. If I could get some help interpreting the results, it would be much appreciated!

Looking Glass test results

TRACEROUTE:
traceroute to 75.182.15.177 (75.182.15.177), 15 hops max, 60 byte packets
1 10.57.68.13 (10.57.68.13) 0.255 ms 0.245 ms 0.243 ms
2 37.244.23.2 (37.244.23.2) 0.705 ms 0.716 ms 0.733 ms
3 24.105.62.150 (24.105.62.150) 0.741 ms 0.873 ms 2.481 ms
4 137.221.66.10 (137.221.66.10) 3.044 ms 3.054 ms 3.056 ms
5 137.221.69.70 (137.221.69.70) 2.489 ms 2.489 ms 2.488 ms
6 137.221.69.34 (137.221.69.34) 2.476 ms 1.943 ms 1.922 ms
7 66.109.9.148 (66.109.9.148) 1.533 ms 1.526 ms 1.506 ms
8 bu-ether39.chcgildt87w-bcr00.tbone.rr.c0m (66.109.1.67) 33.556 ms 33.069 ms 33.046 ms
9 bu-ether11.nycmny837aw-bcr00.tbone.rr.c0m (66.109.6.24) 27.584 ms 27.599 ms 27.597 ms
10 bu-ether11.nwrknjmd67w-bcr00.tbone.rr.c0m (66.109.6.26) 35.020 ms 35.035 ms 34.511 ms
11 107.14.17.239 (107.14.17.239) 27.847 ms 35.123 ms 35.104 ms
12 66.109.6.81 (66.109.6.81) 38.644 ms 35.824 ms 35.816 ms
13 bundle1.mybhsc0601r.southeast.rr.c0m (24.93.64.33) 44.380 ms 44.602 ms 44.692 ms
14 mhe-mgx01-vism13.voip.southeast.rr.c0m (24.31.196.169) 58.128 ms 58.142 ms 57.630 ms
15 cpe-174-111-068-198.triad.res.rr.c0m (174.111.68.198) 46.481 ms 46.021 ms 45.701 ms

21/03/2018 16:50:55 UTC

TRACEROUTE:
traceroute to 75.182.15.177 (75.182.15.177), 15 hops max, 60 byte packets
1 10.56.100.81 (10.56.100.81) 0.454 ms 0.450 ms 0.450 ms
2 37.244.22.131 (37.244.22.131) 0.791 ms 0.861 ms 0.970 ms
3 24.105.30.152 (24.105.30.152) 1.429 ms 1.442 ms 1.444 ms
4 137.221.66.6 (137.221.66.6) 1.740 ms 1.797 ms 1.979 ms
5 137.221.68.68 (137.221.68.68) 1.678 ms 1.691 ms 1.692 ms
6 137.221.68.32 (137.221.68.32) 1.425 ms 1.184 ms 1.247 ms
7 ae34.pr1.lax10.tbone.rr.c0m (66.109.9.160) 0.954 ms 1.000 ms 0.990 ms
8 bu-ether27.tustca4200w-bcr00.tbone.rr.c0m (107.14.19.57) 69.426 ms 68.884 ms 68.922 ms
9 bu-ether16.dllstx976iw-bcr00.tbone.rr.c0m (66.109.6.1) 65.325 ms 65.349 ms 65.350 ms
10 bu-ether12.atldga10ds1-bcr00.tbone.rr.c0m (66.109.3.236) 69.384 ms 69.419 ms 68.834 ms
11 bu-ether18.atlngamq46-bcr00.tbone.rr.c0m (66.109.6.40) 65.325 ms 64.402 ms 64.384 ms
12 66.109.6.83 (66.109.6.83) 73.352 ms 72.982 ms 72.968 ms
13 be1.clmcsc3001r.southeast.rr.c0m (24.93.64.181) 72.321 ms 72.314 ms 72.453 ms
14 mhe-mgx01-vism18.voip.southeast.rr.c0m (24.31.196.171) 89.621 ms 89.097 ms 89.078 ms
15 cpe-174-111-070-102.triad.res.rr.c0m (174.111.70.102) 72.238 ms 72.344 ms 72.405 ms

21/03/2018 16:50:55 UTC

PING:
PING 75.182.15.177 (75.182.15.177) 56(84) bytes of data.
64 bytes from 75.182.15.177: icmp_seq=1 ttl=47 time=78.6 ms
64 bytes from 75.182.15.177: icmp_seq=2 ttl=47 time=78.4 ms
64 bytes from 75.182.15.177: icmp_seq=3 ttl=47 time=78.5 ms
64 bytes from 75.182.15.177: icmp_seq=4 ttl=47 time=79.1 ms

— 75.182.15.177 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2999ms
rtt min/avg/max/mdev = 78.413/78.673/79.105/0.433 ms

21/03/2018 16:50:55 UTC

PING:
PING 75.182.15.177 (75.182.15.177) 56(84) bytes of data.
64 bytes from 75.182.15.177: icmp_seq=1 ttl=49 time=53.3 ms
64 bytes from 75.182.15.177: icmp_seq=2 ttl=49 time=51.9 ms
64 bytes from 75.182.15.177: icmp_seq=3 ttl=49 time=51.4 ms
64 bytes from 75.182.15.177: icmp_seq=4 ttl=49 time=55.4 ms

— 75.182.15.177 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 3002ms
rtt min/avg/max/mdev = 51.438/53.032/55.403/1.533 ms

21/03/2018 16:50:55 UTC

MTR:
Start: Wed Mar 21 16:50:55 2018
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1.|-- 10.56.100.81 0.0% 10 0.3 0.3 0.2 0.3 0.0
2.|-- 37.244.22.131 0.0% 10 0.7 0.7 0.5 1.4 0.0
3.|-- 24.105.30.152 0.0% 10 0.9 1.0 0.8 1.1 0.0
4.|-- 137.221.66.6 0.0% 10 1.8 1.6 1.5 2.0 0.0
5.|-- 137.221.68.68 0.0% 10 1.4 1.5 1.3 2.1 0.0
6.|-- 137.221.68.32 0.0% 10 1.1 1.3 1.1 1.8 0.0
7.|-- ae34.pr1.lax10.tbone.rr.c0m 0.0% 10 1.7 1.1 0.9 1.7 0.0
8.|-- bu-ether27.tustca4200w-bcr00.tbone.rr.c0m 0.0% 10 68.8 67.9 64.0 70.4 2.4
9.|-- bu-ether16.dllstx976iw-bcr00.tbone.rr.c0m 0.0% 10 66.5 67.7 63.7 71.5 2.7
10.|-- bu-ether12.atldga10ds1-bcr00.tbone.rr.c0m 0.0% 10 64.0 67.5 64.0 71.1 2.4
11.|-- bu-ether18.atlngamq46-bcr00.tbone.rr.c0m 0.0% 10 69.9 68.3 65.2 71.4 2.3
12.|-- 66.109.6.83 0.0% 10 72.1 73.0 69.4 75.9 2.3
13.|-- be1.clmcsc3001r.southeast.rr.c0m 0.0% 10 72.2 72.3 72.1 73.1 0.0
14.|-- mhe-mgx01-vism18.voip.southeast.rr.c0m 0.0% 10 92.0 118.7 80.8 284.2 67.3
15.|-- cpe-174-111-070-102.triad.res.rr.c0m 0.0% 10 73.0 73.0 72.5 73.3 0.0
16.|-- cpe-75-182-15-177.sc.res.rr.c0m 0.0% 10 78.4 79.8 76.8 83.4 1.8

21/03/2018 16:50:55 UTC

MTR:
Start: Wed Mar 21 16:50:55 2018
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1.|-- 10.57.68.13 0.0% 10 0.3 0.3 0.3 0.5 0.0
2.|-- 37.244.23.2 0.0% 10 0.5 0.6 0.5 1.1 0.0
3.|-- 24.105.62.150 0.0% 10 1.1 1.5 0.9 3.7 0.7
4.|-- 137.221.66.10 0.0% 10 2.9 2.6 2.3 3.7 0.3
5.|-- 137.221.69.70 0.0% 10 2.5 2.7 2.4 3.7 0.3
6.|-- 137.221.69.34 0.0% 10 2.0 4.0 1.7 18.7 5.3
7.|-- 66.109.9.148 0.0% 10 1.6 3.0 1.5 11.8 3.3
8.|-- bu-ether39.chcgildt87w-bcr00.tbone.rr.c0m 0.0% 10 32.3 31.3 27.4 34.2 2.2
9.|-- bu-ether11.nycmny837aw-bcr00.tbone.rr.c0m 0.0% 10 28.4 31.0 27.9 35.2 2.4
10.|-- bu-ether11.nwrknjmd67w-bcr00.tbone.rr.c0m 0.0% 10 29.0 30.8 27.5 35.2 2.2
11.|-- 107.14.17.239 0.0% 10 31.8 31.9 27.6 35.8 2.5
12.|-- 66.109.6.81 0.0% 10 37.3 37.0 33.6 40.2 2.1
13.|-- gig1-1-0.fyvlncr-rtr1.southeast.rr.c0m 0.0% 10 44.5 44.2 44.0 44.5 0.0
14.|-- mhe-mgx01-vism13.voip.southeast.rr.c0m 0.0% 10 58.3 76.1 55.1 202.1 44.4
15.|-- cpe-174-111-068-198.triad.res.rr.c0m 0.0% 10 46.3 46.0 45.6 46.6 0.0
16.|-- cpe-75-182-15-177.sc.res.rr.c0m 0.0% 10 51.8 53.4 51.6 55.7 1.1

21/03/2018 16:50:55 UTC

2

This may or may not be a problem. First please note there was a recent change to Overwatch which merged the PING and RTT measurements into a single value now called latency which updates more frequently than the other two. Check this developer post for details:

I can’t tell if there is anything wrong with only the Looking Glass test, so you may want to consider posting a WinMTR test if the connection is not performing to your expectations.

3

Thanks for the reply. I’m aware of that. For ping, I’m using the “Ctrl + Shift + N” PNG stat.

Okay, I’ll do that. Am I able to use the training mode for it? Or is an actual game better?

4

Training mode if you are trying to do really heavy troubleshooting, you would still be connecting to the same set of servers.

5

Thanks!

WinMTR Results

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
HG6Box 1 1595 1594 1 3 228 1
cpe-75-182-0-1.sc.res.rr.com 1 1595 1594 7 14 402 16
cpe-174-111-068-093.triad.res.rr.com 1 1595 1594 14 47 403 32
mhe-mgx01-vism12.voip.southeast.rr.com 0 1599 1599 9 17 430 14
xe1-1-2.rlghncpop-rtr1.southeast.rr.com 1 1595 1594 17 27 294 26
bu-ether15.asbnva1611w-bcr00.tbone.rr.com 1 1595 1594 23 34 271 30
66.109.1.47 1 1591 1589 22 32 270 27
ae-14-0.ar0.dca10.tbone.rr.com 1 1591 1589 23 30 281 32
ae1-br01-eqdc2.blizzardonline.net 1 1595 1594 24 32 368 28
No response from host 100 321 0 0 0 0 0
be1-pe01-eqch2.blizzardonline.net 1 1595 1594 49 55 371 54
No response from host 100 321 0 0 0 0 0
24.105.62.151 1 1595 1594 50 65 686 65
24.105.43.73 1 1595 1594 50 57 377 52
6

Thanks for posting, I am not seeing much wrong with these test results (short of two hubs which are known for not reporting back data), your average ping rate to the game server appears to be 57 milliseconds with steady and healthy intervals between each hub.

1 Like