Pretty much everyone from South America and some Europe countries are suffering of big lag spikes. This is not related to a game problem but just a network problem. Prolly a router somewhere, droping packets. First thing u need to do is a traceroute so u identify all the points u pass through to connect to USKO. Type this in a DOS command prompt:
It's a K2 router. This will give u an output similar to this:Code:tracert -d 220.127.116.11
Each ip is a hop. Next step is open as many DOS command prompt windows as IPs u got from the traceroute, and type a "ping -t <ip>". So for this example u will have to open 12 windows, 1 per each 'ping -t'Code:C:>tracert -d 18.104.22.168 Tracing route to 22.214.171.124 over a maximum of 30 hops *1 * * * * * * ** * * * ** * * Request timed out. *2 * * 6 ms * * 6 ms * *10 ms *192.168.1.250 *3 * * 8 ms * * 8 ms * * 7 ms *172.20.0.58 *4 * * 8 ms * * 8 ms * *12 ms *126.96.36.199 *5 * * 8 ms * * 8 ms * * 7 ms *188.8.131.52 *6 * *88 ms * *69 ms * *72 ms *184.108.40.206 *7 * *71 ms * *70 ms * *71 ms *220.127.116.11 *8 * *98 ms * *97 ms * *98 ms *18.104.22.168 *9 * *99 ms * 101 ms * 108 ms *22.214.171.124 10 * 143 ms * 143 ms * 144 ms *126.96.36.199 11 * 146 ms * 143 ms * 143 ms *188.8.131.52 12 * 148 ms * 142 ms * 142 ms *184.108.40.206
The last IPs are the closest to K2 and the most important to monitor since these ones are common to more ppl and prolly where the problem is. Then just play the game. As soon as u get a lag spike, ALT+TAB and check your ping windows. U will start to get errors like this:Code:ping -t 220.127.116.11 ping -t 18.104.22.168 ping -t 22.214.171.124 ping -t 126.96.36.199 etc.
This means, your communication with K2 router had a timeout which caused the lag spike. Check all windows backwards, starting with the last IP and see which one was the first that had that same "Request timed out" error. In my case, I found that 188.8.131.52 was ok but 184.108.40.206 started with the Request timeouts and everything after that, so 220.127.116.11 is the one causing the problems. That IP belongs to:Code:Reply from 18.104.22.168: bytes=32 time=229ms TTL=242 Request timed out. Reply from 22.214.171.124: bytes=32 time=229ms TTL=242
IP Address: 126.96.36.199
Location: Los Angeles (33.972N, 118.250W)
With this info, K2 can talk to their ISP and get this sorted out. If u guys wanna help troubleshoot this problem, u should do the same and see what u get.