I want to preface this by stating that I am fully aware that I am ALSO experiencing packet loss on my end, which I need to discuss with my ISP. Perhaps someone here can help break down if this issue is entirely on my end or if this is on both my end and Blizzard’s end.
However, when running PingPlotter in an effort to narrow down this issue I’ve noticed that this particular node (137.221.72.33 – Hop 8) is displaying abnormally high packet loss and latency.
The lag in-game is very noticeable and makes it very difficult to actually play and enjoy the game. I didn’t notice this at the start of the season because I wasn’t really playing much, but I have most definitely noticed it since the mid season patch, when I picked the game back up again.
If anyone knows a better way to make this legible, please let me know. I’m not too familiar with the forum formatting.
Unless the latency on that node also affects the nodes after it, then you’re just seeing it ignore ICMP requests. This is a common mechanism to protect against DDoS attacks. Doesn’t look like it traveled the whole test.
Okay thanks, I wasn’t sure how to interpret it. I appreciate your swift response, Nicole.
Just trying to figure out where my rubberbanding is coming from because I did notice that when that node was out of whack I did rubberband in-game since I had it on my secondary monitor. Unless it was also coinciding with what may be happening on my end with my ISP.
Especially since what I’ve seen in the PingPlotter is translating to a higher than normal latency for me in-game as well. I used to get 60ms in this game, before the Chicago servers were removed I had 20ms, now I’m lucky if I get 79 ms because usually it’s 90ms + to the Central server. That 90ms usually shoots up to 120 ms and then back down again constantly making the game completely unplayable in comp, which is my preferred mode.
Sorry for the delay Nicole, this issue doesn’t happen every day and mostly only consistently Sundays so I had to wait to test it.
PingPlotter isn’t creating a link at the end of the test, it just relapses over to the next test time. I’m probably not setting it properly, but I was able to take a screenshot of one of the times I tested for 15 minutes.
`https(:)//imgur(.)com/a/4MVHuY8
^ Link to the picture that I got through edit → copy image.
During this time I completely rubberbanded within the game, got booted out of the server I was playing in, sent back to main menu but still in the match, and then I loaded back in.
Edit: unfortunately I’m only trust level 2 so I can’t link create a proper link. You’ll have to copy and paste, my apologies.
Looks like all 239 packets you sent made it to the server, so you can ignore the ICMP loss off to the right. If you’re only experiencing these problems on a specific day of the week, I highly suggest talking to the ISP about it. That generally points to the local neighborhood nodes being overloaded. But as far as the test goes, your ping should be about 51ms.
When this happened my ping in game was 120. But I’ll be sure to have a chat with my ISP about it. Thank you for your time and patience in responding to my thread, I appreciate it.
I’ve been affected by this as well (large latency spikes since the mid season patch).
I’m sincerely hoping the next patch corrects it, because Overwatch is the only game I play that is having this issue. Usually I’m at 40ms, but for about a week and half now, maybe more, it bounces between 70 on a good night, and 100 on a bad night.
I already talked to my ISP and they said my router was out of date (doesn’t make much of a difference, I play on a hard line) and no other games are experiencing lag like this.
Are there any steps I can take to try and remedy this that won’t have the person on the other end asking me to take parts out of my pc as part of the troubleshooting process?
