Frequent ping spikes

Came back after a long break and remembered why I stopped playing - frequent ping spikes. Here are my looking-glass and WinMTR results:

looking-glass


TRACEROUTE:
traceroute to 24.246.43.90 (24.246.43.90), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  0.276 ms  0.284 ms  0.527 ms
 2  24.105.18.130 (24.105.18.130)  0.622 ms  0.647 ms  0.724 ms
 3  137.221.105.10 (137.221.105.10)  0.810 ms  0.844 ms  0.857 ms
 4  137.221.66.20 (137.221.66.20)  10.755 ms  10.802 ms  10.831 ms
 5  137.221.83.84 (137.221.83.84)  887.259 ms  887.274 ms  887.289 ms
 6  * * *
 7  137.221.69.32 (137.221.69.32)  37.976 ms  38.205 ms  38.220 ms
 8  eqix-ch1-ix.teksavvy.com (208.115.136.65)  48.059 ms  48.306 ms  48.322 ms
 9  ae8-0-bdr01-tor2.teksavvy.com (206.248.155.9)  59.305 ms  59.389 ms  59.484 ms
10  ae1-0-agg01-tor.teksavvy.com (206.248.155.18)  59.142 ms  58.867 ms  58.910 ms
11  ajax.rcable-tsi.tor.teksavvy.com (104.195.128.2)  48.682 ms  49.667 ms  48.623 ms
12  7.96.3.185 (7.96.3.185)  51.439 ms  51.513 ms  52.708 ms
13  * * *
14  * * *
15  * * *


18/10/2020 03:08:20 UTC
--------------------

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

--- 24.246.43.90 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2999ms



18/10/2020 03:08:20 UTC
--------------------

MTR:
Start: Sun Oct 18 03:08:20 2020 Blizzard  1.|-- Blizzard                     0.0%    10    0.4   0.4   0.3   0.5   0.0
  2.|-- 24.105.18.130                     0.0%    10    0.7   1.4   0.7   5.8   1.4
  3.|-- 137.221.105.10                    0.0%    10    0.9   1.0   0.9   1.1   0.0
  4.|-- 137.221.66.20                     0.0%    10    0.6   0.8   0.4   2.1   0.3
  5.|-- 137.221.83.84                     0.0%    10  775.7 717.7 179.0 1234. 348.6
  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.5  38.2  67.1   9.3
  8.|-- eqix-ch1-ix.teksavvy.com          0.0%    10   48.9  50.5  48.1  55.9   2.9
  9.|-- ae8-0-bdr01-tor2.teksavvy.com     0.0%    10   64.3  60.5  59.4  64.3   1.6
 10.|-- ae1-0-agg01-tor.teksavvy.com      0.0%    10   59.2  59.5  59.1  61.9   0.7
 11.|-- ajax.rcable-tsi.tor.teksavvy.com  0.0%    10   48.7  49.0  48.7  50.3   0.3
 12.|-- 7.96.3.185                       70.0%    10   50.7  51.2  50.7  51.6   0.0
 13.|-- ???                              100.0    10    0.0   0.0   0.0   0.0   0.0


18/10/2020 03:08:20 UTC
--------------------

And for the WinMTR

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

|                                      WinMTR statistics                                   |

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

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

|                         router.asus.com -    0 |  511 |  511 |    1 |   38 | 2305 |    1 |

|         24-246-43-65.cable.teksavvy.com -    1 |  507 |  506 |    6 |   48 | 2595 |   14 |

|        ajax.rcable-tsi.tor.teksavvy.com -    1 |  507 |  506 |    8 |   50 | 2640 |   14 |

|       ajax.tsi-rcable.tor2.teksavvy.com -    1 |  504 |  502 |    9 |   54 | 2686 |   15 |

|          ae10-0-bdr01-tor2.teksavvy.com -    1 |  507 |  506 |   11 |   54 | 2678 |   16 |

|           ae12-0-bdr01-tor.teksavvy.com -    1 |  507 |  506 |    9 |   53 | 2688 |   21 |

|                eqix-ix-ch1.blizzard.com -    1 |  507 |  506 |   20 |   65 | 2694 |   22 |

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

|         et-0-0-1-pe04-eqch2.as57976.net -    1 |  507 |  506 |   20 |   67 | 2679 |   25 |

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Hopefully someone could help me :frowning:

WinMTR shows a huge latency spike between your PC and ASUS router, and then packet loss after the router once the connection hits the Teksavvy network.

A 2k latency spike like that we often see because of wireless, so if you’re using wifi try switching to wired if possible and power cycle the router.

If you’re still seeing issues after that you may want to reach out to your ISP about the packet loss on the 2nd hop so they can check that out. Packet loss like this can definitely cause ping spikes in Overwatch.

Hope that helps. :slight_smile:

1 Like

Thanks for the reply!

I am aware that using wireless is inferior to wired, but I didn’t know it will affect my gameplay by that much. Especially if my other games does fine on wireless. Nevertheless, I need to work on getting my pc wired.

Thanks for the help! Might be back soon if getting wired doesn’t work out.