Im also getting random Lag spikes on WoW Classic, Whitemane. It’s fine for a few minutes then up to 4000ms for a minute, and the cycle repeats.
Tracing route to 137.221.105.2 over a maximum of 30 hops
1 7 ms 7 ms 6 ms 192.168.1.1
2 15 ms 15 ms 15 ms 68.144.0.1
3 * 15 ms 14 ms rc3no-be151-1.cg.shawcable(dot)net [64.59.132.61]
4 30 ms 30 ms 30 ms rc2wt-be100.wa.shawcable(dot)net [66.163.75.233]
5 30 ms 30 ms 30 ms rc6wt-tge0-10-0-11.wa.shawcable(dot)net [66.163.68.70]
6 65 ms 65 ms 66 ms ae1-br01-eqse2.as57976(dot)net [137.221.73.33]
7 67 ms 69 ms 63 ms xe-0-0-0-1-br01-eqsv5.as57976(dot)net [137.221.65.40]
8 66 ms 65 ms 63 ms et-0-0-29-br02-eqsv5.as57976(dot)net [137.221.65.117]
9 142 ms 65 ms 62 ms xe-0-0-1-1-br02-eqla1.as57976(dot)net [137.221.65.6]
10 218 ms 254 ms 227 ms et-0-0-29-br01-eqla1.as57976(dot)net [137.221.65.0]
11 * * * Request timed out.
12 62 ms 70 ms 63 ms et-0-0-0-pe03-swlv10.as57976(dot)net [137.221.83.85]
13 63 ms 64 ms 64 ms 137.221.105.2
Trace complete.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
Host - % |
Sent |
Recv |
Best |
Avrg |
Wrst |
Last |
192.168.1.1 - 0 |
273 |
273 |
7 |
20 |
347 |
9 |
68.144.0.1 - 2 |
254 |
249 |
14 |
30 |
620 |
21 |
rc3no-be151-1.cg.shawcable(dot) - 4 |
241 |
233 |
12 |
33 |
368 |
17 |
rc2wt-be100.wa.shawcable(dot) net - 5 |
234 |
224 |
30 |
50 |
625 |
41 |
rc6wt-tge0-10-0-11.wa.shawcable(dot) net - 5 |
234 |
224 |
29 |
53 |
635 |
40 |
ae1-br02-eqse2.as57976(dot) net - 13 |
181 |
158 |
60 |
85 |
489 |
65 |
xe-0-0-1-1-br02-eqch2.as57976(dot) net - 7 |
218 |
204 |
63 |
101 |
866 |
86 |
et-0-0-1-pe03-eqch2.as57976(dot) net - 12 |
185 |
163 |
61 |
87 |
544 |
65 |
24.105.62.129 - 5 |
230 |
219 |
63 |
82 |
673 |
88 |
________________________________________________ |
______ |
______ |
______ |
______ |
______ |
______ |
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Hey there,
It looks like the router is having a bit of trouble. The latency is spiking up to 347 often enough to push the average latency up to 20. For perspective that 20 average latency is one third of the total time it takes for the trip to make its way across the country!
I also noticed that there is a 2% packet loss on the node after the router which may be another private device like a modem/router. This loss is made significantly worse by the already unstable latency. The signal appears to degrade further down the line.
If both of those devices are within your home, try doing an extended power cycle by unplugging them for 30+ minutes before plugging them back in. If they are connected wirelessly trying a wired connection directly to the modem may be recommended to help verify if the problem is related to the wireless network.
I do hope the information helps. Let us know how things go with power cycling those devices.