Rookie

High Ping to League of Legends from LA

Usually my ping to the Riot servers in Chicago runs about 65-70ms. On Friday this jumped to 115-135 which makes the game unplayable. It's consistently high, this isn't a spike.

Tracing seems to show a problem in one hop (bu-ether26) ?

 

 1  unknown [192.168.1.1]
  2  142.254.183.177
  3  agg59.vnnzca2402h.socal.rr.com [76.167.27.85]
  4  72.129.14.86
  5  agg29.tustcaft01r.socal.rr.com [72.129.13.2]
  6  bu-ether26.tustca4200w-bcr00.tbone.rr.com [66.109.3.232]
  7  bu-ether14.lsancarc0yw-bcr00.tbone.rr.com [66.109.6.4]
  8  0.ae0.pr1.lax00.tbone.rr.com [107.14.17.248]
  9  24.27.236.127
 10  104.160.133.35
 11  104.160.152.225
 12  104.160.159.100
 13  ae34-br01.chi01.riotdirect.net [104.160.159.22]
 14  104.160.131.1
Computing statistics for 350 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           Amethyst [192.168.1.51]
                                0/ 100 =  0%   |
  1    1ms     0/ 100 =  0%     0/ 100 =  0%  unknown [192.168.1.1]
                                0/ 100 =  0%   |
  2   16ms     0/ 100 =  0%     0/ 100 =  0%  142.254.183.177
                                0/ 100 =  0%   |
  3   15ms     0/ 100 =  0%     0/ 100 =  0%  agg59.vnnzca2402h.socal.rr.com [76.167.27.85]
                                0/ 100 =  0%   |
  4   17ms     0/ 100 =  0%     0/ 100 =  0%  72.129.14.86
                                0/ 100 =  0%   |
  5   18ms     0/ 100 =  0%     0/ 100 =  0%  agg29.tustcaft01r.socal.rr.com [72.129.13.2]
                                0/ 100 =  0%   |
  6   19ms     0/ 100 =  0%     0/ 100 =  0%  bu-ether26.tustca4200w-bcr00.tbone.rr.com [66.109.3.232]
                                0/ 100 =  0%   |
  7   68ms     0/ 100 =  0%     0/ 100 =  0%  bu-ether14.lsancarc0yw-bcr00.tbone.rr.com [66.109.6.4]
                                0/ 100 =  0%   |
  8   65ms     0/ 100 =  0%     0/ 100 =  0%  0.ae0.pr1.lax00.tbone.rr.com [107.14.17.248]
                                0/ 100 =  0%   |
  9   62ms     2/ 100 =  2%     2/ 100 =  2%  24.27.236.127
                                0/ 100 =  0%   |
 10   64ms     0/ 100 =  0%     0/ 100 =  0%  104.160.133.35
                                0/ 100 =  0%   |
 11   70ms     0/ 100 =  0%     0/ 100 =  0%  104.160.152.225
                                2/ 100 =  2%   |
 12  ---     100/ 100 =100%    98/ 100 = 98%  104.160.159.100
                                0/ 100 =  0%   |
 13  ---     100/ 100 =100%    98/ 100 = 98%  ae34-br01.chi01.riotdirect.net [104.160.159.22]
                                0/ 100 =  0%   |
 14  111ms     2/ 100 =  2%     0/ 100 =  0%  104.160.131.1
Trace complete.
2 REPLIES 2
Highlighted
Sharer

Re: High Ping to League of Legends from LA

Actually, it generally looks good until you hit congestion coming into Riot in the Midwest (104.160.xxx.xxx IP's). Only showed 2 dropped packets at the last hop where it hands off of Spectrum's networks. Those two hops showing 98% are likely set to not respond to ICMP Echo, doesn't prove they are good or bad either way. May simply be overloads on their end of the route, or the servers themselves bogging down.
Proven Sharer

Re: High Ping to League of Legends from LA

Most gamers don't understand that Spectrum has NO geographic or load-based route selection.  They only have a handful of IXP (handoff) locations across the entire country.  Each is located in a major metro area and connects to just one specific contracted 3rd party internet provider.  Therefore each of these can be a location where backlogs occur during times of high internet use.

ALL internet traffic from this Spectrum subscriber in SoCal exits Spectrum's transport near LA, then hops on an external transport network to make the long trip to Chicago, and eventually will arrive at the Riot server site.  It does NOT remain inside Spectrum all the way to their Chicago Midwest IXP contractor (which is presently Level 3)!