[NTE Bredband] Lag/ping spikes during matches

Technical Support
1

Greetings.
During my time with overwatch from 2017 to 2020 i’ve never had much of an issue playing the game outside of those crazy random times something goes horribly wrong and people start T-posing and flying everywhere, but during fall 2020 i started noticing worrying details that have made playing the game worse and worse for me.
It started as me just noticing that when i would be strafing left and right to dodge shots, my character would strafe one more time without my input.
Then for example, i would send out an orb as Moira and then immediately after i would send the same orb out again, maybe even a third time, this was annoying, but not game breaking so i continued on.
However, i have been plagued by increasing amounts of what i can only describe as double inputs and recently alot of lag spikes or high jumps in ping.
Usually i’ve enjoyed ping around 58ms, but during these spikes it would jump from 60+ to 175+ and completely throw off my gameplay and lose matches for me and my friends.
I took a test and these are the results that came up, i don’t understand them myself, but i hope someone can help me look into it.

TRACEROUTE:
traceroute to 178.164.102.91 (178.164.102.91), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.258 ms 0.251 ms 0.252 ms
2 37.244.25.2 (37.244.25.2) 0.540 ms 0.683 ms 0.879 ms
3 Blizzard Blizzard 1.208 ms 1.208 ms 1.210 ms
4 137.221.66.32 (137.221.66.32) 1.164 ms 1.179 ms 1.178 ms
5 137.221.77.76 (137.221.77.76) 753.990 ms 920.811 ms 920.826 ms
6 * * *
7 * * *
8 137.221.78.34 (137.221.78.34) 35.105 ms 35.136 ms 35.126 ms
9 * * *
10 89.151.232.151.nteb.no (89.151.232.151) 40.974 ms 41.016 ms 41.460 ms
11 89.151.232.151.nteb.no (89.151.232.151) 40.632 ms 40.700 ms 40.671 ms
12 * * *
13 * * *
14 * * *
15 * * *

30/12/2020 06:13:00 UTC

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

— 178.164.102.91 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 3001ms

30/12/2020 06:12:59 UTC

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

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

30/12/2020 06:13:00 UTC

TRACEROUTE:
traceroute to 178.164.102.91 (178.164.102.91), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.305 ms 0.289 ms 0.287 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *

30/12/2020 06:12:59 UTC

MTR:
Start: Wed Dec 30 06:13:00 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.6 0.3 0.2 0.6 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

30/12/2020 06:12:59 UTC

MTR:
Start: Wed Dec 30 06:13:00 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.4 0.0
2.|-- 37.244.25.2 0.0% 10 323.2 237.7 0.6 331.7 130.9
3.|-- Blizzard 0.0% 10 0.8 0.9 0.8 1.1 0.0
4.|-- 137.221.66.32 0.0% 10 36.9 4.5 0.4 36.9 11.4
5.|-- 137.221.77.76 0.0% 10 39.5 598.5 39.5 1253. 391.5
6.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
7.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
8.|-- 137.221.78.34 0.0% 10 10.1 11.4 9.8 24.7 4.6
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
10.|-- 89.151.232.151.nteb.no 0.0% 10 41.1 41.1 40.9 41.3 0.0
11.|-- 89.151.232.151.nteb.no 0.0% 10 40.9 40.9 40.7 41.2 0.0
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

30/12/2020 06:13:00 UTC

2

Can you run the WinMTR test instead?

Click here to show/hide WinMTR instructions

Carefully follow the Blizzard support documentation for WinMTR.

  • The IP address needed for the test is gathered during gameplay. IPs listed on the instruction page should only be used in special circumstances.
  • Make sure the connection issue is caught in the test or the test lasts for at least 5 minutes.

Share your results in a reply:

  1. Click the “Copy Text to clipboard” button after you’ve finished the test.
  2. Paste the text in a reply, highlight it, then click </> on the post editor.
  3. If you can’t post links, add spaces before .com/.net/.us/.au, etc., which will break the link and allow you to post.
    • You can also post the results on Pastebin.com and provide the link in your reply if you have issues posting results here.

Please do not remove full hostnames from the test instead of “breaking the links” with spaces, as this makes troubleshooting much more difficult.

3

A post was merged into an existing topic: Interpolation Delay

4

Thanks for your reply, i apologize for the silence, but i thought i had fixed the issue with the help of some friends. Unfortunately this is not the case, as more spikes have started appearing for me. I ran the test and this is the result, if you could take a look at it.
|------------------------------------------------------------------------------------------|

|                                      WinMTR statistics                                   |

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

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

|                                    home -    0 |  407 |  407 |    0 |   17 |  384 |    8 |

|                  89.151.255.178.nteb.no -    1 |  403 |  402 |    2 |   19 |  342 |    2 |

|            217-168-93.93.ntebredband.no -    1 |  403 |  402 |    9 |   28 |  335 |    9 |

|            217-168-93.93.ntebredband.no -    1 |  403 |  402 |    8 |   27 |  273 |   12 |

|          lag-126.bear1.Oslo2.Level3.net -    1 |  403 |  402 |    8 |   27 |  365 |   10 |

|   ae-2-3204.edge7.Amsterdam1.Level3.net -    1 |  400 |  398 |   39 |   63 |  372 |   40 |

| BLIZZARD-EN.edge7.Amsterdam1.Level3.net -    1 |  403 |  402 |   33 |   57 |  346 |   33 |

|              ae1-br02-eqam1.as57976.net -    6 |  332 |  314 |   40 |  264 | 3694 |  595 |

|                           137.221.65.77 -    9 |  294 |  269 |   33 |  298 | 3653 |   70 |

|            bond0-vs01-eqam1.as57976.net -    1 |  403 |  402 |   33 |   56 |  325 |   43 |

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

The home network looks quite unstable. Are you playing on WiFi? If so, I recommend trying a cable connection, or changing wireless channels. 384ms is way higher than you want to your own home equipment.

6

My regular ping is very stable though, it just spikes randomly for seemingly no reason and i don’t really have this issue in other games, that’s why i wonder why it happens in overwatch.
My plans are to get a long enough cable for ethernet, but it’s going to take some work and even then i’m used to very stable wifi, not perfect, but absolutely playable until it spikes.

7

Those games might have a lower tick rate than Overwatch, but it’s hard to say for certain that this would be the cause. Ideally, though, Overwatch should be played on a wired connection.

Spikes can be congested channels on the router, interference, or just flooding if it has QoS settings that need adjusting.