Latency issues for a while now

Stephnrock-scilla · July 6, 2019, 3:16pm

The norm is around 56-58 MS world/home.
Last couple weeks … 1500-1800 … reaching 3500 sometimes.

Ill be ingame, the game would freeze up, about 10-12 seconds later everything shoots into turbo speed, catching up.

Caedmun-moon-guard · July 6, 2019, 3:54pm

I’ve been getting this since BfA release. There are some other old threads on it. Basically, works well most of the time, but periodically, 10-12 second lag spike, then snapping back to normal.

I get this issue with no other game. Still haven’t figured it out.

Elocin-mugthol · July 7, 2019, 4:53am

Whoa, that is a long delay. Let’s look at a WinMTR.

WinMTR instructions (click to expand/collapse)

Follow the support documentation for WinMTR. Use an IP from the table provided on that page that matches your region. Run the test until you encounter the issue again, or for at least 10 minutes.

Share your results in a reply:

Click the “Copy Text to clipboard” button after you’ve finished the test per the instructions.
Paste the text in a reply, then highlight the pasted text and click </> on the post editor.
Break any links by adding a space before .com, .net, etc.

Taldk-sargeras · July 7, 2019, 5:09am

Having the same issue. I posted my MTR in a related thread. Strange latency issues - #4 by Taldk-sargeras

Rabidstray-dalaran · July 7, 2019, 7:10am

Try installing Leatrix Latency Fix, I had to install it back in WoTLK. My MS was well over 2k at that time before install, after it helped a ton with lag and latency, now if I have an issue I know it’s WoW servers as my connection is super fast and rarely ever has any problems or goes out, but when I seek help they always blame my connection. Now I’m less than 100ms 99% of the time.

Stephnrock-scilla · July 7, 2019, 5:22pm

WinMTR
|------------------------------------------------------------------------------------------|

| WinMTR statistics |

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

| dsldevice.attlocal - 0 | 408 | 408 | 0 | 1 | 352 | 0 |

|99-114-144-1.lightspeed.chrlnc.sbcglobal 4 | 343 | 330 | 22 | 95 | 4875 | 23 |

| 99.144.25.26 - 5 | 341 | 327 | 25 | 95 | 4851 | 28 |

| 12.240.208.130 - 4 | 342 | 330 | 32 | 128 | 4741 | 38 |

| 12.123.43.197 - 5 | 330 | 316 | 32 | 145 | 4879 | 33 |

| 12.247.68.74 - 3 | 351 | 342 | 33 | 133 | 4829 | 34 |

| ae1-br01-eqat2.as57976 4 | 346 | 335 | 54 | 144 | 4751 | 55 |

| et-0-0-4-br02-eqch2.as57976 4 | 339 | 326 | 0 | 147 | 4748 | 54 |

| be2-pe01-eqch2.as57976 4 | 347 | 335 | 53 | 120 | 4749 | 54 |

| chi-eqch2-ia-bons-02.as57976 4 | 338 | 325 | 55 | 146 | 4753 | 55 |

| 24.105.62.129 - 5 | 339 | 325 | 54 | 124 | 4750 | 55 |

|________________________________________________|______|______|______|______|______|______|

okay here it is, I hope I did this right. I logged into the game and almost immediately it started the latency problem. Got into a one on one against a pally and it froze up over and over until I finally died from lag.

Elocin-mugthol · July 7, 2019, 6:05pm

Your local device is responding a bit slow, so you’re hitting 352ms (occasionally) before you leave the building. Once you connect to the ISP, they’re losing a lot of your data across their network. Ultimately, you can make them aware of this, and even forward this test to them, and they may need to schedule an appointment with you. In the meantime, try rebooting that router/modem and see if it helps at all. If not, they may need to replace that, too.

Stephnrock-scilla · July 7, 2019, 6:08pm

There is also this ping test i did , pinging to Blizzard. com. You can see that it spikes to 3000+ at one time. It starts out fine, then out of the blue this lag issue starts. Everytime.
I have also pinged to Google. com. Havnt encountered a lag spike yet.
In the game the MS reading would have both world and home sky rocketing during the lag spikes.
So frustrating not gettng to play the one game i look forward too during my July 4th break. Just unreal this crap happens during my time off. But what do you do?

