IND spikes - pretty sure it's not my end

I’ve been having awful IND spikes recently, I’ve followed all the troubleshooting guides. I’m a on a wired connection, static IP, tried changing DNS servers to Google. drivers all up to date, no background apps etc.

I’m pretty sure WinMTR is showing the problem isn’t at my end:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |

Host - % Sent Recv Best Avrg Wrst Last
dsldevice. lan - 0 743 743 2 7 10 7
172. 16. 18. 220 - 0 743 743 7 9 28 11
133.hiper04.sheff.dial. plus. net. uk - 99 151 3 13 19 28 13
132.hiper04.sheff.dial. plus. net. uk - 0 743 743 13 17 31 16
peer1-et0-1-4.interxion. ukcore. bt. net - 0 743 743 13 19 76 17
195 .66 . 226. 234 - 0 742 742 15 22 94 18
ae1-br02-eqld5. as57976. net - 0 743 743 22 28 128 27
et-0-0-2-br02-eqpa4. as57976. net - 0 742 742 20 33 1104 21
bond0-vs01-eqpa4. as57976. net - 0 743 743 21 25 54 23
185. 60. 114. 159 - 0 743 743 21 24 39 24
________________________________________________ ______ ______ ______ ______ ______ ______

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

As you can see, et-0-0-2-br02- eqpa4. as57976. net is spiking at over 1000ms, which is a blizzard IP address if I’m correct? I normally get around 35ms ping 20ms IND. Recently it’s been up to 80ms ping 50ms IND, but it’s unstable and both go up and down a lot. Sometimes playing is like watching a powerpoint presentation, like a slide show it’s so choppy. Frame rates are stable though.

Any suggestions?

I’m also getting the same issue

Hey there,

Single node discrepancies on a WinMTR can be safely ignored … if latency was really that high, every node after it would also show the same issues.

This test is fine. All data makes it to us and back, worst latency is about 40ms with average latency of 24 by the time the connection reaches us.

Was this test run to the IP listed on the WinMTR article or did you run the test using the IP listed in the netgraph at the start of the affect match?

If just the ip listed in the article that won’t necessarily be to the server your match was played on.

You can get a better test using the netgraph in game. At the start of the match press CTRL-Shift-N to bring up the netgraph, use the IP at the top left and start the test. Play the match, if there is no issue, repeat with a new match. Once you replicate the issue in match, save the winmtr and paste those results here.

I was using an IP from the WinMTR artcle.

Here’s a readout from an actual game IP, where I got spikes and the yellow network notification icons came up on the left in game. I was able to capture a spike I believe:

Usally, on the amsterdam data centre, I get a consistant 29ms. But not here. . .

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

Host - % Sent Recv Best Avrg Wrst Last
dsldevice. lan - 0 189 189 2 5 9 6
172.16.18. 220 - 0 189 189 6 8 38 8
No response from host - 100 38 0 0 0 0 0
132.hiper04.sheff.dial.plus. net. uk - 0 189 189 13 17 38 17
peer2-et-0-0-4.slough.ukcore. bt. net - 0 189 189 14 19 76 18
195.66.226. 234 - 0 189 189 14 20 80 19
ae1-br01-eqld5.as57976. net - 0 189 189 20 57 255 22
No response from host - 100 38 0 0 0 0 0
137.221.65.77 - 2 177 175 0 92 4636 18
et-0-0-31-pe01-eqam1.as57976. net - 0 189 189 20 23 43 21
No response from host - 100 38 0 0 0 0 0
No response from host - 100 38 0 0 0 0 0
No response from host - 100 38 0 0 0 0 0
No response from host - 100 38 0 0 0 0 0
No response from host - 100 38 0 0 0 0 0
No response from host - 100 38 0 0 0 0 0
No response from host - 100 38 0 0 0 0 0
No response from host - 100 38 0 0 0 0 0
No response from host - 100 38 0 0 0 0 0
No response from host - 100 38 0 0 0 0 0
No response from host - 100 38 0 0 0 0 0
No response from host - 100 38 0 0 0 0 0
No response from host - 100 38 0 0 0 0 0
No response from host - 100 38 0 0 0 0 0
No response from host - 100 38 0 0 0 0 0
No response from host - 100 38 0 0 0 0 0
No response from host - 100 38 0 0 0 0 0
No response from host - 100 38 0 0 0 0 0
No response from host - 100 38 0 0 0 0 0
No response from host - 100 38 0 0 0 0 0
________________________________________________ ______ ______ ______ ______ ______ ______

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

