Severe ping increase. Please help

Hello. As of Friday my ping to 85-90 ms consistently and I cannot play the game. I also cannot identify why this all of the sudden has happened. It’s never that high. When people die there are no animations. Tracers recall she just disappears with no animations. Something is going on and I hope someone can Identify it. Here are my Winmtr results below.

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

|                                      WinMTR statistics                                   |

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

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

|                  dsldeviceattlocalnet -    0 |  982 |  982 |    0 |    0 |    2 |    0 |

|107-130-196-1lightspeedrcsntxsbcglobalnet -    0 |  982 |  982 |   19 |   21 |   42 |   19 |

|                           71.155.29.200 -    0 |  982 |  982 |   20 |   56 |  634 |   21 |

|                          12.123.235.150 -    0 |  982 |  982 |   22 |   26 |   33 |   29 |

|                  dlstx409me9ipattnet -    0 |  982 |  982 |   21 |   22 |   33 |   22 |

|                           12.244.90.238 -    0 |  982 |  982 |   22 |   25 |   90 |   27 |

|              ae1-br01-eqda6as57976net -    0 |  982 |  982 |   42 |   47 |  154 |   67 |

|         et-0-0-4-br01-eqch2.as57976net -    0 |  982 |  982 |   42 |   52 |  246 |   45 |

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Hey there Saibot!

Thanks for reaching out with that WinMTR test data. Reviewing the test, there are significant latency spikes occurring on the third “hop” as shown below:

| 71.155.29.200 - 0 | 982 | 982 | 20 | 56 | 634 | 21 |

However, it’s hard to say with certainty whether this is the cause of your issue because these latency spikes do not persist through the succeeding hops. Does the issue resolve when testing an alternate network?

If you’re not having any issues when using an alternate network, this would indicate that the underlying problem is isolated to your home network or ISP.

I hope this helps!

Hello,

Thank you for the reply. So I called my ISP for assistance with this and it seems I cannot convey to them correctly what my issue is. They sent out a technician and stated they found nothing wrong with the line and everything looked fine.

I insisted that I was having bad latency while playing games online. They also insisted that after testing all my lines that nothing was wrong. I don’t know where to go from here but I’m afraid I won’t be able to play overwatch anymore due to this problem.

Heya Saibot,

When speaking with the ISP, please be sure to ask for an escalation to a Tier 2 or higher agent who understands what routing is. If they sent a guy to your house then they were looking in the wrong location!

This first one here is your router/modem. We did not find any problems related to the connection between the PC and the modem, so it makes sense they found no issues here.

This second hop here is the connection from your modem to a node hosted by your local ISP. We did see a small increase in latency but that’s somewhat expected depending on the distance between your home and this node. Keep in mind that these are often many miles away and are often not even located in the same city! Though I cannot specify for certain, only your ISP would know where that node is physically located.

Once we get to hop 3 is when we start to see the latency go into the 100+ region for the “Worst” connection times. This is the connection between the second hop I mentioned which is controlled by the ISP, and another one of their servers. Both hop 2 and hop 3 are owned by ATT.

I do sincerely hope the information helps explain more of what’s going on. Let us know if you have any further questions!

Yes this makes perfect sense. We have isolated the issue to a servers IP address that is controlled by my ISP. Funny enough I called them and tried to report that I was having severe latency issues that may be caused by this location and they said “sir you are asking me to check a node that is outside of your home location.” I cannot do that"…This was a technical supervisor that I spoke with.

I know you can’t help me untangle the horrendous customer service my IP provides but I do thank you for giving me some clues as to what the issue is.

I’m probably going to try a VPN to see if I can bypass this particular router that’s giving me trouble.

THANK YOU.

Saibot,

A VPN can often work around an ISP issue and confirm more information for the ISP. That all said, we could try investigating the other side of the connection path since we’re at this anyway. Mind running a looking glass when you’re having issues and posting the results here?

