Lag spikes while playing Overwatch

Technical Support
1

Hello I have what I would consider higher ping in game, on average 75 ms. However I get pretty consistent lag spikes to upwards of 105 ms. Running a test on FAST shows me as having 500 down, 55 up. Latency Unloaded 38, loaded 42 ( I don’t know what this means ).

I found a list of things to try including check if drivers are up to date, use googles DNS, reset winsock data, flush dns and release and renew ip. Last thing that was suggested was to use Blizzards looking glass tool and I was hoping someone could help me interperit this because I don’t understand what I’m looking at. Thanks in advance.

Modem: Netgear cm1000v2
Router: Linksys WRT 32x

TRACEROUTE:
traceroute to 73.59.206.130 (73.59.206.130), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.401 ms 0.365 ms 0.358 ms
2 24.105.18.130 (24.105.18.130) 0.638 ms 0.679 ms 0.788 ms
3 137.221.105.14 (137.221.105.14) 0.933 ms 0.954 ms 0.938 ms
4 137.221.66.18 (137.221.66.18) 1.123 ms 1.126 ms 1.124 ms
5 137.221.83.82 (137.221.83.82) 50.524 ms 269.794 ms 269.836 ms
6 * * *
7 137.221.68.32 (137.221.68.32) 7.540 ms 6.004 ms 5.971 ms
8 be-102-pe12.600wseventh.ca.ibone.comcast .net (75.149.229.69) 6.369 ms 6.033 ms 6.014 ms
9 be-3112-cs01.losangeles.ca.ibone.comcast .net (96.110.33.65) 6.809 ms 7.005 ms 6.991 ms
10 be-1112-cr12.losangeles.ca.ibone.comcast .net (96.110.45.166) 6.576 ms 6.567 ms 6.423 ms
11 be-302-cr13.houston.tx.ibone.comcast .net (96.110.37.189) 33.297 ms 32.924 ms 32.986 ms
12 be-1313-cs03.houston.tx.ibone.comcast .net (96.110.46.137) 32.892 ms 32.932 ms 33.133 ms
13 be-1311-cr11.houston.tx.ibone.comcast .net (96.110.46.130) 32.202 ms 32.021 ms 32.009 ms
14 be-311-cr02.dallas.tx.ibone.comcast .net (96.110.36.170) 32.718 ms 33.276 ms 33.253 ms
15 be-7922-ar02.dannythomas.tn.malt.comcast .net (68.86.93.94) 41.062 ms 41.060 ms 41.052 ms

13/10/2021 13:58:04 UTC

TRACEROUTE:
traceroute to 73.59.206.130 (73.59.206.130), 15 hops max, 60 byte packets
1 Blizzard Blizzard 9.174 ms 9.162 ms 9.157 ms
2 37.244.23.3 (37.244.23.3) 9.772 ms 9.791 ms 9.794 ms
3 24.105.62.148 (24.105.62.148) 9.794 ms 9.795 ms 9.795 ms
4 137.221.66.8 (137.221.66.8) 9.122 ms 9.124 ms 9.126 ms
5 * * *
6 137.221.69.32 (137.221.69.32) 9.104 ms 2.788 ms 2.749 ms
7 be-128-pe11.350ecermak.il.ibone.comcast. net (75.149.230.45) 3.348 ms 3.448 ms 3.797 ms
8 be-2211-cs02.350ecermak.il.ibone.comcast. net (96.110.33.197) 2.634 ms 2.654 ms 9.633 ms
9 be-1211-cr11.350ecermak.il.ibone.comcast. net (96.110.35.6) 2.085 ms 2.092 ms 2.013 ms
10 be-301-cr11.1601milehigh.co.ibone.comcast. net (96.110.37.146) 29.997 ms 29.764 ms 29.748 ms
11 be-1111-cs01.1601milehigh.co.ibone.comcast. net (96.110.39.65) 30.473 ms 30.490 ms 30.490 ms
12 be-1112-cr12.1601milehigh.co.ibone.comcast. net (96.110.39.82) 30.195 ms 30.215 ms 30.262 ms
13 be-304-cr02.dallas.tx.ibone.comcast .net (96.110.38.110) 30.878 ms 30.894 ms 30.891 ms
14 be-7922-ar02.dannythomas.tn.malt.comcast. net (68.86.93.94) 38.529 ms 38.700 ms 38.517 ms
15 96.108.172.126 (96.108.172.126) 50.458 ms 50.423 ms 50.405 ms

13/10/2021 13:58:04 UTC

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

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

13/10/2021 13:58:04 UTC

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

— 73.59.206.130 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2999ms

13/10/2021 13:58:04 UTC

MTR:
Start: Wed Oct 13 13:58:04 2021 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.3 0.4 0.0
2.|-- 37.244.23.3 0.0% 10 0.6 0.5 0.4 0.7 0.0
3.|-- 24.105.62.148 0.0% 10 0.8 1.0 0.7 1.2 0.0
4.|-- 137.221.66.8 0.0% 10 1.4 4.5 1.1 32.8 9.9
5.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
6.|-- 137.221.69.32 0.0% 10 2.1 9.9 2.0 33.8 11.5
7.|-- be-128-pe11.350ecermak.il.ibone.comcast. net 0.0% 10 2.1 2.3 1.6 5.3 1.0
8.|-- be-2211-cs02.350ecermak.il.ibone.comcast. net 0.0% 10 2.5 2.7 2.3 3.0 0.0
9.|-- be-1211-cr11.350ecermak.il.ibone.comcast. net 80.0% 10 2.0 1.9 1.8 2.0 0.0
10.|-- be-301-cr11.1601milehigh.co.ibone.comcast. net 0.0% 10 29.9 29.7 29.5 30.0 0.0
11.|-- be-1111-cs01.1601milehigh.co.ibone.comcast. net 0.0% 10 30.2 30.5 30.2 30.8 0.0
12.|-- be-1112-cr12.1601milehigh.co.ibone.comcast. net 10.0% 10 30.5 30.0 29.7 30.5 0.0
13.|-- be-304-cr02.dallas.tx.ibone.comcast. net 0.0% 10 31.1 31.1 29.7 32.6 0.7
14.|-- be-7922-ar02.dannythomas.tn.malt.comcast. net 0.0% 10 38.4 38.6 38.4 39.0 0.0
15.|-- 96.108.172.126 0.0% 10 50.5 50.6 50.5 50.8 0.0
16.|-- 96.110.132.250 0.0% 10 50.7 50.7 50.6 50.9 0.0
17.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

