Lag in m+ and raid (help to understand WinMTR/Ping Plotter)

Hey there. I’m writing to hear if anyone else is experiencing the same as me, and to get a little bit of help understanding my WinMTR log and Ping Plotter.

Currently whenever i go to raid or play m+ in the evening, I experience constant smaller spikes of lag, where the game will stop for a second or two before then continuing (this is not FPS lag). In some occurrences, it will go 5+ seconds and a few times I even had like a 30 second lag spike. I never disconnect and no one else in my instance is affected.

This has now occurred over multiple weeks and it is getting really annoying. I experience no issues with discord or streaming when i lag, but I understand this could be due to smaller packets and buffering.

I’ve contacted my ISP, but so far it’s been a slow process of “reset your router” etc.

Here is a winMTR log i ran during some M+ gameplay last night (used netstat to find which blizzard server i was connecting to):
https://imgur.com/a/RGzPxF0

The WinMTR log to me looks like it would be a problem either on Blizzards end or maybe a routing issue, but I’m not sure exactly what to conclude.

Here is a ping plotter i just ran this morning to google.com:
https://share.pingplotter.com/ZhT9UYqQyHi

Now, the pingplotter to me looks very bad, but I’m not sure I’m fully capable of understanding it. I read that I shouldn’t be too concerned with the high packet loss to the router, as it can choose to disregard the pings to prioritize other things.

Hope someone who knows more about this stuff can chip in and help, thanks!

1 Like

It looks like there’s an issue with the Blizzard peering point that your ISP is using - at first glance it looks more likely than not that the issue is on Blizzard’s side - but your ISP also seems to be introducing more latency within their own network than I’d expect, so I’m reluctant to rule them out completely.

Most likely their network engineers will be already be aware of the issue and IME issue like this tend to be fixed after a few days.

All you can do on your side it keep raising it with your ISP in the hope that one of their CS reps will escalate it to their network engineers for an update/fix.