Hey Drak,

Sure thing. Luckily the issue is consistent so it’s not an intermittent issue. Those are a PAIN. Anyway. Here is my looking glass results.


My latency in game right now is still in the mid 80's. I am currently in north Texas right now.

TRACEROUTE:
traceroute to 99.70.90.52 (99.70.90.52), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  7.670 ms  7.661 ms  7.666 ms
 2  24.105.18.131 (24.105.18.131)  11.201 ms  11.211 ms  11.259 ms
 3  137.221.105.12 (137.221.105.12)  11.433 ms  11.463 ms  11.481 ms
 4  137.221.66.16 (137.221.66.16)  11.345 ms  11.353 ms  11.371 ms
 5  137.221.83.80 (137.221.83.80)  73.048 ms  73.112 ms  73.122 ms
 6  137.221.65.68 (137.221.65.68)  15.190 ms  21.280 ms  21.246 ms
 7  137.221.68.32 (137.221.68.32)  75.154 ms  73.455 ms  73.425 ms
 8  12.245.64.9 (12.245.64.9)  6.988 ms  7.114 ms  7.136 ms
 9  * * *
10  * * *
11  * * *
12  71.155.70.251 (71.155.70.251)  31.482 ms  31.402 ms  31.659 ms
13  * * *
14  * * *
15  * * *


07/03/2020 21:29:07 UTC
--------------------

TRACEROUTE:
traceroute to 99.70.90.52 (99.70.90.52), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  1.485 ms  1.480 ms  1.485 ms
 2  24.105.18.131 (24.105.18.131)  1.339 ms  1.369 ms  4.994 ms
 3  137.221.105.12 (137.221.105.12)  5.206 ms  5.258 ms  5.264 ms
 4  137.221.66.16 (137.221.66.16)  5.146 ms  5.162 ms  5.168 ms
 5  137.221.83.80 (137.221.83.80)  8.927 ms  8.974 ms  9.000 ms
 6  137.221.65.68 (137.221.65.68)  9.005 ms  9.395 ms  9.387 ms
 7  137.221.68.32 (137.221.68.32)  75.264 ms  75.271 ms  72.988 ms
 8  12.245.64.9 (12.245.64.9)  6.465 ms  6.719 ms  6.745 ms
 9  * * *
10  * * *
11  * * *
12  71.155.70.251 (71.155.70.251)  31.241 ms  31.180 ms  31.179 ms
13  * * *
14  * * *
15  * * *


07/03/2020 21:29:07 UTC
--------------------

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

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



07/03/2020 21:29:07 UTC
--------------------

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

--- 99.70.90.52 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3006ms



07/03/2020 21:29:07 UTC
--------------------

MTR:
Start: Sat Mar  7 21:29:07 2020 Blizzard  1.|-- Blizzard    0.0%    10    0.3   1.1   0.3   7.1   2.0
  2.|-- 24.105.18.131    0.0%    10    0.5   3.2   0.5  13.8   4.4
  3.|-- 137.221.105.12   0.0%    10    1.1   0.9   0.8   1.1   0.0
  4.|-- 137.221.66.16    0.0%    10    0.6   0.6   0.4   1.0   0.0
  5.|-- 137.221.83.80    0.0%    10    5.8   5.9   5.7   6.0   0.0
  6.|-- 137.221.65.68    0.0%    10    5.8  10.9   5.8  52.5  14.6
  7.|-- 137.221.68.32    0.0%    10    6.3   8.0   5.9  23.9   5.6
  8.|-- 12.245.64.9      0.0%    10    5.9   6.2   5.8   8.3   0.6
  9.|-- ???             100.0    10    0.0   0.0   0.0   0.0   0.0
 10.|-- ???             100.0    10    0.0   0.0   0.0   0.0   0.0
 11.|-- ???             100.0    10    0.0   0.0   0.0   0.0   0.0
 12.|-- 71.155.70.251    0.0%    10   31.4  31.5  31.3  31.7   0.0
 13.|-- ???             100.0    10    0.0   0.0   0.0   0.0   0.0


