Persistent connection lag after getting new PC

I recently got a new PC and every other game runs perfectly, but as soon as I play Overwatch, as I join a game my ping increases to over 1000 in a matter of seconds before disconnecting me from the game entirely, I am using a wifi adapter but I have no problems with connection on any other game just this one. Does anyone have any idea what could be the problem?

Overwatch does require more than 60 packets per second, which is more than most games available today. Unfortunately, without looking at a WinMTR, we’re just guessing. Please add one here if you’d like to troubleshoot :slight_smile:

Click here to show/hide WinMTR instructions

Players in the Americas and Oceania regions: Follow the Blizzard support documentation for WinMTR.

  • Make sure your issue is caught in the test or you run it for at least 5 minutes.
  • Players on EU servers: please follow the same directions, except you’ll want to post results in the EU Tech Support forum.

Share your results in a reply:

  1. Click the “Copy Text to clipboard” button after you’ve finished the test.
  2. Paste the text in a reply, highlight it, then click </> on the post editor.
  3. If you can’t post links, add spaces before .com/.net/.us/.au, etc., which will break the link and allow you to post.

Please do not remove full hostnames from the test instead of “breaking the links” with spaces, as this makes troubleshooting much more difficult.

Here is the WinMTR, I think this is correct? I have never used this before.

|------------------------------------------------------------------------------------------|
| WinMTR statistics |

Host - % Sent Recv Best Avrg Wrst Last
192.168.0.1 - 93 14 1 7 7 7 7
No response from host - 100 13 0 0 0 0 0
aztw-core-2b-xe-723-0.network.virginmedia .net - 0 67 67 11 17 46 16
No response from host - 100 13 0 0 0 0 0
No response from host - 100 13 0 0 0 0 0
m686-mp2.cvx1-b.lis.dial.ntli .net - 0 67 67 16 21 43 17
213.46.175.254 - 2 64 63 17 26 82 62
ae1-br01-eqld5.as57976 .net - 2 64 63 25 33 80 29
et-0-0-2-br02-eqam1.as57976 .net - 0 67 67 24 33 98 29
137.221.78.83 - 2 64 63 24 39 99 29
185.60.112.157 - 0 67 67 23 29 54 23
________________________________________________ ______ ______ ______ ______ ______ ______

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

This connection test looks okay, but it uses way less packets per second than the actual game being played would use. I noticed that you’re using Virgin Media, is this their mobile broadband or their landline fiber optic?

It is the landline fiber optic.

Hey, Tarantino! Could you run a longer WinMTR test? This one seems to only have been ran for about a minute. While in-game let this run for 10-15 minutes while the latency issue occurs.

Here is the extended test, I couldn’t make it go any longer as it made me disconnect to the menu, my ping went up to 1000ms very very quickly and I couldn’t move I was stuck to the wall. Hopefully this test helps. Thank you for your help and fast replies also.

|------------------------------------------------------------------------------------------|
| WinMTR statistics |

Host - % Sent Recv Best Avrg Wrst Last
192.168.0.1 - 96 41 2 11 1292 2574 2574
No response from host - 100 39 0 0 0 0 0
aztw-core-2b-xe-723-0.network.virginmedia .net - 5 167 159 10 29 459 21
No response from host - 100 39 0 0 0 0 0
No response from host - 100 39 0 0 0 0 0
m686-mp2.cvx1-b.lis.dial.ntli .net - 5 167 159 15 33 387 26
213.46.175.254 - 5 169 162 17 55 3402 18
ae1-br01-eqld5.as57976 .net - 8 139 128 24 282 4620 28
et-0-0-2-br02-eqam1.as57976 .net - 29 91 65 24 157 3480 30
137.221.78.83 - 5 167 159 22 42 398 40
185.60.112.157 - 5 167 159 23 39 393 39
________________________________________________ ______ ______ ______ ______ ______ ______

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

Tarantino,

For some reason, your router is blocking most of your data packets, which is making this extremely difficult to read. I can tell there is a problem somewhere relatively nearby you (probably outside of our control) but I can’t pinpoint where just yet. Let’s try a couple of things to see if we can stabilize it, then re test with the winMTR if it doesn’t help.

  1. Power cycle your router and reset your PC. This’ll clear your network caches, which may be causing the weird packet behavior.
  2. Update your network card drivers and Windows. Old drivers may handle the connection instructions incorrectly.
  3. If you’re on wifi, swap to an ethernet cable. This is probably going to be the fix if the other two things don’t work, as long as it isn’t an ISP issue.

If none of that works, try running the winMTR one more time, just like you ran it last time. Make sure to catch some lag and ensure that you’re doing it via ethernet cable so we can rule out the odd instability at your router.