Overwatch Ping Issues

Lately I’ve been having issues with my ping spiking for no reason. If I take a look at my Network Graph, my latency has a minimum of 0, but lately instead of having a 0 for my ping, it’s been around 60ms constantly.

I used Battle.net’s Looking Glass, and here is the report if that helps. Because you can’t post links, I replaced all links with “—”. Thanks!

TRACEROUTE:
traceroute to 104.137.14.199 (104.137.14.199), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.339 ms 0.324 ms 0.320 ms
2 37.244.23.3 (37.244.23.3) 0.511 ms 0.562 ms 0.619 ms
3 24.105.62.148 (24.105.62.148) 0.914 ms 0.971 ms 1.027 ms
4 137.221.66.8 (137.221.66.8) 2.178 ms 2.183 ms 2.181 ms
5 137.221.69.50 (137.221.69.50) 1.693 ms 1.695 ms 1.696 ms
6 137.221.69.34 (137.221.69.34) 1.620 ms 1.680 ms 1.647 ms
7 66.109.9.148 (66.109.9.148) 1.459 ms 1.380 ms 1.360 ms
8 66.109.5.224 (66.109.5.224) 19.991 ms 20.089 ms 20.076 ms
9 — (66.109.3.238) 25.555 ms 25.574 ms 25.585 ms
10 66.109.6.223 (66.109.6.223) 30.294 ms 30.289 ms 30.303 ms
11 — (72.31.238.217) 30.743 ms 30.742 ms 30.754 ms
12 — (72.31.238.198) 30.637 ms 30.818 ms 30.771 ms
13 — (104.137.14.199) 42.815 ms 43.593 ms 47.895 ms

02/08/2020 16:25:27 UTC

TRACEROUTE:
traceroute to 104.137.14.199 (104.137.14.199), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.436 ms 0.407 ms 0.403 ms
2 24.105.18.2 (24.105.18.2) 1.136 ms * *
3 137.221.105.10 (137.221.105.10) 1.126 ms 1.126 ms 1.127 ms
4 137.221.66.16 (137.221.66.16) 1.076 ms 1.089 ms 1.091 ms
5 137.221.83.80 (137.221.83.80) 152.065 ms 152.095 ms 389.070 ms
6 * * *
7 137.221.68.32 (137.221.68.32) 5.930 ms 5.941 ms 5.940 ms
8 — (66.109.9.160) 5.375 ms 6.715 ms 6.728 ms
9 66.109.5.240 (66.109.5.240) 57.638 ms 57.598 ms 55.608 ms
10 66.109.5.229 (66.109.5.229) 50.934 ms 51.047 ms 51.075 ms
11 — (66.109.3.236) 56.759 ms 56.747 ms 57.913 ms
12 66.109.6.223 (66.109.6.223) 61.548 ms 61.539 ms 61.390 ms
13 — (72.31.238.217) 61.811 ms 61.826 ms 61.478 ms
14 — (72.31.238.198) 61.360 ms 61.690 ms 61.369 ms
15 — (104.137.14.199) 72.220 ms 72.180 ms 71.750 ms

02/08/2020 16:25:27 UTC

PING:
PING 104.137.14.199 (104.137.14.199) 56(84) bytes of data.
64 bytes from 104.137.14.199: icmp_seq=1 ttl=49 time=73.3 ms
64 bytes from 104.137.14.199: icmp_seq=2 ttl=49 time=70.2 ms
64 bytes from 104.137.14.199: icmp_seq=3 ttl=49 time=70.7 ms
64 bytes from 104.137.14.199: icmp_seq=4 ttl=49 time=73.7 ms

— 104.137.14.199 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2999ms
rtt min/avg/max/mdev = 70.212/72.019/73.767/1.563 ms

02/08/2020 16:25:27 UTC

PING:
PING 104.137.14.199 (104.137.14.199) 56(84) bytes of data.
64 bytes from 104.137.14.199: icmp_seq=1 ttl=51 time=48.8 ms
64 bytes from 104.137.14.199: icmp_seq=2 ttl=51 time=39.2 ms
64 bytes from 104.137.14.199: icmp_seq=3 ttl=51 time=44.0 ms
64 bytes from 104.137.14.199: icmp_seq=4 ttl=51 time=43.0 ms

— 104.137.14.199 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 39.278/43.802/48.874/3.426 ms

02/08/2020 16:25:27 UTC

