Gaming Lag

@Carl Frederickson

If it's just the game server you're having trouble with the connection to it might not necessarily be the Internet connection that's causing problems. If you could get some trace routes to the server in question we can look for any problems there.

Thanks. How do I do that? I don't think that it is just the game server as in Colorado I had no lag whatsoever. And once I restart my modem (at the start of every game) it's fine.

Thanks,

Traceroute has started…

traceroute to 104.160.131.1 (104.160.131.1), 64 hops max, 72 byte packets

 1  192.168.0.1 (192.168.0.1)  2.598 ms  1.062 ms  5.818 ms

 2  10.39.0.1 (10.39.0.1)  14.017 ms  8.065 ms  8.045 ms

 3  100.127.73.184 (100.127.73.184)  9.930 ms  8.377 ms  9.666 ms

 4  70.169.73.90 (70.169.73.90)  7.796 ms  7.554 ms  7.989 ms

 5  68.1.4.252 (68.1.4.252)  20.537 ms  20.727 ms  31.190 ms

 6  72.215.224.162 (72.215.224.162)  20.356 ms  22.713 ms  21.660 ms

 7  104.160.133.35 (104.160.133.35)  22.695 ms  21.986 ms  21.603 ms

 8  104.160.159.100 (104.160.159.100)  45.670 ms  46.017 ms  45.827 ms

 9  ae34-br01.chi01.riotdirect.net (104.160.159.22)  62.577 ms  63.915 ms  65.122 ms

10  104.160.131.1 (104.160.131.1)  65.325 ms  64.645 ms  65.697 ms

@Carl Frederickson

Based on those results you've obtained I'm thinking it's the Internet connection causing the issues you're seeing. The latency does increase a bit once your connection reaches Riot's network but I don't think that is really a problem. I'd suggest reaching out to their support to see if they have any suggestions as to what could be happening.

Additional tests below. I ran Riot's (video game company) server tracer test and these are the two traceroutes based on the servers it pinged back...

Traceroute has started…

traceroute to 216.133.234.62 (216.133.234.62), 64 hops max, 72 byte packets

 1  192.168.0.1 (192.168.0.1)  516.766 ms  1022.908 ms  1023.072 ms

 2  10.39.0.1 (10.39.0.1)  921.519 ms  1004.927 ms  1041.771 ms

 3  100.127.73.186 (100.127.73.186)  928.223 ms  1014.356 ms  1010.649 ms

 4  70.169.73.196 (70.169.73.196)  1059.570 ms  1036.012 ms  1022.433 ms

 5  68.1.4.252 (68.1.4.252)  941.878 ms  1021.836 ms  1012.068 ms

 6  be-204-pe02.600wseventh.ca.ibone.comcast.net (173.167.57.109)  959.567 ms  997.975 ms  137.467 ms

 7  hu-0-5-0-0-cr02.losangeles.ca.ibone.comcast.net (68.86.83.17)  39.063 ms  679.798 ms  1008.149 ms

 8  be-11599-pe01.losangeles.ca.ibone.comcast.net (68.86.84.194)  1001.107 ms  1016.700 ms  1030.996 ms

 9  96-87-8-74-static.hfc.comcastbusiness.net (96.87.8.74)  940.083 ms  1024.065 ms  1023.028 ms

10  border2.po2-40g-bbnet2.lax010.pnap.net (216.52.255.93)  21.809 ms  25.064 ms  21.263 ms

11  * * *

12  * * *

13  * * *

14  * * *

15  * * *

16  * * *

17  * * *

18  * * *

19  * * *

20  * * *

21  * * *

22  * * *

23  * * *

and

Traceroute has started…

traceroute to 192.64.170.62 (192.64.170.62), 64 hops max, 72 byte packets

 1  192.168.0.1 (192.168.0.1)  3.170 ms  1.078 ms  0.971 ms

 2  10.39.0.1 (10.39.0.1)  8.647 ms  9.589 ms  9.734 ms

 3  100.127.73.184 (100.127.73.184)  10.203 ms  10.266 ms  8.493 ms

 4  70.169.73.90 (70.169.73.90)  9.252 ms  10.906 ms  9.703 ms

 5  chgobprj01-ae0.0.rd.ch.cox.net (68.1.4.42)  53.318 ms  52.694 ms  53.622 ms

 6  ip70-167-150-114.at.at.cox.net (70.167.150.114)  60.826 ms  59.328 ms  59.650 ms

 7  104.160.131.46 (104.160.131.46)  58.099 ms  59.143 ms  59.520 ms

 8  104.160.131.103 (104.160.131.103)  60.056 ms  60.657 ms  62.705 ms

 9  * * *

10  *

Hello Chris,

If you think it is the internet connection that is causing the issues can you explain why I should reach out to Riot for assistance?

Thank you for your help.

@Carl Frederickson

It appears I mis-typed. I actually meant to say I don't think it's the Internet connection that's the issue here. Riot may have a few suggestions to troubleshoot this further. If you've consistently observed the problem going away after a device reset it's possible the device itself is contributing to the problem.

Thank you Chris. I am lagging at ~500ms at the start of every game. Once it begins I can restart my router and after the 2 minutes of restart and reconnect the MS reduces to 65-75ms which is what I am used to in Arizona. I have done this/re-created this 10 times over the last 3 days. The router/modem is brand new as of March/April.

Thanks,

@Carl Frederickson

It's entirely possible there's something about the traffic between Riot and the game you're playing is causing an issue with the router using if resetting the router works. Even if it is new that doesn't necessary mean it's not free of problems of some kind.
This would be another good reason to reach out to them for further guidance. The cause and effect you're describing appears to rule out the Internet as being a contributor.

Ever resolve your issue? I am having same problem with blizzard games. Lag spikes about every 30-45 seconds.