Ping Issues in Game

Technical Support
1

I’ve been having ping issues lately, with spikes going up to 300ms, and averaging around 150-200ms in game. I haven’t changed anything on my end, and I’m going crazy trying to figure out what the problem is. Here’s the Looking Glass output. Any ideas? Thanks!

TRACEROUTE:
traceroute to 67.80.187.5 (67.80.187.5), 15 hops max, 60 byte packets
1 Blizzard Blizzard 4.408 ms 4.380 ms 4.374 ms
2 24.105.18.2 (24.105.18.2) 4.367 ms 4.363 ms 4.360 ms
3 137.221.105.10 (137.221.105.10) 4.354 ms 4.350 ms 4.346 ms
4 137.221.66.20 (137.221.66.20) 4.339 ms 4.335 ms 4.330 ms
5 137.221.83.84 (137.221.83.84) 1511.905 ms 1512.550 ms 1512.567 ms
6 * * *
7 137.221.69.32 (137.221.69.32) 40.760 ms 38.654 ms 38.651 ms
8 rtr2.in.chcgildt.cv. net (208.115.136.56) 38.587 ms 38.412 ms 38.862 ms
9 64.15.0.199 (64.15.0.199) 61.255 ms 61.015 ms 61.306 ms
10 64.15.3.93 (64.15.3.93) 64.462 ms 63.971 ms 63.975 ms
11 67.59.239.90 (67.59.239.90) 64.121 ms 64.108 ms 64.731 ms
12 ool-4353e795.dyn.optonline. net (67.83.231.149) 65.391 ms 65.185 ms 65.071 ms
13 cbr104-te5-1-0.cmts.smfrct.cv. net (67.59.232.37) 64.526 ms 64.758 ms 64.530 ms
14 * * *
15 * * *

18/12/2020 02:33:17 UTC

TRACEROUTE:
traceroute to 67.80.187.5 (67.80.187.5), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.319 ms 0.301 ms 0.299 ms
2 37.244.23.131 (37.244.23.131) 1.020 ms 1.074 ms 1.191 ms
3 24.105.62.152 (24.105.62.152) 0.873 ms 0.878 ms 0.877 ms
4 137.221.66.14 (137.221.66.14) 1.281 ms 1.285 ms 1.285 ms
5 * * *
6 137.221.69.32 (137.221.69.32) 2.246 ms 1.984 ms 2.366 ms
7 rtr2.in.chcgildt.cv. net (208.115.136.56) 1.277 ms 1.278 ms 1.291 ms
8 64.15.0.199 (64.15.0.199) 24.427 ms 25.365 ms 25.341 ms
9 64.15.3.93 (64.15.3.93) 31.364 ms 27.217 ms 27.211 ms
10 64.15.8.171 (64.15.8.171) 27.188 ms 27.194 ms 27.194 ms
11 ool-4353e797.dyn.optonline. net (67.83.231.151) 29.052 ms 29.054 ms 29.637 ms
12 67.59.230.213 (67.59.230.213) 29.004 ms 27.916 ms 27.556 ms
13 * * *
14 * * *
15 * * *

18/12/2020 02:33:18 UTC

PING:
PING 67.80.187.5 (67.80.187.5) 56(84) bytes of data.

— 67.80.187.5 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2998ms

18/12/2020 02:33:17 UTC

PING:
PING 67.80.187.5 (67.80.187.5) 56(84) bytes of data.

— 67.80.187.5 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2998ms

18/12/2020 02:33:18 UTC

