Extremely High Home Latency

Support Technical Support
1

Good evening. Over the past month or so I have experience extremely high latency when playing WoW. My main is on Stormrage-US. I have never experienced this before. When I start WoW it starts pretty relative, about 60ms home&world. Over time, about 10 or so minutes, it rises to unplayable levels such as 3500ms for home latency only. This makes interacting with NPCs, porting to zones, and ect absolutely impossible.

I play WoW primary on my desktop, via wired, and this issue is subject to my desktop only. When I play on my laptop, via WiFi, it does not occur.

As stated, I use a wired connection on my Desktop, which connects to my Nighthawk router.

I of course did research on this issue and have tried every possible fix. The following is what I have done so far and nothing has been successful:

-Flush DNS
-Have checked and unchecked all the network settings in-game
-Reset WoW interface
-Reinstalled WoW all together
-Reformat my desktop with a clean install of Windows
-Reset route
-Change out all my Cat 5e cables for Cat 8 cables
-Install a new network card in my desktop
-Connect directly to my modem and bypassed my router

WinMRT ran for just over 10 minutes while playing WoW

WinMTR Statistics

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
192.168.1.1 0 831 831 0 0 16 14
67-218-102-91.cust.layer42.net 35 355 234 8 13 24 12
174.127.182.52 36 347 224 8 14 26 12
be3.cr1-kirkham.bb.as11404.net 36 347 224 8 15 30 15
be2.cr1-fdcp.bb.as11404.net 36 347 224 10 17 36 15
port-b1-link.telia.net 37 343 219 14 20 40 18
sea-b2-link.telia.net 36 347 224 14 23 88 28
att-ic-338580-sea-b2.c.telia.net 40 327 199 30 37 70 43
st0wa81crs.ip.att.net 41 319 189 72 79 118 78
st6wa22crs.ip.att.net 41 319 189 72 80 118 82
cgcil22crs.ip.att.net 39 331 204 72 82 94 83
gar3.cgcil.ip.att.net 38 336 210 71 90 246 74
12.122.251.50 90 183 19 0 79 94 82
No response from host 100 168 0 0 0 0 0
No response from host 100 168 0 0 0 0 0
No response from host 100 168 0 0 0 0 0
No response from host 100 168 0 0 0 0 0
No response from host 100 168 0 0 0 0 0
No response from host 100 168 0 0 0 0 0
No response from host 100 168 0 0 0 0 0
No response from host 100 168 0 0 0 0 0
No response from host 100 168 0 0 0 0 0
No response from host 100 168 0 0 0 0 0
No response from host 100 168 0 0 0 0 0
No response from host 100 168 0 0 0 0 0
No response from host 100 168 0 0 0 0 0
No response from host 100 168 0 0 0 0 0
No response from host 100 168 0 0 0 0 0
No response from host 100 168 0 0 0 0 0
No response from host 100 168 0 0 0 0 0

As you see I have tried just about everything besides buying a new computer, haha. I am desperate to fix this before Shadowlands drops. Any suggestions would greatly helped.

Thank you!

2

With all those “No response from host,” I recommend you reach out to your ISP in order to see what they can do on their end to fix your service.

3

Please read my post. I am not having this issue on my laptop, only my desktop…

4

I have a desktop and in posts I’ve made the “No response from host” within my WinMTR tests did have Blizzard employees direct me to reach out to my Internet Service Provider in order to solve the issue.

5

Hey there! We appreciate you taking the time to reach out with those details regarding this persistent latency problem. The WinMTR test is showing a significant spike in packet loss beginning at the second “hop”, which appears to be directly outside of your home network:

Above we can see that you have a strong, stable connection to your router. The second hop, however, is where that 35% packet loss begins and persists through all subsequent hops. This basically means that only a portion of the network data is reaching the game server, and when this happens, you can experience fluctuating latency or a complete disconnect from the server.

To confirm a potential ISP issue, can you temporarily test an alternate network such as a mobile hotspot or VPN?

If the latency issue disappears when using an alternate network, at that point we can be sure that the issue is isolated to the primary network. In these situations, ultimately we can only recommend contacting the Internet Service Provider (ISP) for assistance determining what is causing the issue to occur on that specific network. They might need to adjust network-level security/firewall settings on your modem or temporarily replace the device to narrow it down further. I always recommend requesting to be forwarded to a “level 2 or level 3 technician” when contacting the ISP since the front-line representatives typically only have access to basic diagnostics and troubleshooting tools.

I hope this helps! Let us know if you have any questions going forward.

6

Since that is the first hop and this is a fiber based ISP, he’ll definitely need to get in touch with them. 35% packet loss on a fiber connection indicates either malfunctioning equipment or possibly a fiber line cut somewhere between the OP’s residence and first PON relay. Given that this is in Mountain View, their response should be relatively quick as they serve some high profile customers out there.