C:\Users\Bella>ping blizzard. com

Pinging blizzard
137.221.106.104] with 32 bytes of data:
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50
Reply from 137.221.106.104: bytes=32 time=81ms TTL=50

Ping statistics for 137.221.106.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 77ms, Maximum = 81ms, Average = 78ms

C:\Users\Bella>ping blizzard.
Pinging blizzard [137.221.106.104] with 32 bytes of data:
Reply from 137.221.106.104: bytes=32 time=80ms TTL=50
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50
Reply from 137.221.106.104: bytes=32 time=80ms TTL=50

Ping statistics for 137.221.106.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 77ms, Maximum = 80ms, Average = 78ms

C:\Users\Bella>ping blizzard.

Pinging blizzard [137.221.106.104] with 32 bytes of data:
Reply from 137.221.106.104: bytes=32 time=78ms TTL=50
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50

Ping statistics for 137.221.106.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 77ms, Maximum = 78ms, Average = 77ms

C:\Users\Bella>ping blizzard

Pinging blizzard. [137.221.106.104] with 32 bytes of data:
Reply from 137.221.106.104: bytes=32 time=78ms TTL=50
Reply from 137.221.106.104: bytes=32 time=78ms TTL=50
Request timed out.
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50

Ping statistics for 137.221.106.104:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 77ms, Maximum = 78ms, Average = 77ms

C:\Users\Bella>ping blizzard.
Pinging blizzard. [137.221.106.104] with 32 bytes of data:
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50

Ping statistics for 137.221.106.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 77ms, Maximum = 77ms, Average = 77ms

C:\Users\Bella>ping blizzard.

Pinging blizzard. [137.221.106.104] with 32 bytes of data:
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50

Ping statistics for 137.221.106.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 77ms, Maximum = 77ms, Average = 77ms

C:\Users\Bella>ping blizzard.
Pinging blizzard [137.221.106.104] with 32 bytes of data:
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50
Request timed out.
Reply from 137.221.106.104: bytes=32 time=78ms TTL=50
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50

Ping statistics for 137.221.106.104:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 77ms, Maximum = 78ms, Average = 77ms

C:\Users\Bella>ping blizzard.

Pinging blizzard [137.221.106.104] with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50

Ping statistics for 137.221.106.104:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 77ms, Maximum = 77ms, Average = 77ms

C:\Users\Bella>ping blizzard

Pinging blizzard [137.221.106.104] with 32 bytes of data:
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50
Reply from 137.221.106.104: bytes=32 time=78ms TTL=50
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50
Reply from 137.221.106.104: bytes=32 time=78ms TTL=50

Ping statistics for 137.221.106.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 77ms, Maximum = 78ms, Average = 77ms

C:\Users\Bella>ping blizzard.

Pinging blizzard [137.221.106.104] with 32 bytes of data:
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50

Ping statistics for 137.221.106.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 77ms, Maximum = 77ms, Average = 77ms

C:\Users\Bella>ping blizzard.
Pinging blizzard [137.221.106.104] with 32 bytes of data:
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50
Reply from 137.221.106.104: bytes=32 time=78ms TTL=50

Ping statistics for 137.221.106.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 77ms, Maximum = 78ms, Average = 77ms

C:\Users\Bella>ping blizzard

Pinging blizzard [137.221.106.104] with 32 bytes of data:
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50
Reply from 137.221.106.104: bytes=32 time=78ms TTL=50
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50

Ping statistics for 137.221.106.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 77ms, Maximum = 78ms, Average = 77ms

C:\Users\Bella>ping blizzard

Pinging blizzard[137.221.106.104] with 32 bytes of data:
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50
Reply from 137.221.106.104: bytes=32 time=78ms TTL=50
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50

Ping statistics for 137.221.106.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 77ms, Maximum = 78ms, Average = 77ms

C:\Users\Bella>ping blizzard

Pinging blizzard [137.221.106.104] with 32 bytes of data:
Reply from 137.221.106.104: bytes=32 time=78ms TTL=50
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50

Ping statistics for 137.221.106.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 77ms, Maximum = 78ms, Average = 77ms

