Very fast WiFi, but high ping in Overwatch

My wifi is pretty fast getting up to 230 mbs download speeds. However, my ping in Overwatch is very high, hovering around 90-110ms consistently. This causes me to “double shoot” and when using my abilities they sometimes don’t register. I’ve tried many troubleshooting methods like resetting and flushing my ip, but nothing seems to help. I have my Blizzard Looking Glass stats:

TRACEROUTE:
traceroute to 96.18.175.23 (96.18.175.23), 15 hops max, 60 byte packets
1 Blizzard Blizzard 3.068 ms 3.017 ms 3.013 ms
2 24.105.18.131 (24.105.18.131) 10.861 ms 10.846 ms 10.846 ms
3 137.221.105.16 (137.221.105.16) 10.802 ms 10.816 ms 10.818 ms
4 137.221.66.18 (137.221.66.18) 10.832 ms 10.833 ms 10.834 ms
5 137.221.83.90 (137.221.83.90) 28.539 ms 28.551 ms 28.539 ms
6 137.221.65.66 (137.221.65.66) 28.379 ms 26.831 ms 26.811 ms
7 137.221.74.34 (137.221.74.34) 26.683 ms 27.266 ms 27.320 ms
8 67-60-74-29.cpe.sparklight. net (67.60.74.29) 26.562 ms 25.596 ms 25.636 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *

05/04/2020 06:40:03 UTC

TRACEROUTE:
traceroute to 96.18.175.23 (96.18.175.23), 15 hops max, 60 byte packets
1 Blizzard Blizzard 2.407 ms 2.395 ms 2.403 ms
2 24.105.18.131 (24.105.18.131) 3.484 ms 3.497 ms 3.540 ms
3 137.221.105.16 (137.221.105.16) 3.565 ms 3.576 ms 3.586 ms
4 137.221.66.18 (137.221.66.18) 3.650 ms 3.663 ms 3.687 ms
5 137.221.83.90 (137.221.83.90) 28.174 ms 28.181 ms 28.191 ms
6 137.221.65.66 (137.221.65.66) 27.783 ms 26.785 ms 26.749 ms
7 137.221.74.34 (137.221.74.34) 27.190 ms 25.951 ms 26.317 ms
8 67-60-74-29.cpe.sparklight. net (67.60.74.29) 25.621 ms 25.408 ms 25.510 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *

05/04/2020 06:40:03 UTC

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

— 96.18.175.23 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2998ms

05/04/2020 06:40:03 UTC

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

— 96.18.175.23 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2998ms

05/04/2020 06:40:03 UTC

MTR:
Start: Sun Apr 5 06:40:03 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.4 0.3 0.5 0.0
2.|-- 24.105.18.131 0.0% 10 0.7 0.8 0.6 1.6 0.0
3.|-- 137.221.105.16 0.0% 10 0.8 1.0 0.7 1.2 0.0
4.|-- 137.221.66.18 0.0% 10 0.5 0.6 0.4 0.8 0.0
5.|-- 137.221.83.90 0.0% 10 25.8 25.8 25.6 26.1 0.0
6.|-- 137.221.65.66 0.0% 10 25.7 26.2 25.5 30.1 1.2
7.|-- 137.221.74.34 0.0% 10 25.8 30.9 25.8 66.6 12.8
8.|-- 67-60-74-29.cpe.sparklight. net 0.0% 10 25.9 25.7 25.4 26.0 0.0
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

05/04/2020 06:40:03 UTC

MTR:
Start: Sun Apr 5 06:40:03 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.3 0.5 0.0
2.|-- 24.105.18.131 0.0% 10 0.5 0.6 0.5 0.9 0.0
3.|-- 137.221.105.16 0.0% 10 0.9 1.0 0.6 3.0 0.7
4.|-- 137.221.66.18 0.0% 10 0.7 2.6 0.4 20.8 6.4
5.|-- 137.221.83.90 0.0% 10 25.6 26.0 25.6 27.8 0.5
6.|-- 137.221.65.66 0.0% 10 25.6 27.4 25.5 43.3 5.6
7.|-- 137.221.74.34 0.0% 10 29.1 27.3 25.8 36.7 3.4
8.|-- 67-60-74-29.cpe.sparklight. net 0.0% 10 25.6 26.5 25.4 35.7 3.2
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

05/04/2020 06:40:03 UTC

Here is the winMTR Test Results as well:

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

