Much higher ping than usual lately (Overwatch only)

I would say for the past month or so I have had much higher ping than usual. I am usually at about 40 but it has been consistently at 80 or so. And now with these latest patch I am always at 120 ping with stutters that feel like they are caused from latency issues.

2 Likes

While I realize this is double the ping you’re used to, it’s still considered acceptable since the staff has said it’s close to the average most players see on the game. Have you run the WinMTR they suggest? Can you post the results here? If you missed it, instructions are at the top of the forum:

I agree that it is annoying but still playable if it stayed at 80, but it continues to get worse every patch and is very inconsistent. Sometimes it feels playable even at high ping and other times there is stuttering from latency.

I have tried different cables, different ports on my router, and power cycled the router. Here is the WinMTR file while the ping was around 110~115.

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

| WinMTR statistics |

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

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

| 192.168.0.1 - 0 | 135 | 135 | 0 | 8 | 17 | 15 |

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

| 24-155-250-137.dyn.grandenetworks. net - 0 | 135 | 135 | 7 | 23 | 70 | 41 |

| ae4.0.core01.gf01.dllstx.grandecom. net - 0 | 135 | 135 | 8 | 24 | 62 | 25 |

|24-155-121-220.static.grandenetworks. net - 0 | 135 | 135 | 8 | 22 | 62 | 10 |

| ae10.0.core01.smrctx.grandecom. net - 0 | 135 | 135 | 13 | 26 | 53 | 29 |

| lag-108.bear1.Houston1.Level3. net - 2 | 128 | 126 | 18 | 26 | 46 | 20 |

| ae-2-3608.ear7.Chicago2.Level3. net - 97 | 29 | 1 | 0 | 48 | 48 | 48 |

| BLIZZARD-EN.ear7.Chicago2.Level3. net - 0 | 135 | 135 | 38 | 54 | 117 | 38 |

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

| et-0-0-3-br02-eqla1.as57976. net - 0 | 135 | 135 | 65 | 117 | 856 | 87 |

| be3-pe02-eqla3.as57976. net - 0 | 135 | 135 | 93 | 111 | 183 | 111 |

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

|____________|||||||

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

Patches don’t change the route you use for the game, they change the client software itself.

I do see that the average ping in this test is 111ms, which seems kinda high. Are you located in Texas? If so, there should be a relatively similar ping to both Chicago and Los Angeles from there. Have you tried running the test to the LA server instead?

Hey Joe!

It looks like the network service provider might be doing maintenance. I notice all users of the same ISP had higher latency at the same time you were! It looks to be normal currently but I’ll definitely keep an eye on this on our side.

Since the problem appears to be the hand-off between Grande and Level3, please be sure to contact them directly to have them escalate the report:

Basically they’d need to have one of their tier 3 agents put in a ticket with the higher ups to check with their peer network Level3 on the issue. That is if they’re not already aware of it which is super possible since it looks to be going back to normal.

I wish we had a more direct solution here but I do hope the info helps. If there’s anything else you might need just let us know!

Cheers!

I know. It’s probably just confirmation bias but it has been getting worse. Have not had the stuttering latency issue until right after this latest patch.

I am in Texas and here is the logs for when I was playing on the Chicago server. I also noticed that the lighting bolt with a circle around it was showing up as well as the packet loss notification once in a while.

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

| WinMTR statistics |

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

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

| 192.168.0.1 - 0 | 2989 | 2989 | 0 | 0 | 93 | 0 |

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

| 24-155-250-137.dyn.grandenetworks. net - 0 | 2989 | 2989 | 3 | 12 | 131 | 12 |

| ae4.0.core01.gf01.dllstx.grandecom. net - 0 | 2989 | 2989 | 7 | 13 | 115 | 8 |

| static.rcn. com - 0 | 2989 | 2989 | 36 | 41 | 163 | 42 |

| hge0-0-0-9.core1.lnh.md.rcn. net - 0 | 2989 | 2989 | 37 | 42 | 182 | 44 |

| hge0-0-0-2.border1.eqnx.va.rcn. net - 1 | 2982 | 2980 | 34 | 41 | 182 | 39 |

| eqix-dc2.blizzard. com - 0 | 2989 | 2989 | 38 | 47 | 182 | 44 |

| ae1-br01-eqdc2.as57976. net - 0 | 2989 | 2989 | 55 | 83 | 332 | 61 |

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

| et-0-0-0-pe01-eqch2.as57976. net - 0 | 2989 | 2989 | 55 | 63 | 184 | 61 |

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

|____________|||||||

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

Hey again,

I’m seeing that all users Grande having the same latency as this account. This typically means the provider itself is having a problem.

I have seen some users change their routing by using a VPN service, but those are typically paid for programs that we can’t recommend through support. It may be best to discuss the problem with Grande directly.

Hope the info helps. Cheers!

1 Like

Wow. That was definitely the issue. Tried using a VPN and am getting 40 ping to central server and 70 ping to west server, pretty much exactly what I was getting before it went downhill.

Just wanted to go on record as another Grande customer having this issue since December. It all starts with the static.rcn com hop in one of the winmrt above. This is for all blizzard games, not just overwatch for me. Used to have 30-45ish ping in game. Now it’s rarely below 100.

Here’s mine…

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

Host - % Sent Recv Best Avrg Wrst Last
192.168.1.1 - 0 55 55 0 0 1 0
No response from host - 100 11 0 0 0 0 0
24-155-250-209.dyn.grandenetworks. net - 0 55 55 7 12 30 13
ae6.61.core01.gf01.dllstx.grandecom. net - 0 55 55 20 26 60 34
static.rcn. com - 0 55 55 94 99 105 104
hge0-0-0-5.core2.lnh.md.rcn. net - 0 55 55 95 100 105 96
hge0-0-0-3.border1.eqnx.va.rcn. net - 0 55 55 95 100 105 101
eqix-dc2.blizzard. com - 0 55 55 96 104 151 101
ae1-br01-eqdc2.as57976. net - 0 55 55 113 148 360 161
No response from host - 100 11 0 0 0 0 0
et-0-0-0-pe02-eqch2.as57976. net - 0 55 55 113 119 171 117
No response from host - 100 11 0 0 0 0 0
No response from host - 100 11 0 0 0 0 0
No response from host - 100 11 0 0 0 0 0
No response from host - 100 11 0 0 0 0 0
No response from host - 100 11 0 0 0 0 0
No response from host - 100 11 0 0 0 0 0
No response from host - 100 11 0 0 0 0 0
No response from host - 100 11 0 0 0 0 0
No response from host - 100 11 0 0 0 0 0
No response from host - 100 11 0 0 0 0 0
No response from host - 100 11 0 0 0 0 0
No response from host - 100 11 0 0 0 0 0
No response from host - 100 11 0 0 0 0 0
No response from host - 100 11 0 0 0 0 0
No response from host - 100 11 0 0 0 0 0
No response from host - 100 11 0 0 0 0 0
No response from host - 100 11 0 0 0 0 0
No response from host - 100 11 0 0 0 0 0
No response from host - 100 11 0 0 0 0 0
________________________________________________ ______ ______ ______ ______ ______ ______

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

I’m in Austin and DON’T use Grande and have had zero issues, so it’s probably Grande.

1 Like

As someone else said, I’ve tried a VPN as well and it solves the issue so it definitely is Grande or their peer partners.

1 Like