C:\Users\Bella>ping blizzard

Pinging blizzard[137.221.106.104] with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50

Ping statistics for 137.221.106.104:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 77ms, Maximum = 77ms, Average = 77ms

C:\Users\Bella>ping blizzard

Pinging blizzard [137.221.106.104] with 32 bytes of data:
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50
Reply from 137.221.106.104: bytes=32 time=78ms TTL=50
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50

Ping statistics for 137.221.106.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 77ms, Maximum = 78ms, Average = 77ms

C:\Users\Bella>ping blizzard

Pinging blizzard [137.221.106.104] with 32 bytes of data:
Reply from 137.221.106.104: bytes=32 time=137ms TTL=50
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50
Reply from 137.221.106.104: bytes=32 time=78ms TTL=50
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50

Ping statistics for 137.221.106.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 77ms, Maximum = 137ms, Average = 92ms

C:\Users\Bella>ping blizzard

Pinging blizzard [137.221.106.104] with 32 bytes of data:
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50

Ping statistics for 137.221.106.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 77ms, Maximum = 77ms, Average = 77ms

C:\Users\Bella>ping blizzard

Pinging blizzard [137.221.106.104] with 32 bytes of data:
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50

Ping statistics for 137.221.106.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 77ms, Maximum = 77ms, Average = 77ms

C:\Users\Bella>ping blizzard

Pinging blizzard[137.221.106.104] with 32 bytes of data:
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50
Reply from 137.221.106.104: bytes=32 time=78ms TTL=50
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50

Ping statistics for 137.221.106.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 77ms, Maximum = 78ms, Average = 77ms

C:\Users\Bella>ping blizzard

Pinging blizzard [137.221.106.104] with 32 bytes of data:
Reply from 137.221.106.104: bytes=32 time=78ms TTL=50
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50

Ping statistics for 137.221.106.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 77ms, Maximum = 78ms, Average = 77ms

C:\Users\Bella>ping blizzard

Pinging blizzard [137.221.106.104] with 32 bytes of data:
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50
Reply from 137.221.106.104: bytes=32 time=78ms TTL=50
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50

Ping statistics for 137.221.106.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 77ms, Maximum = 78ms, Average = 77ms

C:\Users\Bella>ping blizzard

Pinging blizzard[137.221.106.104] with 32 bytes of data:
Reply from 137.221.106.104: bytes=32 time=284ms TTL=50
Reply from 137.221.106.104: bytes=32 time=78ms TTL=50
Reply from 137.221.106.104: bytes=32 time=78ms TTL=50
Reply from 137.221.106.104: bytes=32 time=78ms TTL=50

Ping statistics for 137.221.106.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 78ms, Maximum = 284ms, Average = 129ms

C:\Users\Bella>ping blizzard

Pinging blizzard [137.221.106.104] with 32 bytes of data:
Reply from 137.221.106.104: bytes=32 time=78ms TTL=50
Reply from 137.221.106.104: bytes=32 time=90ms TTL=50
Reply from 137.221.106.104: bytes=32 time=3727ms TTL=50
Request timed out.

Ping statistics for 137.221.106.104:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 78ms, Maximum = 3727ms, Average = 1298ms

C:\Users\Bella>ping blizzard

Pinging blizzard[137.221.106.104] with 32 bytes of data:
Reply from 137.221.106.104: bytes=32 time=78ms TTL=50
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50
Reply from 137.221.106.104: bytes=32 time=77ms TTL=50

Ping statistics for 137.221.106.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 77ms, Maximum = 78ms, Average = 77ms

C:\Users\Bella>ping blizzard

Elocin-mugthol · July 7, 2019, 6:14pm

Well, if you have access to another form of internet connection, like a mobile tether, you could see if the problem is specifically with your ISP. The route you take to Blizzard is different than the route to Google, but it’s also important to keep in mind that pings sometimes don’t catch packet loss when they are a short test. That’s why the WinMTR is so useful, because it’s an average over time.

Stephnrock-scilla · July 7, 2019, 6:14pm

Thank you Elocin. I do appreciate your input.
Ill do what you suggest. I do find it odd that other players are having the same issues as me, but maybe they have sheety AT&T DSL as I do lol.