I randomly now have high ping

I was playing overwatch yesterday (05/11/2019) and I played 2 games, everything was great. I get into my third game and things look kinda weird, delayed hit markers, shots going through players, etc. My ping was 80 and a steady 80, I restarted my router and still have a steady 80 ping the next day. I was reading a thread from 02/16/2019 about the same thing happening. It was an overwatch issue, not a player issue. I was wondering if anyone was experiencing the same problems?

Hey Brincz,

I haven’t seen any recent reports of higher than normal latency yesterday or today. It looks like you are using AT&T as your internet provider, so we will keep an eye out for anyone else reporting a similar increase.

  • Can you let us know which server and IP you are connecting to? When you get into a match press Ctrl+Shift+N to open the network graph and the server name will be shown in [] brackets

  • Run a traceroute test to the IP address shown for the server and post that so we can take a look.

1 Like

Sorry if I misspoke, by ping I mean my network latency is showing as 80, I assumed that is my ping.

Tracing route to 24.105.46.142 over a maximum of 30 hops

1 2 ms 11 ms 8 ms 10.0.0.1
2 14 ms 9 ms 9 ms dsldevice attlocal net [192.168.1.254]
3 31 ms 35 ms 29 ms 99-185-72-1lightspeed clmasc sbcglobal net [99.185.72.1]
4 27 ms 39 ms 31 ms 99.175.12.13
5 34 ms 39 ms 38 ms 12.240.209.66
6 30 ms 31 ms 39 ms 12.123.43.197
7 30 ms 34 ms 39 ms 12.247.68.74
8 56 ms 59 ms 59 ms ae1-br01-eqat2 as57976 net [137.221.75.33]
9 56 ms 59 ms 69 ms et-0-0-4-br02-eqch2 as57976 net [137.221.65.46]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Thank for the quick reply

Thanks for the traceroute. Things look fine with it from what I can tell. The last hop (#9) we can see it ends up around 60ms or so, and that appears to be correct for the path your connection is taking through the AT&T network to reach our network.

One thing to keep in mind is that your latency in-game is going to show anywhere from 10-20ms higher than what you seen on connection tests like traceroute. The reason for that was posted here.

Unfortunately we can’t see what your ping might have been several days ago, but it is possible that something changed in the routing that has caused you to get higher ping than what you’re used to.

If the rubberbanding and hit marker/shot issue continues then you may want to run a more detailed connection test like WinMTR
This will help monitor the connection for any packet loss or high latency spikes while playing, and then depending on what is happening we may need to have you reach out to your internet provider. As far as our servers and network go, that all appears to be stable at the moment.

Hopefully this info helps!

1 Like

Ok thank you, appreciate the help and quick responses.

I think what it is, you guys saw me get 50% accuracy on hanzo 2 games in a row and had to nerf me, I understand.


Test 1

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

| WinMTR statistics |

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

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

| 10.0.0.1 - 0 | 381 | 381 | 0 | 2 | 11 | 2 |

| dsldevice attlocal net - 0 | 381 | 381 | 1 | 4 | 17 | 2 |

|99-185-72-1 lightspeed clmasc sbcglobal net - 0 | 381 | 381 | 21 | 26 | 304 | 22 |

| 99.175.12.13 - 0 | 381 | 381 | 20 | 29 | 881 | 23 |

| 12.240.209.66 - 0 | 381 | 381 | 26 | 32 | 47 | 28 |

| 12.123.43.197 - 0 | 381 | 381 | 25 | 27 | 35 | 30 |

| 12.247.68.74 - 0 | 381 | 381 | 25 | 29 | 65 | 27 |

| ae1-br01-eqat2 as57976 net - 0 | 381 | 381 | 46 | 53 | 182 | 51 |

| et-0-0-4-br02-eqch2 as57976 net - 0 | 381 | 381 | 47 | 59 | 218 | 52 |

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Test 2

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

| WinMTR statistics |

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

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

| 10.0.0.1 - 0 | 420 | 420 | 0 | 2 | 9 | 3 |

| dsldevice attlocal net - 0 | 420 | 420 | 1 | 4 | 12 | 3 |

|99-185-72-1 lightspeed clmasc sbcglobal net - 0 | 420 | 420 | 20 | 25 | 49 | 24 |

| 99.175.12.13 - 0 | 420 | 420 | 20 | 23 | 37 | 22 |

| 12.240.209.66 - 0 | 420 | 420 | 25 | 32 | 45 | 31 |

| 12.123.43.197 - 0 | 420 | 420 | 25 | 29 | 40 | 27 |

| 12.247.68.74 - 0 | 420 | 420 | 25 | 30 | 77 | 30 |

| ae1-br01-eqat2 as57976 net - 0 | 420 | 420 | 45 | 53 | 209 | 54 |

| et-0-0-4-br02-eqch2 as57976 net - 1 | 409 | 408 | 47 | 90 | 4838 | 59 |

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

No errors on WinMTR or noticeable ping spikes in game

no reply as expected

1 Like

What? //Need More Letters

Thanks for the WinMTRs Brincz!

The results look pretty good actually. The 1 packet dropped and 4838ms spike on et-0-0-4-br02-eqch2 as57976 net is normal, since those routers de-prioritize the test packets.

How did the games feel when these tests were running? Did you see any network icons show up on the left side or feel any stuttering/rubberbanding?

From what the tests are showing your connection should be working fine and performing normally. Let us know if you run into any other issues.

13 posts were split to a new topic: South Australian latency increase

I want to say that I have been having the same issue, starting today. My ISP is Cox Communications.

My ping will jump between 40 something to over 500 and fluctuate in between and was dropped from a game entirely. I have never had this issue with Overwatch and all other apps run normally. I am not showing packet loss to other servers.