MTR:
Start: Fri Dec 18 02:33:17 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.5 0.5 0.3 0.7 0.0
2.|-- 24.105.18.2 0.0% 10 0.6 1.0 0.5 4.0 0.9
3.|-- 137.221.105.10 0.0% 10 0.7 0.8 0.6 1.1 0.0
4.|-- 137.221.66.20 0.0% 10 0.6 1.9 0.4 13.9 4.2
5.|-- 137.221.83.84 0.0% 10 1337. 867.1 43.0 1337. 442.1
6.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
7.|-- 137.221.69.32 0.0% 10 38.2 42.2 38.1 66.9 9.2
8.|-- rtr2.in.chcgildt.cv. net 0.0% 10 37.9 38.2 37.7 39.6 0.0
9.|-- 64.15.0.199 0.0% 10 60.9 60.9 60.6 61.1 0.0
10.|-- 64.15.3.93 0.0% 10 63.8 63.8 63.5 64.1 0.0
11.|-- 67.59.239.90 0.0% 10 63.8 64.8 63.6 69.6 1.9
12.|-- ool-4353e795.dyn.optonline. net 0.0% 10 64.8 64.8 64.6 65.2 0.0
13.|-- cbr104-te5-1-0.cmts.smfrct.cv. net 0.0% 10 64.3 64.6 64.2 66.2 0.3
14.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

18/12/2020 02:33:17 UTC

MTR:
Start: Fri Dec 18 02:33:18 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.6 0.4 0.3 0.6 0.0
2.|-- 37.244.23.131 0.0% 10 0.7 0.7 0.5 1.0 0.0
3.|-- 24.105.62.152 0.0% 10 1.0 1.0 0.8 1.2 0.0
4.|-- 137.221.66.14 0.0% 10 1.3 13.0 1.2 118.4 37.0
5.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
6.|-- 137.221.69.32 0.0% 10 2.1 7.9 1.9 36.6 12.2
7.|-- rtr2.in.chcgildt.cv. net 0.0% 10 1.7 1.6 1.2 1.9 0.0
8.|-- 64.15.0.199 0.0% 10 24.2 24.4 24.2 24.6 0.0
9.|-- 64.15.3.93 0.0% 10 27.4 27.5 27.1 28.1 0.0
10.|-- 64.15.8.171 0.0% 10 27.5 27.5 27.3 27.7 0.0
11.|-- ool-4353e797.dyn.optonline. net 0.0% 10 28.8 28.9 28.7 29.2 0.0
12.|-- 67.59.230.213 0.0% 10 27.7 27.8 27.7 28.0 0.0
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

18/12/2020 02:33:18 UTC

2

This ping isn’t successful, which is usually the sign of a connection issue. However, unless you’re playing on console only, you’d want to use the WinMTR mentioned at the top of the forum.

3

Thanks Nicole, here’s the WinMTR output:

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                          Docsis-Gateway -    0 |  490 |  490 |    0 |    1 |   12 |    1 |
|                          10.240.180.113 -    4 |  433 |  418 |    6 |   46 |  388 |    8 |
|                            67.59.232.30 -    4 |  433 |  418 |    7 |   46 |  389 |   12 |
|          ool-4353e796.dyn.optonline.net -    4 |  433 |  418 |    8 |   46 |  393 |   12 |
|                             64.15.8.170 -    4 |  433 |  418 |    8 |   47 |  391 |    9 |
|              451be0ee.cst.lightpath.net -    4 |  437 |  423 |    9 |   48 |  390 |   18 |
|          nyiix.eqny8.blizzardonline.net -    4 |  437 |  423 |    9 |   51 |  393 |   22 |
|              ae1-br01-eqny8.as57976.net -    2 |  454 |  445 |   32 |  154 | 2088 |   47 |
|                   No response from host -  100 |   99 |    0 |    0 |    0 |    0 |    0 |
|         et-0-0-1-pe04-eqch2.as57976.net -    4 |  433 |  418 |   30 |   72 |  414 |   31 |
|                   No response from host -  100 |   99 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   99 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   99 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   99 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   99 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   99 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   99 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   99 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   99 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   99 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   99 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   99 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   99 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   99 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   99 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   99 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   99 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   99 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   99 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   99 |    0 |    0 |    0 |    0 |    0 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
4

The first node in the ISP’s network is showing packet loss, as well as high response times. This isn’t something you can fix on your own and will require contacting the ISP to get them started a resolution for it.

1 Like