Been experiencing high latency for no reason the past couple of days. It is especially bad in warsong gulch. I created new Interface, Cache, and WTF folders. I flushed ipconfig and dns.
Would it be an ISP side issue? All other devices in the house stream fine, it only seems to be my computer (with or without other devices turned on) AND im hooked up via ethernet
I’d also like to add that I’ve been experiencing memory issues. WoW crashed once due to “memory problems” and frequently when I load the game backgrounds/borders take time to load – which does resolve. Not sure if the problems are related
5% packet loss often shows up as disconnections, and the 3000+ms latency spikes aren’t helping. They continue throughout the entire test, which means that your first isp hop is setting the tone for your entire connection.
Other internet apps can buffer. Wow can’t. So these sorts of things have more of an impact in wow.
Thanks guys. I contacted my ISP today, they’re acting like everything on their side is fine. The guy i’m talking to doesn’t seem to know what hes talking about, even after me explaining that I’m having packet loss and latency issues.
My girlfriend did move our TV (and amazon prime box) which was hooked up to an Ethernet adapter and is now connected over wifi. Would that affect it ?
The most I got out of the tech guy was that I should replace my ethernet cable as it might be the culprit. Any suggestions ?
That’s where you politely but firmly ask for your case to be escalated.
You could power cycle all of your network equipment. That could resolve it. But, it really looks like the issue is the ISP’s equipment outside your network.
I guess I’m calling them back. I’ve power cycled my modem multiple times. Even when out today and bought a brand new cat-6 Ethernet cable, still no improvement…frustrating.
They have gotten me to check my ping/bandwith on speedtest. net multiple times, then run tracerp in CMD. Technician is insisting its a WoW server side problem.
Tracing route to worldofwarcraft. com [34.202.253.206]
over a maximum of 30 hops:
1 6 ms 1 ms 3 ms 192.168.0.1
2 * 14 ms 19 ms 192-0-202-65.cpe.teksavvy. com [192.0.202.65]
3 * * 26 ms kitchener.rcable-tsi.tor.teksavvy. com [104.195.128.70]
4 51 ms 38 ms 40 ms kitchener.tsi-rcable.tor.teksavvy. com [104.195.128.69]
5 26 ms 18 ms 29 ms ae2-0-bdr01-tor2.teksavvy. com [206.248.155.17]
6 35 ms 25 ms 65 ms ae12-0-bdr01-tor.teksavvy. com [206.248.155.10]
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
2nd run :
Tracing route to worldofwarcraft.com [34.202.253.206]
over a maximum of 30 hops:
1 2 ms 2 ms 5 ms 192.168.0.1
2 143 ms 122 ms 103 ms 192-0-202-65.cpe.teksavvy. com [192.0.202.65]
3 113 ms 114 ms 118 ms kitchener.rcable-tsi.tor.teksavvy. com [104.195.128.70]
4 109 ms 120 ms 121 ms kitchener.tsi-rcable.tor.teksavvy. com [104.195.128.69]
5 146 ms 127 ms 131 ms ae2-0-bdr01-tor2.teksavvy. com [206.248.155.17]
6 128 ms 117 ms 147 ms ae12-0-bdr01-tor.teksavvy. com [206.248.155.10]
7 * * * Request timed out.
8 * * * Request timed out.
UPDATE: I told the tech rep about speaking with you guys and the proposed culprit of 192-0-202-65.cpe.teksavvy. com - 5 . She said that that address is actually my home modem, and if I’m receiving the high of packet loss/ping then the equipment probably needs to be replaced.
I hope Technical Support could fix these problem. I also got higher latency almost 3000 ms. After I delete the addon and restart my WoW, sometimes still 3000 ms but now it turns normal again at 200 ms this evening.
For anyone interested. The 6th tech rep I talked to said that my RF was out about .9. They sent a rogers technician to my house and he fixed a broken cable aswell as re-calibrated the distance between my modem and the cable box. All is working now
Glad to hear that the technician was able to find the issue and get you all fixed up. Going to go ahead and lock this thread since it’s been resolved.