07/03/2020 21:29:07 UTC
--------------------

MTR:
Start: Sat Mar  7 21:29:07 2020 Blizzard  1.|-- Blizzard    0.0%    10    0.3   0.5   0.3   1.6   0.0
  2.|-- 24.105.18.131    0.0%    10    0.6   0.6   0.5   0.7   0.0
  3.|-- 137.221.105.12   0.0%    10    1.0   1.0   0.7   1.5   0.0
  4.|-- 137.221.66.16    0.0%    10    0.7  11.9   0.3 113.3  35.6
  5.|-- 137.221.83.80    0.0%    10    6.3   6.0   5.8   6.3   0.0
  6.|-- 137.221.65.68    0.0%    10    5.8  12.8   5.7  62.2  17.8
  7.|-- 137.221.68.32    0.0%    10    6.0  13.9   5.9  56.1  16.8
  8.|-- 12.245.64.9      0.0%    10    5.9   5.8   5.7   5.9   0.0
  9.|-- ???             100.0    10    0.0   0.0   0.0   0.0   0.0
 10.|-- ???             100.0    10    0.0   0.0   0.0   0.0   0.0
 11.|-- ???             100.0    10    0.0   0.0   0.0   0.0   0.0
 12.|-- 71.155.70.251    0.0%    10   31.5  31.4  31.3  31.6   0.0
 13.|-- ???             100.0    10    0.0   0.0   0.0   0.0   0.0


07/03/2020 21:29:07 UTC
--------------------

This ALSO looks fine. Interesting. Can you get a screenshot of your netgraph (Ctrl+Shift+N in game) for me and upload it somewhere like imgur, then link it here? None of these tests are adding up right now.

That’s interesting cause I too am having higher than usual ping and I’m in Houston Texas. Have you noticed any issues with spamming a voiceline and only hearing it once? My ping used to be 40-45ms and now its 62-72ms

HI HoHoHo,

Yes absolutely. My voice lines aren’t working either. As well as tracer recall animations…hit box pings etc…

sounds like we’re in the same boat, guessing the cause of it is due to our pings. I posted my MTR here

TRACEROUTE:
traceroute to 204.60.26.246 (204.60.26.246), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  4.640 ms  7.547 ms  7.566 ms
 2  24.105.18.3 (24.105.18.3)  7.569 ms  7.570 ms  7.571 ms
 3  137.221.105.12 (137.221.105.12)  5.429 ms  5.433 ms  5.434 ms
 4  137.221.66.20 (137.221.66.20)  5.334 ms  5.346 ms  5.349 ms
 5  137.221.83.84 (137.221.83.84)  43.399 ms  43.408 ms  43.416 ms
 6  137.221.65.68 (137.221.65.68)  11.683 ms  9.021 ms  9.030 ms
 7  137.221.68.32 (137.221.68.32)  9.086 ms  9.089 ms  9.092 ms
 8  12.245.64.9 (12.245.64.9)  9.009 ms  9.014 ms  9.011 ms
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  71.149.39.95 (71.149.39.95)  35.791 ms  34.793 ms  34.961 ms
15  * * *


08/03/2020 08:39:07 UTC
--------------------

TRACEROUTE:
traceroute to 204.60.26.246 (204.60.26.246), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  0.935 ms  0.938 ms  0.945 ms
 2  24.105.18.3 (24.105.18.3)  2.098 ms  2.121 ms  2.127 ms
 3  137.221.105.12 (137.221.105.12)  4.407 ms  4.415 ms  4.422 ms
 4  137.221.66.20 (137.221.66.20)  4.320 ms  4.355 ms  4.368 ms
 5  137.221.83.84 (137.221.83.84)  40.103 ms  40.142 ms  40.153 ms
 6  137.221.65.68 (137.221.65.68)  6.721 ms  6.248 ms  10.862 ms
 7  137.221.68.32 (137.221.68.32)  6.298 ms  6.041 ms  6.563 ms
 8  12.245.64.9 (12.245.64.9)  6.113 ms  6.137 ms  6.278 ms
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  71.149.39.95 (71.149.39.95)  36.093 ms  34.774 ms  34.965 ms
15  * * *