MTR:
Start: Sun Aug 2 16:25:27 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.4 0.0
2.|-- 24.105.18.2 0.0% 10 0.6 0.6 0.5 0.8 0.0
3.|-- 137.221.105.10 0.0% 10 1.0 0.8 0.6 1.0 0.0
4.|-- 137.221.66.16 0.0% 10 0.4 0.5 0.4 0.7 0.0
5.|-- 137.221.83.80 0.0% 10 162.4 344.1 70.6 1137. 372.5
6.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
7.|-- 137.221.68.32 0.0% 10 5.9 11.1 5.8 34.7 10.9
8.|-- — 0.0% 10 5.8 7.4 5.4 15.4 3.7
9.|-- 66.109.5.240 0.0% 10 55.4 54.5 51.2 57.7 2.4
10.|-- 66.109.5.229 0.0% 10 51.0 52.6 50.8 65.0 4.4
11.|-- — 0.0% 10 56.3 55.4 51.2 58.1 2.6
12.|-- 66.109.6.223 0.0% 10 61.6 61.5 61.4 61.8 0.0
13.|-- — 0.0% 10 61.6 61.6 61.4 61.8 0.0
14.|-- — 0.0% 10 61.4 61.4 61.3 61.9 0.0
15.|-- — 0.0% 10 70.0 73.8 69.4 85.9 5.3

02/08/2020 16:25:27 UTC

MTR:
Start: Sun Aug 2 16:25:27 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.4 0.0
2.|-- 37.244.23.131 0.0% 10 0.5 0.5 0.4 0.6 0.0
3.|-- 24.105.62.148 0.0% 10 1.1 1.2 1.0 1.4 0.0
4.|-- 137.221.66.8 0.0% 10 1.2 2.0 1.0 9.9 2.7
5.|-- 137.221.69.50 0.0% 10 1.5 6.5 1.3 51.5 15.8
6.|-- 137.221.69.34 0.0% 10 1.6 4.2 1.5 17.2 4.8
7.|-- 66.109.9.148 0.0% 10 1.4 1.3 1.1 2.0 0.0
8.|-- 66.109.5.224 0.0% 10 24.1 24.1 19.5 42.0 8.2
9.|-- — 0.0% 10 24.9 24.2 19.8 27.5 2.3
10.|-- 66.109.6.223 0.0% 10 31.1 30.7 30.5 31.1 0.0
11.|-- — 0.0% 10 30.9 30.8 30.5 30.9 0.0
12.|-- — 0.0% 10 30.5 30.5 30.4 30.6 0.0
13.|-- — 0.0% 10 39.7 40.6 37.7 44.3 2.0

02/08/2020 16:25:27 UTC

Hey, DubbyDubzr! The looking glass test looks fine. It’s usually only helpful for situations where we request them though.

Could you provide a WinMTR test instead? This should show us the connection from the computer to the overwatch servers. Run the test until the problem occurs for 10 to 15 minutes. Copy and paste the text file created and paste it between two ~~~ like so:

~~~
WinMTR Here
~~~

If you have issues pasting here, use Pastebin and post the end of the link. (ie. 123456 for pastebin.com/123456)

Here you go!

|------------------------------------------------------------------------------------------|

|                                      WinMTR statistics                                   |

|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

|                             192.168.0.1 -    2 | 1306 | 1281 |    2 |  152 | 4307 |   17 |

|        072-031-148-037.res.spectrum.com -    2 | 1330 | 1310 |   11 |  160 | 2710 |   32 |

|        072-031-238-193.res.spectrum.com -    3 | 1299 | 1272 |   12 |  158 | 2603 |   29 |

|        072-031-238-216.res.spectrum.com -    2 | 1324 | 1303 |   11 |  164 | 2603 |   26 |

|10.bu-ether15.atlngamq46w-bcr01.tbone.rr.com -    2 | 1309 | 1285 |   22 |  175 | 2761 |   33 |

|bu-ether18.atlngamq46-bcr00.tbone.rr.com -    1 | 1354 | 1341 |   22 |  169 | 2762 |   29 |

|                            66.109.5.125 -    2 | 1310 | 1286 |   23 |  178 | 4704 |   34 |

|                            66.109.9.107 -    2 | 1325 | 1305 |   23 |  176 | 2771 |  104 |

|              ae1-br01-eqat2.as57976.net -    3 | 1285 | 1255 |   40 |  197 | 4896 |   94 |

|                   No response from host -  100 |  285 |    0 |    0 |    0 |    0 |    0 |

|         et-0-0-1-pe03-eqch2.as57976.net -    2 | 1328 | 1308 |   40 |  186 | 2747 |   44 |

|                   No response from host -  100 |  285 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |  285 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |  285 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |  285 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |  285 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |  285 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |  285 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |  285 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |  285 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |  285 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |  285 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |  285 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |  285 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |  285 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |  285 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |  285 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |  285 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |  285 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |  285 |    0 |    0 |    0 |    0 |    0 |

|________________________________________________|______|______|______|______|______|______|

   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

| 192.168.0.1 - :warning: 2 | 1306 | 1281 | 2 | 152 | 4307 | 17 |

There’s the problem. The connection between your PC/router is pretty unstable. You’ve got latency spikes of over 4 seconds (check worst column), an average latency of 152 ms, and 2% packet loss between your PC and router. This is super bad for a connection within your house.

With this info, I’d do these things in this order. First, power cycle your connection to clear your network caches. If that fails and you’re on wifi, redo the test on ethernet instead. If it’s still this bad on ethernet, it’ll mean it’s time to replace the router most likely. Feel free to post the winMTR on ethernet here so we can give it another look.