The past 3-4 days the game has been incredibly Jumpy, to the point where im constantly spamming my resync button to even move around town. Ive done all the steps in the support thread, but no improvement so far. C:\Users\Coy>tracert login.uorenaissance.com Tracing route to login.uorenaissance.com [76.74.249.219] over a maximum of 30 hops: 1 1 ms <1 ms 1 ms 192.168.0.1 2 9 ms 8 ms 7 ms 96.120.15.121 3 8 ms 9 ms 11 ms te-8-4-ur01.oldgetwell.tn.malt.comcast.net [68.8 5.55.41] 4 9 ms 10 ms 11 ms te-0-10-0-0-ar02.winchester.tn.malt.comcast.net [68.86.240.21] 5 22 ms 21 ms 21 ms be-22258-cr02.56marietta.ga.ibone.comcast.net [6 8.86.90.37] 6 29 ms 31 ms 32 ms be-11314-cr01.dallas.tx.ibone.comcast.net [68.86 .85.21] 7 31 ms 30 ms 30 ms he-0-11-0-0-pe03.1950stemmons.tx.ibone.comcast.n et [68.86.86.174] 8 31 ms 29 ms 29 ms 173.167.58.14 9 * * * Request timed out. 10 * * * Request timed out. 11 42 ms 38 ms 37 ms 76.74.249.219 Trace complete. C:\Users\Coy>tracert login.uorenaissance.com Tracing route to login.uorenaissance.com [76.74.249.219] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.0.1 2 10 ms 10 ms 12 ms 96.120.15.121 3 9 ms 9 ms 9 ms te-8-4-ur01.oldgetwell.tn.malt.comcast.net [68.8 5.55.41] 4 11 ms 13 ms 9 ms te-0-10-0-0-ar02.winchester.tn.malt.comcast.net [68.86.240.21] 5 22 ms 22 ms 20 ms be-22258-cr02.56marietta.ga.ibone.comcast.net [6 8.86.90.37] 6 32 ms 32 ms 34 ms be-11314-cr01.dallas.tx.ibone.comcast.net [68.86 .85.21] 7 28 ms 30 ms 28 ms he-0-11-0-0-pe03.1950stemmons.tx.ibone.comcast.n et [68.86.86.174] 8 28 ms 29 ms 28 ms 173.167.58.14 9 * * * Request timed out. 10 * * * Request timed out. 11 38 ms 44 ms 37 ms 76.74.249.219 Trace complete. C:\Users\Coy>ping 64.125.31.86 -t Pinging 64.125.31.86 with 32 bytes of data: Reply from 64.125.31.86: bytes=32 time=18ms TTL=56 Reply from 64.125.31.86: bytes=32 time=22ms TTL=56 Reply from 64.125.31.86: bytes=32 time=20ms TTL=56 Reply from 64.125.31.86: bytes=32 time=24ms TTL=56 Reply from 64.125.31.86: bytes=32 time=21ms TTL=56 Reply from 64.125.31.86: bytes=32 time=19ms TTL=56 Reply from 64.125.31.86: bytes=32 time=22ms TTL=56 Reply from 64.125.31.86: bytes=32 time=48ms TTL=56 Reply from 64.125.31.86: bytes=32 time=46ms TTL=56 Reply from 64.125.31.86: bytes=32 time=134ms TTL=56 Reply from 64.125.31.86: bytes=32 time=23ms TTL=56 Reply from 64.125.31.86: bytes=32 time=29ms TTL=56 Reply from 64.125.31.86: bytes=32 time=65ms TTL=56 Reply from 64.125.31.86: bytes=32 time=40ms TTL=56 Reply from 64.125.31.86: bytes=32 time=27ms TTL=56 Reply from 64.125.31.86: bytes=32 time=19ms TTL=56 Reply from 64.125.31.86: bytes=32 time=51ms TTL=56 Reply from 64.125.31.86: bytes=32 time=18ms TTL=56 Reply from 64.125.31.86: bytes=32 time=33ms TTL=56 Reply from 64.125.31.86: bytes=32 time=22ms TTL=56 Reply from 64.125.31.86: bytes=32 time=34ms TTL=56 Reply from 64.125.31.86: bytes=32 time=53ms TTL=56 Reply from 64.125.31.86: bytes=32 time=68ms TTL=56 Reply from 64.125.31.86: bytes=32 time=24ms TTL=56 Reply from 64.125.31.86: bytes=32 time=38ms TTL=56 Reply from 64.125.31.86: bytes=32 time=34ms TTL=56 Reply from 64.125.31.86: bytes=32 time=20ms TTL=56 Reply from 64.125.31.86: bytes=32 time=20ms TTL=56 Reply from 64.125.31.86: bytes=32 time=19ms TTL=56 Reply from 64.125.31.86: bytes=32 time=56ms TTL=56 Reply from 64.125.31.86: bytes=32 time=364ms TTL=56 Ping statistics for 64.125.31.86: Packets: Sent = 31, Received = 31, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 18ms, Maximum = 364ms, Average = 46ms Control-C ^C C:\Users\Coy>
I've basically got the same ping problem as you. It's constantly spiking up to 300-400 for some reason. I've tried other games, counter-strike, TF2 and my pings there are 100% smooth. What I've done is use this WTFast program to take off those huge spikes. But to be honest that WTFast program is a pain, I don't wanna pay for it and I've not been playing much lately.