08/03/2020 08:39:07 UTC
--------------------

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

--- 204.60.26.246 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3002ms



08/03/2020 08:39:07 UTC
--------------------

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

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



08/03/2020 08:39:07 UTC
--------------------

MTR:
Start: Sun Mar  8 08:39:07 2020 Blizzard  1.|-- Blizzard     0.0%    10    0.5   0.7   0.3   2.1   0.3
  2.|-- 24.105.18.3      0.0%    10    0.9   1.0   0.6   2.4   0.3
  3.|-- 137.221.105.12   0.0%    10    0.7   1.4   0.7   5.5   1.3
  4.|-- 137.221.66.20    0.0%    10    0.6   8.4   0.4  41.4  16.6
  5.|-- 137.221.83.84    0.0%    10  155.3 101.0   8.4 185.7  48.9
  6.|-- 137.221.65.68    0.0%    10    6.0   9.2   5.7  37.6   9.9
  7.|-- 137.221.68.32    0.0%    10    6.1   9.7   6.0  40.8  10.9
  8.|-- 12.245.64.9      0.0%    10    5.9   6.0   5.9   6.3   0.0
  9.|-- ???             100.0    10    0.0   0.0   0.0   0.0   0.0
 10.|-- ???             100.0    10    0.0   0.0   0.0   0.0   0.0
 11.|-- ???             100.0    10    0.0   0.0   0.0   0.0   0.0
 12.|-- ???             100.0    10    0.0   0.0   0.0   0.0   0.0
 13.|-- 12.122.147.77   70.0%    10   33.8  33.9  33.8  34.0   0.0
 14.|-- 71.149.39.95     0.0%    10   35.0  35.0  34.7  35.2   0.0
 15.|-- ???             100.0    10    0.0   0.0   0.0   0.0   0.0


08/03/2020 08:39:07 UTC
--------------------

MTR:
Start: Sun Mar  8 08:39:07 2020 Blizzard  1.|-- Blizzard     0.0%    10    0.4   0.6   0.3   1.8   0.3
  2.|-- 24.105.18.3      0.0%    10    1.0   1.4   0.5   6.2   1.6
  3.|-- 137.221.105.12   0.0%    10    0.7   1.4   0.7   5.7   1.4
  4.|-- 137.221.66.20    0.0%    10    0.6   8.3   0.4  40.2  16.3
  5.|-- 137.221.83.84    0.0%    10  155.1 130.8   8.6 406.0 108.1
  6.|-- 137.221.65.68    0.0%    10    6.0   9.1   5.7  37.6  10.0
  7.|-- 137.221.68.32    0.0%    10    6.1   9.6   5.9  40.7  10.9
  8.|-- 12.245.64.9      0.0%    10    6.2   6.0   5.9   6.2   0.0
  9.|-- ???             100.0    10    0.0   0.0   0.0   0.0   0.0
 10.|-- ???             100.0    10    0.0   0.0   0.0   0.0   0.0
 11.|-- ???             100.0    10    0.0   0.0   0.0   0.0   0.0
 12.|-- ???             100.0    10    0.0   0.0   0.0   0.0   0.0
 13.|-- 12.122.147.77   80.0%    10   34.3  34.1  33.9  34.3   0.0
 14.|-- 71.149.39.95     0.0%    10   34.9  35.0  34.7  35.2   0.0
 15.|-- ???             100.0    10    0.0   0.0   0.0   0.0   0.0


