Riot Games - League of Legends issues

[Bekadin]

Hi, lately I've been getting annoying packet drops in League of Legends, that creates lag-like issues in game. If you've played League of Legends you know what I am talking about. To those who don't play the game here is the clip [https://www.youtube.com/watch?v=2VDEh40xYis](ignore the sound.) 

Anyways, I've contacted the Riot support and they told me to run couple of tests. I did few, and one of them was tracert test. I did that as well, and Riot Support guy told me this " From the tracers it is evident that your ISP is dropping the ball, if you look at the 2nd tracer you can see the specific point where the connection fails ( hop 6 ) which is your ISP's server." 

Here is the Second Tracer: 

Tracing route to 192.64.170.62 over a maximum of 30 hops

1 1 ms <1 ms <1 ms 192.168.1.1
2 6 ms 9 ms 8 ms L100.BSTNMA-VFTTP-160.verizon-gni.net [96.237.193.1]
3 14 ms 12 ms 19 ms G0-3-3-1.BSTNMA-LCR-21.verizon-gni.net [130.81.177.12]
4 13 ms 8 ms 29 ms ae1-0.BOS-BB-RTR1.verizon-gni.net [130.81.151.60]
5 18 ms 19 ms 19 ms 0.ae11.XL3.NYC1.ALTER.NET [152.63.20.69]
6 * * * Request timed out.
7 23 ms 21 ms 16 ms 0.ae2.BR2.NYC4.ALTER.NET [140.222.229.93]
8 21 ms 19 ms 22 ms 204.255.168.26
9 38 ms 18 ms 41 ms ae8.cr1.lga5.us.above.net [64.125.26.161]
10 49 ms 37 ms 39 ms ae6.cr1.ord2.us.above.net [64.125.24.34]
11 119 ms 87 ms 154 ms ae2.mpr1.sea1.us.above.net [64.125.20.69]
12 88 ms 87 ms 79 ms ae8.mpr1.pdx1.us.above.net [64.125.30.26]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
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.

After that, I contacted Verizon support, I told him/her the issue and she/he told me that I am gonna get disconnected from the internet because they gonna do something from their end. I waited, i got disconnected and I am stil getting the issues. 

The tracert above was run on : May 17 12:00. 

Here is new tracert test to same server. 

Tracing route to 192.64.170.62 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 14 ms 8 ms 10 ms L100.BSTNMA-VFTTP-160.verizon-gni.net [96.237.19
3.1]
3 14 ms 11 ms 7 ms G0-3-3-1.BSTNMA-LCR-21.verizon-gni.net [130.81.1
77.12]
4 110 ms 28 ms 64 ms ae1-0.BOS-BB-RTR1.verizon-gni.net [130.81.151.60
]
5 16 ms 21 ms 18 ms 0.ae11.XL3.NYC1.ALTER.NET [152.63.20.69]
6 * * * Request timed out.
7 * * * Request timed out.
8 18 ms 19 ms 20 ms 204.255.168.26
9 * * 21 ms ae8.cr1.lga5.us.above.net [64.125.26.161]
10 44 ms 39 ms 49 ms ae6.cr1.ord2.us.above.net [64.125.24.34]
11 78 ms 84 ms 82 ms ae2.mpr1.sea1.us.above.net [64.125.20.69]
12 78 ms 78 ms 78 ms ae8.mpr1.pdx1.us.above.net [64.125.30.26]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
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.

Please help. 

Thanks! 

PS: Forgot to add, I have wired connection. 

[Telcoguru]

Hop 6 is not your trouble. It just does not respond to being pinged. It looks like your trouble is us.above.net.

[Hubrisnxs]

Telecoguru is correct.

The guy from the Game Support forum doesn't know how to look at traceroutes.   Surprisingly A LOT OF TECH SUPPORT PEOPLE and even IT people don't know how to properly look at traceroutes. 

real common mistake he made.   But Above.net is your problem child.

Consider getting a high performing VPN service to bypass that router, or route.

5 best VPNs for gaming | Best VPN.com

I use Cyberghost but I don't game, so I don't know how they rate for gamers.

[Hubrisnxs]

just to give you a little amunition when talking to their tech support.

Ask them to reconcile this traceroute against their previous conclusion.

The following traceroute is from Chi-town to RiOT in LA.   No Verizon Hops no verizon provider, but it fails with teh same Above.net provider, who is probably Riot's Internet Provider. 

Traceroute to 192.64.170.62 (192.64.170.62), 20 hops max
-	CA APM Cloud Monitor Checkpoint
2	dr6506b.ord02.singlehop.net (99.198.126.193) 0.590 ms
3	xe-1-2-0.er2.ord2.us.above.net (64.124.200.141) 0.826 ms
4	ae15.cr2.ord2.us.above.net (64.125.24.149) 0.835 ms
5	ae11.cr1.ord2.us.above.net (64.125.20.245) 0.826 ms
6	ae2.mpr1.sea1.us.above.net (64.125.20.69) 40.796 ms
7	ae8.mpr1.pdx1.us.above.net (64.125.30.26) 43.791 ms
8	*
9	*
10	*
11	*
12	*
13	*
14	*
15	*
16	*
17	*
18	*
19	*
20	*
Number of hops exceeded

[Bekadin]

Ok, expect this VPN thing, how to fix this? What i have to do? Is IT only VPN issue?? THey told me that it was verizon was dropping the ball cuz i am getting packet drops..... 

[Hubrisnxs]

Nowhere in that trace route shows packets being dropped by verizon.

You have two choices.

1. Re-escalate to them and show them my traceroute and say if it's verizon then how does the very same thing happen to someone not on verizon.  

OR

2.  Get a vpn, and use that.   It's Riot's ISP that is the problem, not your ISP

[Bekadin]

Intersting, Riot support guy said it was my ISP dropping the ball becasue I was loosing them packets.. Now you guys telling me that it's Riots ISP? Love the ping pong action. 

[Hubrisnxs]

Proof's in the pudding.

 🙂

[Telcoguru]

You are not dropping packets. You have high latency to us.above.net.

[LawrenceC]

As this thread is now over two years old, it will be locked in order to keep discussions current. If you have the same or a similar question/issue we invite you to start a new thread on the topic.