Constant Latency Spikes lasting 1-2 secs, happening every 10 secs or so

So I’ve been having a strange problem for the last 2-3 days when playing. Everything will be fine, around 20ms (I have Virgin 100 internet) and then every 10 seconds or so, I will get a surge where my MS goes to about 1k for only 1-2 seconds. This happens constantly, whether I am in the practice range, Comp, or quick play. I’ve used the Ctrl-Shift-N to get the network graph up, and it is like clockwork, every 10 secs, i get the orange network logo flash on the left hand side of the screen for about 1-2 secs, and my MS spikes up to ~1K and then straight back down to about 20. It is so strange that there is such a constant pattern to this spiking in ms.
Obviously during this 1-2 seconds of high latency, players and enemies on my screen freeze, and then immediately resume having jumped/ported to a new position etc. As you can imagine this is infuriating to play with.

Can someone please help me with this. I’ve played OW since launch, on this same laptop, pretty much most days with no problems whatsoever, and then this week I’ve encountered this issue. Nothing has been downloaded/changed/configured on my laptop for this to happen.

Also it is worth noting this is only happening in OW, when playing WoW I have no issues.

Many thanks for reading.

2 Likes

Same, except for me its been about a week or so. No issues on ANY other games that i play. No hardware changes, no driver updates, same wired connection, nada. Just all of the sudden random lag spikes every game from 60ms up to 300-500ms then back down to 60…then back up…then back down. Judging by all the other related threads they just chalk it up to your router. If that were the case, im pretty sure ALL my games would be lagging, not only overwatch. :man_shrugging:

What troubleshooting steps from the stickied threads have you tried already?

Can we see your WinMTR results? Blizzard Support - Running WinMTR

Just because you’re not having issues connecting to other games or websites, doesn’t mean the issue is Blizzard’s fault or an issue with your modem/router. It could be that your ISP uses a connection path that has problems on the way TO Blizzard. So try some troubleshooting steps, report back on what you’ve tried, and then we can look over your pathping, tracert, and WinMTR results. I’m listening if you want help.

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

Host - % Sent Recv Best Avrg Wrst Last
FoWifiNet - 0 534 534 0 1 50 1
10.11.0.1 - 0 534 534 8 18 284 18
10.145.3.5 - 1 531 530 13 55 878 18
No response from host - 100 107 0 0 0 0 0
10.101.17.41 - 0 534 534 9 39 902 18
10.101.1.10 - 1 531 530 9 44 749 16
10.145.1.9 - 1 519 515 9 53 890 11
10.101.130.10 - 1 527 525 10 46 797 19
No response from host - 100 107 0 0 0 0 0
No response from host - 100 107 0 0 0 0 0
No response from host - 100 107 0 0 0 0 0
No response from host - 100 107 0 0 0 0 0
No response from host - 100 107 0 0 0 0 0
No response from host - 100 107 0 0 0 0 0
No response from host - 100 107 0 0 0 0 0
No response from host - 100 107 0 0 0 0 0
No response from host - 100 107 0 0 0 0 0
No response from host - 100 107 0 0 0 0 0
No response from host - 100 107 0 0 0 0 0
No response from host - 100 107 0 0 0 0 0
No response from host - 100 107 0 0 0 0 0
No response from host - 100 107 0 0 0 0 0
No response from host - 100 107 0 0 0 0 0
24.105.62.129 - 0 534 534 44 50 84 52
________________________________________________ ______ ______ ______ ______ ______ ______

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

TRACEROUTE:
traceroute to 96.8.173.20 (96.8.173.20), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.312 ms 0.294 ms 0.290 ms
2 37.244.22.131 (37.244.22.131) 0.627 ms 0.697 ms 0.894 ms
3 24.105.30.152 (24.105.30.152) 1.274 ms 1.311 ms 1.382 ms
4 137.221.66.6 (137.221.66.6) 1.651 ms 1.741 ms 1.798 ms
5 137.221.68.68 (137.221.68.68) 1.492 ms 1.495 ms 1.494 ms
6 137.221.68.32 (137.221.68.32) 1.199 ms 1.614 ms 1.588 ms
7 213.248.78.166 (213.248.78.166) 1.576 ms 1.517 ms 1.536 ms
8 dls-b21-link.telianet (62.115.123.136) 32.371 ms 32.367 ms 31.927 ms
9 aust-b1-link.telianet (62.115.116.4) 36.609 ms 36.605 ms 36.598 ms
10 guadalupe-ic-324062-aust-b1.c.telianet (62.115.153.197) 38.566 ms 38.582 ms 38.520 ms
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *

10/08/2018 02:41:03 UTC

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

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

10/08/2018 02:41:03 UTC

MTR:
Start: Fri Aug 10 02:41:03 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.3 0.3 0.4 0.0
2.|-- 37.244.22.131 0.0% 10 0.5 0.6 0.5 0.7 0.0
3.|-- 24.105.30.152 0.0% 10 1.3 1.1 1.1 1.3 0.0
4.|-- 137.221.66.6 0.0% 10 1.8 1.6 1.5 1.8 0.0
5.|-- 137.221.68.68 0.0% 10 1.4 1.6 1.4 2.5 0.0
6.|-- 137.221.68.32 0.0% 10 1.2 2.6 1.1 14.8 4.3
7.|-- 213.248.78.166 0.0% 10 1.5 1.5 1.4 1.8 0.0
8.|-- dls-b21-link.telianet 0.0% 10 31.9 33.9 31.9 46.4 4.4
9.|-- aust-b1-link.telianet 0.0% 10 40.7 36.3 35.8 40.7 1.5
10.|-- guadalupe-ic-324062-aust-b1.c.telianet 0.0% 10 38.7 38.6 38.4 38.9 0.0
11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

10/08/2018 02:41:03 UTC

i used the US Central server

Weird, after the tests i had two full games with no ping/latency issues. then it randomly came back again

Looks like you have some packet loss on your home network, as those response times are way too high (800+ms). You’ll likely need to contact your ISP if you’re using their hardware to connect.