Host - % Sent Recv Best Avrg Wrst Last
192.168.86.1 - 0 410 410 0 0 0 0
192.168.0.1 - 0 410 410 0 25 359 10
10.113.243.1 - 0 410 410 7 42 377 19
192.168.69.221 - 0 410 410 7 41 372 20
10.224.253.133 - 0 410 410 8 43 373 12
lag-101.ear4.Seattle1.Level3. net - 54 131 61 0 100 1525 77
No response from host - 100 82 0 0 0 0 0
4.7.26.166 - 0 410 410 41 82 403 46
ae1-br01-csla1.as57976. net - 0 410 410 71 116 444 74
xe-0-0-1-3-br01-eqla1.as57976. net - 0 410 410 70 121 432 82
et-0-0-2-br01-swlv10.as57976. net - 0 410 410 71 118 438 77
137.221.65.133 - 0 410 410 71 123 470 80
et-0-0-0-pe02-eqch2.as57976. net - 0 410 410 65 111 448 66
No response from host - 100 82 0 0 0 0 0
No response from host - 100 82 0 0 0 0 0
No response from host - 100 82 0 0 0 0 0
No response from host - 100 82 0 0 0 0 0
No response from host - 100 82 0 0 0 0 0
No response from host - 100 82 0 0 0 0 0
No response from host - 100 82 0 0 0 0 0
No response from host - 100 82 0 0 0 0 0
No response from host - 100 82 0 0 0 0 0
No response from host - 100 82 0 0 0 0 0
No response from host - 100 82 0 0 0 0 0
No response from host - 100 82 0 0 0 0 0
No response from host - 100 82 0 0 0 0 0
No response from host - 100 82 0 0 0 0 0
No response from host - 100 82 0 0 0 0 0
No response from host - 100 82 0 0 0 0 0
No response from host - 100 82 0 0 0 0 0
________________________________________________ ______ ______ ______ ______ ______ ______

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

If anyone could help me it would be greatly appreciated.
Thank you!

Hey Austiin, I had similar issues with latency last week and my winMTR looked quite a bit like yours. The issue starts here:

The IP address 192.168.0.1 (which I believe to be your router/modem) seems to occasionally jump up to a response time of 359ms, which is not terribly fast.

This could be a hardware issue or even software related, as it was in my case.

Here is the link to my topic with the fix that worked for me. Even if it doesn’t work for you, there’s a few informative posts there from more knowledgeable people than myself.

I hope you are well.

Edit: Grammar & referenced incorrect IP, fixed

1 Like

These are all local network addresses, meaning they are in your home or building, and all of them are showing very high ping of 359-373ms. It could be that the network is overtaxed due to everyone being home, or that parts of the equipment are flooded or failing. Depending on how much control you have over these nodes in your network, you may need to consult either your building or ISP about repairs. Until the local networking issue is resolved, you’ll continue to experience the high ping.

You may also notice high ping on the Level3 node after your network, but you can ignore this because the ping returns to “normal” (as it can be with the home network lag) after that hop.

1 Like

Thank you very much Arbiter and Nicole for your responses.

So I’m not very savvy in this field and due to that I’m confused on what approach to take. To add, I just recently replaced my router to a Google Wifi kit (This lag issue in the game was still present before the new router). So I’m not sure whether it’s a hardware issue with my modem or an issue with my ISP. If it is an issue with my provider, how would I ask them about the problem?

Thanks again!

It looks like the device you’re directly connected to is working okay, but the nodes right after that are where the problem exists. I can’t see your physical network configuration and don’t know who is responsible for each node, so I think it would be best to forward the test, and you can include my findings, to your your ISP.

Thank you Nicole again for your response.

Is there a way I can provide you my configuration or any other information that could be helpful to you? I plan to contact my ISP tomorrow to address the issue which would specifically be latency problems right?

Much appreciated!

The WinMTR gave us the digital addresses for each piece of hardware, but I’m talking about physically looking at the setup. This would either be something the ISP has in their records, or something they’d send a technician to look at. Even if you could tell me which equipment was assigned to the addresses mentioned above, other than recommending you reboot all of them, there’s not much else I can do over the forum.

You’ll want to mention you have a very high ping over 300ms when connecting to games.

In the meantime, you might look at your ISP’s forums (if they have them), their tweets/replies, or people talking to them on Twitter. Sometimes this can clue you in on what’s happening for them around your city.

Hey all,

I wanted to clarify a little known fact about those IP addresses you’re seeing here. Some ISPs lately will actually use these reserved IP addresses for hardware they own - especially smaller ones. Just for the sake of making the interaction with the ISP smooth, they may note that the problems are in their network rather than in your building. (It’s very uncommon for you to have 5 routing devices in one building unless something very janky is going on configuration wise)

Regardless, the troubleshooting given here is good - I’d still reach out to the ISP to see if they’re aware of any network capacity issues. They’re quite common with everybody hanging out at home due to quarantine. If there aren’t any known issues, you may need to swap out some devices (such as your modem/router) with the ISP to see if it fixes things.