Latency spikes

Technical Support
Few weeks ago I bought with new laptop (Asus Vivibook S15). Since then when I play Overwatch I get lag spikes. I have not observed much but they show up from time to time and most noticeable during skirmishes. I have played the game always on WiFi and never had such problems (with my old laptop). I doubts the system is weak for the game - it got 16 GB RAM and i7 7700HQ with GeForce GTX 1050. Even with my old laptop which was 8 years old and much worse configuration I had no trouble playing the game. Also, I've been testing on 3 different locations and different cities with the same result. Haven't played the game for few months and now coming back to such lag spikes is pain in the !@#.
I checked my ping times to the server's IP 185.60.112.157. This is the result and it pretty much sums up the latency I get during play:

Pinging 185.60.112.157 with 32 bytes of data:
Reply from 185.60.112.157: bytes=32 time=52ms TTL=241
Reply from 185.60.112.157: bytes=32 time=52ms TTL=241
Reply from 185.60.112.157: bytes=32 time=51ms TTL=241
Reply from 185.60.112.157: bytes=32 time=52ms TTL=241
Reply from 185.60.112.157: bytes=32 time=52ms TTL=241
Reply from 185.60.112.157: bytes=32 time=129ms TTL=241
Reply from 185.60.112.157: bytes=32 time=191ms TTL=241
Reply from 185.60.112.157: bytes=32 time=270ms TTL=241
Reply from 185.60.112.157: bytes=32 time=166ms TTL=241
Reply from 185.60.112.157: bytes=32 time=52ms TTL=241
Reply from 185.60.112.157: bytes=32 time=52ms TTL=241
Reply from 185.60.112.157: bytes=32 time=52ms TTL=241
Reply from 185.60.112.157: bytes=32 time=52ms TTL=241
Reply from 185.60.112.157: bytes=32 time=52ms TTL=241
Reply from 185.60.112.157: bytes=32 time=52ms TTL=241
Reply from 185.60.112.157: bytes=32 time=52ms TTL=241
Reply from 185.60.112.157: bytes=32 time=52ms TTL=241
Reply from 185.60.112.157: bytes=32 time=103ms TTL=241
Reply from 185.60.112.157: bytes=32 time=222ms TTL=241
Reply from 185.60.112.157: bytes=32 time=200ms TTL=241
Reply from 185.60.112.157: bytes=32 time=119ms TTL=241
Reply from 185.60.112.157: bytes=32 time=180ms TTL=241
Reply from 185.60.112.157: bytes=32 time=52ms TTL=241
Reply from 185.60.112.157: bytes=32 time=52ms TTL=241
Reply from 185.60.112.157: bytes=32 time=52ms TTL=241
Reply from 185.60.112.157: bytes=32 time=52ms TTL=241
Reply from 185.60.112.157: bytes=32 time=52ms TTL=241
Reply from 185.60.112.157: bytes=32 time=52ms TTL=241
Reply from 185.60.112.157: bytes=32 time=52ms TTL=241
Reply from 185.60.112.157: bytes=32 time=52ms TTL=241
Reply from 185.60.112.157: bytes=32 time=52ms TTL=241
Reply from 185.60.112.157: bytes=32 time=52ms TTL=241
Reply from 185.60.112.157: bytes=32 time=190ms TTL=241
Reply from 185.60.112.157: bytes=32 time=272ms TTL=241
Reply from 185.60.112.157: bytes=32 time=194ms TTL=241
Reply from 185.60.112.157: bytes=32 time=52ms TTL=241
Reply from 185.60.112.157: bytes=32 time=52ms TTL=241
Reply from 185.60.112.157: bytes=32 time=52ms TTL=241
Reply from 185.60.112.157: bytes=32 time=52ms TTL=241
Reply from 185.60.112.157: bytes=32 time=52ms TTL=241
Reply from 185.60.112.157: bytes=32 time=52ms TTL=241
Reply from 185.60.112.157: bytes=32 time=52ms TTL=241
Reply from 185.60.112.157: bytes=32 time=57ms TTL=241
Reply from 185.60.112.157: bytes=32 time=53ms TTL=241
Reply from 185.60.112.157: bytes=32 time=52ms TTL=241
Reply from 185.60.112.157: bytes=32 time=55ms TTL=241
Reply from 185.60.112.157: bytes=32 time=254ms TTL=241
Reply from 185.60.112.157: bytes=32 time=54ms TTL=241
Reply from 185.60.112.157: bytes=32 time=52ms TTL=241
Reply from 185.60.112.157: bytes=32 time=52ms TTL=241
Reply from 185.60.112.157: bytes=32 time=56ms TTL=241
Reply from 185.60.112.157: bytes=32 time=54ms TTL=241
Reply from 185.60.112.157: bytes=32 time=72ms TTL=241
Reply from 185.60.112.157: bytes=32 time=52ms TTL=241
Reply from 185.60.112.157: bytes=32 time=52ms TTL=241
Reply from 185.60.112.157: bytes=32 time=53ms TTL=241
Reply from 185.60.112.157: bytes=32 time=52ms TTL=241
Reply from 185.60.112.157: bytes=32 time=233ms TTL=241
Reply from 185.60.112.157: bytes=32 time=174ms TTL=241
Reply from 185.60.112.157: bytes=32 time=52ms TTL=241
Reply from 185.60.112.157: bytes=32 time=52ms TTL=241
Reply from 185.60.112.157: bytes=32 time=52ms TTL=241
Reply from 185.60.112.157: bytes=32 time=52ms TTL=241
Hello chixlovem,

Keep in mind that Wifi connections can easily be affected by interferences. Due to this, we don't offer support for this kind of connections (we can try to help, but we can't assure that it's going to work). We always recommend connecting via cable whenever possible.

Now, you mention having tried in different locations/cities, but was the connection different as well, or some kind of mobile router?

I would start by checking this article and making sure you follow all the instructions, including the advanced steps:
battle.net/support/article/99037

If the issue persists, we would need the following diagnostics so we can take a look:

- Traceroute (right after a disconnection or whenever you're experiencing the issue)
- Pathping (right after a disconnection or whenever you're experiencing the issue)
- WinMTR (right after a disconnection or whenever you're experiencing the issue)

______________________________________________________
Got feedback about the support I'm providing? Leave your comments here!

Join the Conversation

Return to Forum