08/03/2020 08:39:07 UTC
--------------------

Yep! I even remember the exact time and date it started happening. It was Feb 28th around 9:00pm. I always check my latency when I enter into a comp game and I was like oh wait what? lol…

The game prior to that it was no more than 50-55

Drak,

Here is the information you requested.
imgurcom/a/laumHAv

Interestingly enough my latency is the exact same whether I am connected to LAX1 or ord1. Which is never the case. I’m usually in the mid 70s on LAX1 and 50-55 on ord1. :>

Also, I tried using a VPN but it didn’t work. Just thought I’d mention that.

Saibot,

Looks like that was taken in the practice range, which is a bit screwy on its own and doesn’t necessarily demonstrate issues you’d have in actual matches. That said, the biggest thing I’m seeing in this test is the stepping up/down PNG line. That could indicate something odd going on with quality of service settings on a router or your PC. If you have a network card with Quality of Service settings built in to it, you can disable that. Primarily this is a problem on gaming oriented network cards, like Killer. They have an “Advanced Stream Detect” setting that can mess with packet priorities.

Otherwise, we could test to see if the behavior you’re having problems with is worse if we totally remove your router from the equation. USUALLY your phone is going to be a worse question, but if you hook up via a USB or mobile tether, do the voice lines all come back and the shots hit correctly again? If so, that near certainly puts the issue squarely on the router/modem. Likely in that case you’re looking at quality of service on the modem/router, or some other issue with it that’s undetectable by connection tests.

Hey Sailbot, I did this and it dropped my ping back down to 40-45ms

I turned mine off as it was on and I can hear my voicelines now.

• Now, let’s also check on the Limit Client/server send data rates. To do this open up Overwatch and go to options. Once there you will go to Gameplay. Turn on or off the following:
- Limit Client Send Rate
- Limit Server Send Rate

Hey,

I’m glad you were able to fix your issue. So I tried to find the settings for QOS in both my modem and my network card however neither have anything labeled QOS that I could change. My network card is an Intel® 82579V. I did deselect QOS packet scheduler in the Ethernet properties however this didn’t change anything and I turned it on again.

I turned Limit client/server send data rates off in overwatch and it actually increased my ping by almost 15. Kind of weird but possibly a hint at the problem?

Also Drak,

So I connected using a tethering. And I literally got the same exact results as I did when I was on Ethernet. Here is the imgur link

imgurcom/a/CgrRAcm

Saibot,

Blah, it looks like your mobile connection just isn’t super stable in general. Your packet processing just flatlined for a sec there. We won’t be able to use that information to prove anything, but that is three totally different connection types we just tested. More on that in a sec, wanted to cover the other thing you mentioned about send/receive rates.

Limiting client/server send rate will usually change how the game registers your ping which results in higher numbers. The numbers don’t always correlate to behavior however. Did the gameplay “Feel” better despite that increase, or was it about the same or worse? Were the animations better, etc?

Based on the fact that we’re looking at three entirely different connection paths having issues, we may want to get you live with or customer support squad to do more troubleshooting. It’s possible something odd is going on with your drivers and we’d need something like an msinfo to see more than what we’ve already tried here. We try not to collect MSinfos over the forums for privacy reasons.

You’ll probably want to list to them in your ticket what you’ve already done and link this thread so they can read over what you’ve already tried so we don’t double up on things.

Hi Drak!

Thank you for your assistance in this. As of 03/13/2020 everything has returned to normal. I didn’t change any settings or do anything it just kind of fixed itself. I was hoping to add some kind of fix here for people in the future however I didn’t do anything in this case.

I guess sometimes just waiting it out is the only “fix”. Anyway thank you again!!

Saibot,

Thanks for the update nonetheless. If it comes back, please ping us. In some cases, we find that issues like this may come and go during peak usage hours, so if it returns, it’ll be important to note exactly when it starts back up.

Good luck anyway! :smiley: