Hi everyone, I've had two games now which suffered SEVERE lag. The kind where the champion stops obeying commands, and Skype still works.
I've noticed a pattern where only Canadian players get this. I queued with 3 other Canadians and 1 American and only the Canadians experienced this issue (all at once). The other team had one Canadian who experienced the issue.
Apparently HotshotGG has been getting this issue.
I'm wondering if anyone can explain it or is sharing a similar lag issue (Canadian or not).
Edit: Some recent steps suggested by a Wrenchman!
everyone that would be willing do the following it could be helpful
Open a command prompt, win 7 click start and type cmd, xp click run and type cmd.
type in the following command
tracert 126.96.36.199 > c:\trace.txt
Attach the trace.txt to a post after it finishes running. it may take 5 minutes. You can go to https://support.leagueoflegends.com/...r-ip-addresses and do this with any of the IP addresses, it will overwrite the file each time you run it.
file output should be SIMILAR, but not the same to what is below
Tracing route to 188.8.131.52 over a maximum of 30 hops
1 9 ms 9 ms 10 ms 10.200.176.1
2 7 ms 8 ms 10 ms interface-74-214-233-33.etv.net [184.108.40.206]
3 20 ms 25 ms 25 ms interface-74-214-233-149.etv.net [220.127.116.11]
4 15 ms 10 ms 11 ms interface-74-214-233-10.etv.net [18.104.22.168]
5 12 ms 14 ms 15 ms ge-7-45.car1.SaltLakeCity1.Level3.net [22.214.171.124]
6 28 ms 26 ms 36 ms ae-7-7.ebr1.LosAngeles1.Level3.net [126.96.36.199]
7 23 ms 23 ms 23 ms ae-71-71.csw2.LosAngeles1.Level3.net [188.8.131.52]
8 25 ms 25 ms 24 ms ae-2-70.edge1.LosAngeles9.Level3.net [184.108.40.206]
9 69 ms 212 ms 55 ms gblx-level3-xe.LosAngeles9.Level3.net [220.127.116.11]
10 27 ms 26 ms 26 ms INTERNAP.te1-4.ar4.LAX1.gblx.net [18.104.22.168]
11 25 ms 24 ms 25 ms border1.po1-20g-bbnet1.lax010.pnap.net [22.214.171.124]
12 27 ms 25 ms 25 ms 126.96.36.199
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
the request time outs are normal. Its how the system responds when the router provider makes it so the IP cannot be pinged.
my theory has changed a bit as not all of you are going through the same location.... back to the drawing board.
amazing how much shaw jumps around.. something isnt right as it goes from one side of the continent to the other in a single hop.