For the past month or so, I peak up to high latency at around 9pm EST, lasting 60-90 mins or so. Some nights its just a few lag spike freezes, and some nights the game is not playable.
It’s always the same hop with high ping on my pathping. Looks to be a blizzard node? I need help since I can’t raid like this much longer.
Right-click on the downloaded .zip folder and select “Extract All”, to extract the files to a new folder.
Open the new folder that was created, then open the WinMTR_x32 folder.
Right-click on the WinMTR application and select “Run as administrator”.
Type the IP address 137.221.105.2 in the “Host” field.
Click on “Start” and then launch the game. Allow the test to run for at least 10 minutes. Click on “Stop” when you’re done playing after you have experienced the latency or connection issue.
Click on “Copy Text to Clipboard”, paste the results here, then highlight everything and hit the </> button in the posting section so it will allow links.
I recently transferred to Tichondrius and found my “normal” latency to be higher. About 70ms or so. Back on BurningLegion it was 50ms. I consider high latency anything above 100ms. But these nightly increases jump up to as high as 500ms. And it is characterized by 2-3 second freezing spikes rather than static latency in my abilities.
This doesnt look good. I am on wifi, but i havent had issues with it in 3 years. I guess I should try an ethernet cable if I can get one long enough
Burning Legion is a US Central realm, while Tichondrius is a US West realm. It’s possible your ISP just has better routing to the Central servers, which could explain the jump from 50ms to 70ms.
I’d definitely recommend trying a wired connection to the router if possible. That’s the best way to rule out if the latency spikes up to 500ms are related to the wifi or not.
The packet loss in the WinMTR looks to be all over the place, so it’s hard to say what is actual loss and not just those routers ignoring the test packets. The last hop does show 0% loss which is a good sign. Hopefully the wired connection will help out, and if it does then you can look at troubleshooting the wifi itself once you’ve narrowed it down.
How did it feel in-game when this last WinMTR was run? Any spikes up to 500ms?
The first hop looks about the same, so it’s possible there’s an issue with the router although it’s hard to say for sure. The packet loss after the router looks a bit better.
If you’re still feeling the issues in-game though it may be worth reaching out to the ISP to see if they can look for any signal issues or problems with the router that might be causing it. Might also be worth having them swap the router out with a new device, if it’s one that you lease from them.
I did this WinMTR during off-peak hours and my in-game issues are only noticeable during peak hours. Also note this is connected directly to my modem, not using the router.
I am going to reach out to the ISP since it seems possible this is a hardware issue. Let me know if you have any other suggestions though
I’m having the exact same issue, in the exact same time frame, on the same ISP and at the same port. Though I’m on US-Sargeras. It’s really hurting our raid prog. I can start a new thread but I figured I’d chime in on this that it might not be a hardware issue if we’re both experiencing the exact same thing. I’ve had my MS spike to 2k+ in game world only while all other internet is smooth.
Normally my MS sits comfortably on this server between 20-30 world and home so this has been insane the past week or so.
For context, nothing on my setup (software or hardware) has changed since this issue started, and I’ve been raiding consistently with minimal to no issues at the same time frame for months so this is very strange.
I’m trying to do a Ny’alotha run, home ms is 75 (about average), and world ms is 1270, literally happens every time I come in here for the past 2-3 weeks.
For about 2-3 weeks, at peak times 8-9, completely unplayable. Happens during the raids mostly, and in PvP but not at the same extent. No issues basically before that. Same provider and I think the same area.
TRACEROUTE:
traceroute to 185.242.5.150 (185.242.5.150), 15 hops max, 60 byte packets
1 Blizzard Blizzard 1.860 ms 1.864 ms 1.867 ms
2 24.105.18.130 (24.105.18.130) 3.263 ms 3.286 ms 3.291 ms
3 137.221.105.14 (137.221.105.14) 3.293 ms 3.296 ms 3.298 ms
4 137.221.66.18 (137.221.66.18) 3.795 ms 3.808 ms 3.810 ms
5 137.221.83.82 (137.221.83.82) 275.639 ms 275.644 ms 275.647 ms
6 * * *
7 137.221.68.32 (137.221.68.32) 6.004 ms 6.134 ms 6.126 ms
8 4-1-3.ear3.LosAngeles1.Level3.ne (4.71.135.105) 5.488 ms 5.607 ms 5.601 ms
9 ae-28.r00.lsanca07.us.bb.gin.ntt.ne (129.250.9.93) 6.060 ms 5.975 ms 6.095 ms
10 ae-2.r23.lsanca07.us.bb.gin.ntt.ne (129.250.3.237) 5.693 ms 5.805 ms 5.818 ms
11 ae-5.r01.lsanca20.us.bb.gin.ntt.ne (129.250.6.49) 6.506 ms 6.632 ms 6.646 ms
12 ce-0-1-0-0.r01.lsanca20.us.ce.gin.ntt.ne (128.241.6.1) 6.085 ms 5.813 ms 5.668 ms
Deleted the T in .net
But essentially the same routing/issues as the others here.
Not trying to be a snooty, but it seems like an issue with the routing to a Blizzard server, talked to a networking friend and he suggested its not on my (our) ends.
^^^ Thats me, Zul’Jin is my server, forgot to mention that. The trace was the wrong one, forgot I was testing it with my VPN, although the same cluster of servers seem to be an issue. (.com removed) It gets much worse around 830-9.
1 Blizzard Blizzard 0.476 ms 0.441 ms 0.440 ms
2 24.105.18.2 (24.105.18.2) 0.585 ms 0.632 ms 0.681 ms
3 137.221.105.10 (137.221.105.10) 0.729 ms 0.740 ms 0.777 ms
4 137.221.66.16 (137.221.66.16) 0.495 ms 0.513 ms 0.527 ms
5 137.221.83.80 (137.221.83.80) 294.166 ms 294.183 ms 294.195 ms
6 * * *
7 137.221.69.32 (137.221.69.32) 38.170 ms 38.613 ms 38.663 ms
8 eqix-ch1-ix.teksavvy (208.115.136.65) 49.513 ms 49.867 ms 49.851 ms
9 ae8-0-bdr01-tor2.teksavvy (206.248.155.9) 60.859 ms 66.642 ms 66.640 ms
10 ae3-0-agg01-tor2.teksavvy (206.248.155.93) 58.998 ms 58.881 ms 58.885 ms
11 richmond_road-ottawa.rcable-tsi.tor2.teksavvy (104.195.129.2) 48.468 ms 48.417 ms 48.548 ms
12 * * *
13 * * *
14 * * *
15 * * *
The downstream looks fine from the LookingGlass test. Could you try this winMTR instead to check the upstream? It should look similar to the one posted by Alarael.
On that note, I do need to mention that the problem in Alarael’s winMTR appears here:
Basically some data is being lost in transit between the game client and game servers. This causes the game to have to wait and re-send/receive the same data which may result in an increased display for latency in-game. The in-game display measures how long the game waits on data, so if it has to redo stuff it will make the number higher regardless of what the actual latency is.
I have the same problem. We’re in the same area in Ottawa. M+ is impossible for me to play as I lag out all the time. I called TekSavvy and they’re idiots and won’t acknowledge the problem or provide any solution. I don’t know what else to do stop playing WoW all together.
This is happening again tonight (first time on since last Weds at peak), though it feels not as drastic yet. Started spiking at 9:20pm EDT. Currently 46/680.