I am attempting to play World of Warcraft, same as I have been for the past 11 days since this was installed. Randomly, my latency will jump from its usual 100 ms to 300 ms or higher - my highest so far since the issues started was nearly 3k ms. In addition, I am experiencing a lot of hanging issues in-game.
I do not blame Comcast entirely for the issues I am having - it seems a lot of people have been having issues since a game patch done recently - but some of my issues are definitely because of packet loss and server issues between my router and the game server.
I am running Windows 8.1. The router we were given is the Arris TG852. I am running on WiFi.
My game latency at the beginning of the traceroute was over 2k ms. My game latency at the beginning of the pathping, run just after the traceroute completed, had dropped to 352 ms; during the pathping, it jumped up to nearly 1k ms.
Traceroute:
Tracing route to mdf1-bi8k-1-ve-87.phx1.attens.net [63.241.138.161]
over a maximum of 30 hops:
1 * 2 ms 1 ms 10.0.0.1
2 879 ms 971 ms 364 ms 174.54.88.1
3 15 ms 52 ms 11 ms te-1-2-ur01.waynesboro.pa.pitt.comcast.net [68.85.43.193]
4 14 ms 15 ms 19 ms te-0-13-0-9-ar03.lowerpaxton.pa.pitt.comcast.net [68.85.52.133]
5 22 ms 27 ms 23 ms pos-0-2-0-0-ar03.pittsburgh.pa.pitt.comcast.net [68.85.52.158]
6 35 ms 31 ms 32 ms he-4-14-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.94.185]
7 * * * Request timed out.
8 51 ms 32 ms 35 ms 192.205.37.33
9 100 ms 99 ms 100 ms cr2.n54ny.ip.att.net [12.122.130.110]
10 99 ms 100 ms 101 ms cr2.wswdc.ip.att.net [12.122.3.38]
11 239 ms 832 ms 1109 ms cr1.attga.ip.att.net [12.122.1.173]
12 105 ms 444 ms 99 ms cr2.dlstx.ip.att.net [12.122.28.174]
13 223 ms 122 ms 103 ms cr1.dlstx.ip.att.net [12.122.1.209]
14 107 ms 101 ms 100 ms cr1.phmaz.ip.att.net [12.122.28.182]
15 102 ms 329 ms 274 ms 12.123.158.5
16 428 ms 106 ms 113 ms 12-122-254-218.attens.net [12.122.254.218]
17 99 ms 102 ms 101 ms mdf002c7613r0002-gig-12-1.phx1.attens.net [63.241.130.202]
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
Pathping:
Tracing route to mdf1-bi8k-1-ve-87.phx1.attens.net [63.241.138.161]
over a maximum of 30 hops:
0 Raiukage.hsd1.pa.comcast.net. [10.0.0.3]
1 10.0.0.1
2 174.54.88.1
3 te-1-2-ur01.waynesboro.pa.pitt.comcast.net [68.85.43.193]
4 te-0-13-0-9-ar03.lowerpaxton.pa.pitt.comcast.net [68.85.52.133]
5 pos-0-2-0-0-ar03.pittsburgh.pa.pitt.comcast.net [68.85.52.158]
6 he-4-14-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.94.185]
7 * * *
Computing statistics for 150 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Raiukage.hsd1.pa.comcast.net. [10.0.0.3]
22/ 100 = 22% |
1 405ms 22/ 100 = 22% 0/ 100 = 0% 10.0.0.1
3/ 100 = 3% |
2 401ms 28/ 100 = 28% 3/ 100 = 3% 174.54.88.1
0/ 100 = 0% |
3 391ms 27/ 100 = 27% 2/ 100 = 2% te-1-2-ur01.waynesboro.pa.pitt.comcast.net [68.85.43.193]
0/ 100 = 0% |
4 375ms 27/ 100 = 27% 2/ 100 = 2% te-0-13-0-9-ar03.lowerpaxton.pa.pitt.comcast.net [68.85.52.133]
0/ 100 = 0% |
5 446ms 25/ 100 = 25% 0/ 100 = 0% pos-0-2-0-0-ar03.pittsburgh.pa.pitt.comcast.net [68.85.52.158]
1/ 100 = 1% |
6 393ms 26/ 100 = 26% 0/ 100 = 0% he-4-14-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.94.185]
Trace complete.
How can this be remedied without needing to do a direct connection to the router? (I asked for a wireless router to get rid of the need for wires! The last thing I want is to be stuck on the living room couch holding a laptop whenever I want to play.)