The second test looks the same as the first. It has a great connection, ping, no data loss. It’s possible WinMTR isn’t capturing the issue, or that it’s related to hardware on the computer. WinMTR only sends one packet per second, and it’s possible you’re losing data in between those ticks on the game. But if you run it for 5-10mins, and the results are the same, I’d start looking to the computer as the source of the issue.

Any suggestions where to look next? I’ve already updated network drivers, made sure my power plan is “high performance” - closed all background applications, updated Windows, reinstalled Overwatch and updated video drivers.

MVPs and staff have a lot of experience reading these tests, and the information you’re providing is not accurate.

That is not packet loss. Check the packets sent on the first node:

189 packets sent.

189 packets received by the game server.

Any security apps that could be causing it? Check your error reporting in MSInfo (once you export it).

https :// www .dropbox. com/s/9pqp8tris17au4g/msinfo.txt?dl=0

28/02/2022 16:31	Application Error	
Faulting application name: vgtray.exe

Vanguard is known for having conflicts with Blizzard games, so you could try disabling or removing that.

You guys who? I don’t work at Blizzard.

I’m running without Vangaurd now and I got it, I captured packet loss

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

Host - % Sent Recv Best Avrg Wrst Last
dsldevice. lan - 0 428 428 0 1 15 1
172.16.18.220 - 3 398 390 4 10 53 9
No response from host - 100 86 0 0 0 0 0
128.hiper04.sheff.dial.plus. net. uk - 2 405 399 0 18 58 40
peer1-et-0-0-1.interxion.ukcore. bt. net - 1 420 418 14 21 63 40
195.66.226. 234 - 3 393 384 15 24 110 30
ae1-br01-eqld5.as57976. net - 7 338 317 21 104 4399 270
No response from host - 100 86 0 0 0 0 0
137.221.65. 77 - 7 342 321 19 80 4179 4179
et-0-0-31-pe01-eqam1. as57976. net - 2 405 399 20 26 63 48
No response from host - 100 86 0 0 0 0 0
No response from host - 100 86 0 0 0 0 0
No response from host - 100 86 0 0 0 0 0
No response from host - 100 86 0 0 0 0 0
No response from host - 100 86 0 0 0 0 0
No response from host - 100 86 0 0 0 0 0
No response from host - 100 86 0 0 0 0 0
No response from host - 100 86 0 0 0 0 0
No response from host - 100 86 0 0 0 0 0
No response from host - 100 86 0 0 0 0 0
No response from host - 100 86 0 0 0 0 0
No response from host - 100 86 0 0 0 0 0
No response from host - 100 86 0 0 0 0 0
No response from host - 100 86 0 0 0 0 0
No response from host - 100 86 0 0 0 0 0
No response from host - 100 86 0 0 0 0 0
No response from host - 100 86 0 0 0 0 0
No response from host - 100 86 0 0 0 0 0
No response from host - 100 86 0 0 0 0 0
No response from host - 100 86 0 0 0 0 0
________________________________________________ ______ ______ ______ ______ ______ ______

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

It’s likely one or both of these ISP nodes I mentioned above. Once again you can ignore the 7% loss line. While it probably has some data loss (just measures the previous hops), it goes back to 2% loss on the last line, which is what matters.

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