13/10/2021 13:58:04 UTC

MTR:
Start: Wed Oct 13 13:58:04 2021 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.8 0.3 2.2 0.6
2.|-- 24.105.18.130 0.0% 10 18.6 5.4 0.5 21.5 8.1
3.|-- 137.221.105.14 0.0% 10 0.9 1.3 0.8 5.0 1.2
4.|-- 137.221.66.18 0.0% 10 0.4 6.4 0.4 57.1 17.8
5.|-- 137.221.83.82 0.0% 10 1492. 656.0 96.4 1492. 523.3
6.|-- 137.221.65.68 90.0% 10 15748 15748 15748 15748 0.0
7.|-- 137.221.68.32 0.0% 10 6.1 13.4 5.9 42.5 12.7
8.|-- be-102-pe12.600wseventh.ca.ibone.comcast(dot)net 0.0% 10 6.2 6.3 5.8 8.4 0.7
9.|-- be-3112-cs01.losangeles.ca.ibone.comcast(dot)net 0.0% 10 6.6 6.9 6.4 7.7 0.0
10.|-- be-1112-cr12.losangeles.ca.ibone.comcast(dot)net 0.0% 10 6.5 7.5 6.2 12.1 1.8
11.|-- be-302-cr13.houston.tx.ibone.comcast(dot)net 0.0% 10 32.9 33.5 32.4 36.4 1.1
12.|-- be-1313-cs03.houston.tx.ibone.comcast(dot)net 0.0% 10 32.8 33.2 32.7 34.0 0.0
13.|-- be-1311-cr11.houston.tx.ibone.comcast(dot)net 0.0% 10 32.4 32.5 32.1 33.5 0.3
14.|-- be-311-cr02.dallas.tx.ibone.comcast(dot)net 0.0% 10 33.7 34.0 32.6 35.9 0.9
15.|-- be-7922-ar02.dannythomas.tn.malt.comcast(dot)net 0.0% 10 40.9 42.0 40.9 45.4 1.3
16.|-- 96.108.172.126 0.0% 10 53.1 53.4 53.0 55.2 0.6
17.|-- 96.110.132.250 0.0% 10 53.2 54.1 53.2 60.7 2.3
18.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

13/10/2021 13:58:04 UTC

1 Like
2

These results look good, but this test isn’t a good way to measure connection issues. It’s generally only useful if you can’t login to the game.

Instead, you’ll want to use a WinMTR:

Also, keep in mind that a speedtest does not test connection quality, which is what we need the WinMTR to do.

3

I got disconnected a couple of times as well so I will use this as an aid to fix whatever problem exist.
Thank you for your suggestion and help. :heart:

4

I’ll check this out after I get home from work thank you

5

No worries. You may need to post the results on Pastebin.com due to link restrictions.

6

Okay I ran everything as it said to and this is what I got

7

The issue is data loss, which is happening on the first node in your ISP network (line coming to house or neighborhood hub).

Host - % Sent Recv Best Avrg Wrst Last
myrouter.local - 0 579 579 0 0 17 0
96.120.15.81 - 2 :warning: 547 539 7 10 31 9
96.110.133.9 - 2 543 534 7 10 36 15
68.86.241.21 - 2 543 534 4 10 36 15
be-611-ar02.dannythomas.tn.malt.comcast.net - 2 547 539 20 23 46 22
be-22258-cr02.dallas.tx.ibone.comcast.net - 2 543 534 29 33 61 30
be-3212-pe12.1950stemmons.tx.ibone.comcast.net - 2 543 534 29 33 63 30
66.208.216.198 - 2 543 534 29 36 120 :question: 30
ae1-br01-eqda6.as57976.net - 2 543 534 56 63 303 :question: 57
No response from host - 100 117 0 0 0 0 0
et-0-0-0-pe01-eqch2.as57976.net - 2 547 539 56 62 129 :question: 59
24.105.62.129 - 2 547 539 57 60 81 :ok: 59

You can ignore the lines with the 120, 303, and 129ms pings because the connection settles at 81ms on the last line. Overall, the test shows your worst ping is hitting 81ms. This may change if you run the test longer, or only when you’re experiencing the high ping in-game. Additionally, you may capture worse ping loss in a longer test.

8

Thank you for putting this into digestible terms for me, I’ll do my best to get comcast to play ball :slight_smile: :slight_smile: :frowning:

So I’m assuming the first line where you put the :warning: is the first node? And the fact that my receives is less than my sent is what indicated packet loss?

9

Yes, most likely. Sometimes ISPs hide some nodes, so they would be able to fully clarify that.

Well, that and the 2 (meaning 2%) next to the IP address. :slight_smile:

10

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.