Weird Latency only in Overwatch matches

Technical Support
1

So typically, I keep a running ping to Googles servers going at all times on my secondary monitor just so I can identify any spikes. Tonight, I’ve been having a consistent spike in my ping exactly every 10 seconds ( I counted ). It’s caused my character to run off cliffs, stop shooting or moving, to miss abilities, etc. When I’m NOT in a game of Overwatch, the ping goes back to normal. I ran the WinMTR and it shows that its a spike in my network, which clearly it must be since it’s affecting my connection to Google. But why does it only happen when I’m in a game of Overwatch?

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

|                                      WinMTR statistics                                   |

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

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

|                               mynetwork -    0 |  379 |  379 |    1 |   28 |  567 |    1 |

|                              10.11.4.33 -    0 |  379 |  379 |   14 |   46 |  581 |   22 |

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

|tcore4-toronto47_hu2/14/0/1_46.net.bell.ca -    0 |  379 |  379 |   21 |   54 |  600 |   23 |

|tcore4x-london14_hundredgige0-11-0-0.net.bell.ca -    0 |  379 |  379 |   21 |   51 |  589 |   22 |

|      dis21-london14_xe7-0-0.net.bell.ca -    0 |  379 |  379 |   20 |   50 |  588 |   22 |

|tcore4-london14_tengige10-0-1.net.bell.ca -    0 |  379 |  379 |   35 |   65 |  604 |   36 |

|tcore4-toronto47_hundredgige2-8-0-1.net.bell.ca -    0 |  379 |  379 |   31 |   63 |  606 |   38 |

|tcore4-chicagocp_hundredgige0-3-0-0.net.bell.ca -    0 |  379 |  379 |   31 |   64 |  603 |   39 |

|       bx6-chicagodt_0-7-0-0.net.bell.ca -    0 |  379 |  379 |   33 |   62 |  603 |   34 |

|      blizzard_bx6-chicagodt.net.bell.ca -    0 |  379 |  379 |   33 |   66 |  608 |   35 |

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

|         et-0-0-1-pe04-eqch2.as57976.net -    0 |  379 |  379 |   31 |   66 |  598 |   32 |

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

The home network does look very laggy with a worst ping of 567ms between the computer and modem. If you’re on wifi, try resolving with a cable, or by switching the broadcast channel. If you’re on 5Ghz, try 2.4Ghz instead because it’s more stable.

It may only be happening in-game because the modem is experiencing a packet flood (might need replacing), or because the signal is too weak for 60 packets/second.

Keep in mind that your route to Google and your route to Blizzard are going to be very different, so they aren’t a good comparison for diagnosing a connection issue.

3

I contacted my ISP about it, and they said that it’s a known issue with Overwatch servers and that I should use a VPN… I think it’s time I find a new ISP.