Have been having issues with latency over the last month+ sometimes I goes as high as 1k+ but most of the time it randomly sits at 200-500ms then sometimes its fine.
Below logs I was sitting at around 97ms then dropped back down to my normal 24-27ms.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % |
Sent |
Recv |
Best |
Avrg |
Wrst |
Last |
| unifi - 1 |
793 |
788 |
0 |
0 |
28 |
0 |
| No response from host - 100 |
164 |
0 |
0 |
0 |
0 |
0 |
| ae210.2011.FTWSPAFW-MSE01-AA-IE1.verizon-gni.n et - 1 |
800 |
797 |
5 |
8 |
50 |
6 |
| No response from host - 100 |
164 |
0 |
0 |
0 |
0 |
0 |
| ae14.bar4.phi1.sp.lumen.tech - 43 |
307 |
178 |
0 |
9 |
32 |
8 |
| No response from host - 100 |
164 |
0 |
0 |
0 |
0 |
0 |
| BLIZZARD-EN.ear7.Chicago2.Level3.n et - 1 |
800 |
797 |
24 |
30 |
111 |
27 |
| No response from host - 100 |
164 |
0 |
0 |
0 |
0 |
0 |
| et-0-0-0-pe02-evch1.as57976.n et - 1 |
801 |
798 |
26 |
28 |
65 |
28 |
| 137.221.67.65 - 1 |
800 |
797 |
25 |
26 |
37 |
27 |
| No response from host - 100 |
164 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
164 |
0 |
0 |
0 |
0 |
0 |
| 37.244.2.174 - 1 |
800 |
797 |
24 |
26 |
37 |
27 |
| ________________________________________________ |
______ |
______ |
______ |
______ |
______ |
______ |
Blizzard no longer supports troubleshooting with WinMTR, which is why they discontinued the documentation/instructions for it.
However, I have many years of experience reading these. According to those logs, your highest response time was 37ms to the IP you pinged. The lines prior with higher values are irrelevant because those are nodes ignoring your ICMP requests (which is what WinMTR uses).
You’re either pinging the wrong IP (since we saw no pings above 37ms) or the issue is happening on the computer itself.
Edit: Blizzard doesn’t disclose the server IPs anymore, and the ones that were posted in the forum are no longer relevant. So, where did this IP come from?
1 Like
Used the below command and found IPs with an established connection on port one of these ports. 1119, 3724, 6112, 6113, or 6114.
netstat -an
Used one I found let WinMTR run while playing.
My goal is rule out if this is a blizzard issue or a Verizon FIOS issue. It only started a month ago.
Work in IT professional so good with troubleshooting just networking isn’t my strong suite. Have unifi hardware at home and no issues for other platforms when it comes to latency. Issue does occur on multiple devices for WoW however least when I tested last. Going to test again shortly.
You’re better off looking at the IP in task manager for the executable. I think you’re pinging an authentication server.
It is a realm IP as that and one other are the two IPs I see traffic on coming from wow.exe via TCPView from Sysinternals. Even see similar traffic from those IPs on my router.
37.244.2.174
66.40.178.52
I’ve ran winmtr on both and see similar results.
Well, then the behavior you’re seeing in game isn’t being caused by your connection route to the server. A worst ping of 37ms isn’t going to display as 500ms in the game. However, a hardware processing or thermal issue could cause delays in properly reading the latency.
1 Like