League of legends high latency

Hi I am having issues with my league of legends ping in game.  It used to be around 40 ping and that was fine, but now at peak hours 12pm to 2am my ping varies from 140 to 300+, after talking to riot support I wasn't able to get great detail on the core issue.  Time warner has sent multiple techs to try to fix the issue and even a complete re install didn't fix the latency spikes for long periods. (3-25% packet loss at times before re install)

Here are the tracert for the servers given by riot support.

192.64.170.252
1 <1 ms <1 ms <1 ms 192.168.2.1
2 <1 ms <1 ms <1 ms 192.168.0.1
3 26 ms 17 ms 13 ms cpe-66-69-0-1.satx.res.rr.com [66.69.0.1]
4 27 ms 30 ms 32 ms tge0-0-1.snaxtx4701h.texas.rr.com [24.28.135.9]

5 17 ms 10 ms 13 ms agg63.snantxvy01r.texas.rr.com [24.175.33.232]
6 22 ms 24 ms 23 ms agg23.dllatxl301r.texas.rr.com [24.175.32.146]
7 21 ms 31 ms 23 ms bu-ether14.dllstx976iw-bcr00.tbone.rr.com [66.10
9.6.88]
8 21 ms 20 ms 18 ms 0.ae2.pr1.dfw10.tbone.rr.com [107.14.17.236]
9 22 ms 25 ms 24 ms 24.27.236.233
10 71 ms 70 ms 68 ms 104.160.134.35
11 155 ms 152 ms 163 ms ae35-br02.chi01.riotdirect.net [104.160.159.24]

12 159 ms 170 ms 163 ms 104.160.131.36
13 150 ms 126 ms 161 ms 104.160.131.46
14 45 ms 44 ms 42 ms 104.160.131.101
15 * * * Request timed out.

Gyazo of MTR (no packet loss)

https://gyazo.com/84e0d790f38bc5d9e4ea1186eb54904d

 

104.160.131.1

 

Tracing route to 104.160.131.1 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.2.1
2 <1 ms <1 ms <1 ms 192.168.0.1
3 16 ms 15 ms 13 ms cpe-66-69-0-1.satx.res.rr.com [66.69.0.1]
4 41 ms 44 ms 57 ms tge0-0-1.snaxtx4701h.texas.rr.com [24.28.135.9]

5 16 ms 14 ms 13 ms agg63.snantxvy01r.texas.rr.com [24.175.33.232]
6 33 ms 31 ms 23 ms agg23.dllatxl301r.texas.rr.com [24.175.32.146]
7 29 ms 24 ms 22 ms bu-ether14.dllstx976iw-bcr00.tbone.rr.com [66.10
9.6.88]
8 25 ms 25 ms 20 ms 0.ae2.pr1.dfw10.tbone.rr.com [107.14.17.236]
9 21 ms 23 ms 20 ms 24.27.236.233
10 63 ms 63 ms 54 ms 104.160.134.35
11 370 ms 337 ms 328 ms ae35-br02.chi01.riotdirect.net [104.160.159.24]

12 149 ms 127 ms 104 ms ae1-br01.chi01.riotdirect.net [104.160.159.8]
13 197 ms 152 ms 177 ms 104.160.131.1

Trace complete.

https://gyazo.com/bda49f400f1ca58110f9e8f160af611f

 

Network Analysis
http://n2.netalyzr.icsi.berkeley.edu/summary/id=36a470be-15533-ec1b1990-5666-4472-98d9

 

46 REPLIES 46
Expert

Re: League of legends high latency

problem isn't TWC, it's these guys:

11 370 ms 337 ms 328 ms ae35-br02.chi01.riotdirect.net [104.160.159.24]

 

Re: League of legends high latency

This is the response I recieved from them

"If you're experiencing issues with your Router/modem, you'll need to make sure the router/modem is configured properly and can handle the bandwidth from the devices connected to it. As it seems you're still connected to the router and it's experiencing high latency and packet loss.

Your router may be experiencing excessive packet buffering. This can be problematic when your router or internet connection cannot handle all of the bandwidth and cause your connection to League of Legends to fail in various ways. Some third-party applications that can contribute to high buffering rates are Skype, P2P Applications such as uTorrent, Hamachi, and audio/video streams. Closing these applications may help reduce the strain on your network.

If your high latency continue to be a problem, you may need to speak with your Internet Service Provider on the type of router that would be appropriate for your connection and bandwidth limitations."

 

But I see what you are saying, there doesnt seem to be any issues with packet loss right now but the ping is still high and all the nodes before that one are good/great.  I'm just reluctant because of all the time warner issues I have had lately.

Helper

Re: League of legends high latency

Yeah, it looks like THEIR server is having issues, those are great times on your side.
Spectrum Employee

Re: League of legends high latency

MsRaye and jhf5 are telling it truly, this is their server or ISP having the issue on their end, not a problem with your internet.

 

In fact I did a little digging of my own:

Your forward / downstream signals are doing excellent, not a single packet lost.  0% correcteds, 0% uncorrecteds.

Spoiler
Frequency Modulation TX SNR
37.00 MhzATDMA  34 dBmv  40.4 dB
24.20 MhzATDMA  34 dBmv  35.1 dB
30.60 MhzATDMA  34 dBmv  36.1 dB
19.40 MhzTDMA  32.5 dBmv  37.4 dB
Downstream16 Frequency Modulation RX SNR
567.00 MhzQAM256  5.9 dBmv  38.9 dB
537.00 MhzQAM256  5.9 dBmv  39.1 dB
543.00 MhzQAM256  5.9 dBmv  39.1 dB
549.00 MhzQAM256  6.2 dBmv  39.3 dB
555.00 MhzQAM256  6.1 dBmv  39.2 dB
561.00 MhzQAM256  6.1 dBmv  39.2 dB
531.00 MhzQAM256  6.3 dBmv  39.3 dB
573.00 MhzQAM256  5.3 dBmv  38.6 dB
579.00 MhzQAM256  5.2 dBmv  38.5 dB
585.00 MhzQAM256  4.5 dBmv  37.9 dB
591.00 MhzQAM256  4.1 dBmv  37.5 dB
597.00 MhzQAM256  3.9 dBmv  37.4 dB
603.00 MhzQAM256  4.1 dBmv  37.5 dB
609.00 MhzQAM256  4.7 dBmv  38.1 dB
615.00 MhzQAM256  5.3 dBmv  38.6 dB
621.00 MhzQAM256  5.6 dBmv  38.8 dB

Your ustream / return signal is also nearly flawless.  0% uncorrectables (packet loss), and the corrected your are having are 2 specific frequencies which may be caused by an ingress leak (from what I can tell, it's actually on of your neighbor's "noisy" equipment, which isn't something you can control).

Spoiler
Logical Upstream Channel 9/2.1/0 (24.20 Mhz)
Corrected errors 3.2454%

Logical Upstream Channel 9/2.2/0 (30.60 Mhz)
Corrected errors 1.1450%

Higher correcteds with no uncorrectables (like this case) on the upstream signal, this means that your neighborhood node is getting some garbled/static/interference with that signal coming back from your modem (and that of your neighbors).  This wouldn't account for the extreme latency in-game you're seeing, and about 1% correcteds isn't great but it's not noticable either.  You local node is correcting all of those errors on-the-fly.

If that had been uncorrecteds however (garble so bad that data packet are actually lost), I would be more concerned, and saying a field tech should probably be sent ot check it out and try to find out which neighbor is the source of the issue.  But in this case, that shouldn't even be noticable.

So... yeah... the underlying root cause, the primary issue here is the server MyRaye pointed out.

As far as the noisy neighbor's modem, the best thing I can suggest from a fine-tuning part is just to make sure you don't have any ghosting being caused in your own home by making sure you have all "hot"/active coax jacks terminated.  (PS: here's a classroom lecture style video about "why")



 

 

My postings on this site are my own, off-the-clock, and don’t necessarily represent TWC’s/Charter's strategies or opinions.
Expert

Re: League of legends high latency

Contact LOL and tell them this is their side of the transport carrier at

11 370 ms 337 ms 328 ms ae35-br02.chi01.riotdirect.net [104.160.159.24]

12 149 ms 127 ms 104 ms ae1-br01.chi01.riotdirect.net [104.160.159.8]
13 197 ms 152 ms 177 ms 104.160.131.1

 

104.160.159.24 IP address Information

The IP address 104.160.159.24 was found in Santa Monica, California, United States. It is allocated to Riot Games. Additional IP location information, as well as network tools are available below.

IP address:104.160.159.24
hostname:ae35-br02.chi01.riotdirect.net
ISP:Riot Games
City:Santa Monica
Region:California
Country:United States (US) flag
Postal code:90404
Area code:310

And here is their contact info:

OrgNOCHandle: NOC12528-ARIN
OrgNOCName:   Noc
OrgNOCPhone:  +1-626-252-8774 
OrgNOCEmail:  noc@riotgames.com
OrgNOCRef:    https://whois.arin.net/rest/poc/NOC12528-ARIN

OrgTechHandle: NETWO5012-ARIN
OrgTechName:   Network Engineering
OrgTechPhone:  +1-424-431-1111 
OrgTechEmail:  peering@riotgames.com
OrgTechRef:    https://whois.arin.net/rest/poc/NETWO5012-ARIN

 Here is my tracert to them, i'm in Ohio and it is good...

 

Tracing route to 104.160.131.1 over a maximum of 30 hops

1 2 ms <1 ms <1 ms DD-WRT [192.168.6.6]
2 1 ms <1 ms <1 ms 192.168.1.1
3 18 ms 9 ms 9 ms 142.254.157.117
4 24 ms 21 ms 21 ms 24.164.114.189
5 11 ms 11 ms 10 ms be20.clhgohcc01r.midwest.rr.com [24.33.103.58]
6 11 ms 15 ms 16 ms be14.clevohek02r.midwest.rr.com [65.29.1.98]
7 11 ms 12 ms 11 ms be25.clevohek01r.midwest.rr.com [65.29.1.32]
8 23 ms 23 ms 23 ms 0.ae3.pr1.lax00.tbone.rr.com [107.14.17.254]
9 27 ms 31 ms 32 ms bu-ether12.nwrknjmd67w-bcr00.tbone.rr.com [66.109.6.29]
10 27 ms 31 ms 24 ms bu-ether12.nycmny837aw-bcr00.tbone.rr.com [66.109.6.27]
11 24 ms 33 ms 23 ms ae-1-0.c1.buf00.tbone.rr.com [66.109.1.57]
12 24 ms 24 ms 24 ms 24.27.236.129
13 24 ms 24 ms 24 ms 104.160.132.35
14 34 ms 34 ms 32 ms ae31-br01.chi01.riotdirect.net [104.160.159.14]

15 33 ms 34 ms 33 ms 104.160.131.1

Trace complete.

C:\Documents and Settings\HP_Administrator>

Re: League of legends high latency

https://gyazo.com/9f647bb078654455e63ecfff4c2cc232

This is the respone I recived back with new tracers


| 192.168.2.1 - 0 | 821 | 821 | 0 | 0 | 2 | 0 |
| 192.168.0.1 - 0 | 821 | 821 | 0 | 0 | 62 | 0 |
| cpe-66-69-0-1.satx.res.rr.com - 1 | 817 | 816 | 5 | 22 | 141 | 18 |
| tge0-0-1.snaxtx4701h.texas.rr.com - 0 | 821 | 821 | 13 | 52 | 382 | 28 |
| agg63.snantxvy01r.texas.rr.com - 1 | 817 | 816 | 6 | 23 | 142 | 23 |
| agg23.dllatxl301r.texas.rr.com - 0 | 821 | 821 | 15 | 33 | 150 | 26 |
|bu-ether14.dllstx976iw-bcr00.tbone.rr.com - 0 | 821 | 821 | 15 | 33 | 112 | 31 |
| 0.ae2.pr1.dfw10.tbone.rr.com - 0 | 821 | 821 | 13 | 32 | 148 | 22 |
| 24.27.236.233 - 0 | 821 | 821 | 11 | 30 | 152 | 19 |
| 104.160.134.35 - 0 | 821 | 821 | 39 | 132 | 301 | 67 |
| ae35-br02.chi01.riotdirect.net - 0 | 821 | 821 | 34 | 133 | 340 | 169 |
| 104.160.131.36 - 0 | 821 | 821 | 121 | 248 | 429 | 322 |
| 104.160.131.46 - 1 | 817 | 816 | 34 | 155 | 407 | 328 |
| 104.160.131.103 - 0 | 821 | 821 | 32 | 51 | 169 | 42 |

 

 

 

192.168.2.1 - 0 | 1363 | 1363 | 0 | 0 | 4 | 0 |
| 192.168.0.1 - 0 | 1362 | 1362 | 0 | 0 | 53 | 0 |
| cpe-66-69-0-1.satx.res.rr.com - 0 | 1362 | 1362 | 5 | 23 | 163 | 12 |
| tge0-0-1.snaxtx4701h.texas.rr.com - 0 | 1362 | 1362 | 13 | 52 | 394 | 33 |
| agg63.snantxvy01r.texas.rr.com - 0 | 1362 | 1362 | 5 | 23 | 155 | 13 |
| agg23.dllatxl301r.texas.rr.com - 1 | 1358 | 1357 | 13 | 33 | 166 | 20 |
|bu-ether14.dllstx976iw-bcr00.tbone.rr.com - 1 | 1358 | 1357 | 16 | 34 | 168 | 18 |
| 0.ae2.pr1.dfw10.tbone.rr.com - 1 | 1354 | 1352 | 11 | 32 | 162 | 25 |
| 24.27.236.233 - 0 | 1362 | 1362 | 13 | 30 | 166 | 17 |
| 104.160.134.35 - 0 | 1362 | 1362 | 40 | 155 | 376 | 77 |
| ae35-br02.chi01.riotdirect.net - 0 | 1362 | 1362 | 45 | 160 | 332 | 142 |
| ae1-br01.chi01.riotdirect.net - 0 | 1362 | 1362 | 69 | 190 | 393 | 167 |
| 104.160.131.1 - 2 | 1307 | 1293 | 46 | 169 | 370 | 254 |

Newcomer

Re: League of legends high latency

Hey guys!

 

We use ICMP rate limiting on our devices to protect the control plane of our routers.  I can assure you that while it looks like there may be a problem there (higher ping times) it's just the rate limiting and the router CPU restriction that shows the higher ping time.  There's nothing going on with our connection at that hop or the devices.

 

Riot Laslow

Valued Contributor

Re: League of legends high latency

Trace from Kentucky

 

Tracing route to 104.160.131.1 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  router.asus.com [192.168.1.1]
  2     8 ms     8 ms     8 ms  142.254.154.61
  3     8 ms     7 ms    10 ms  be62.smrtkyen01h.midwest.rr.com [74.128.5.121]
  4    15 ms    20 ms    14 ms  tge0-10-0-10.rcmdkyat01r.midwest.rr.com [65.29.29.162]
  5    33 ms    28 ms    39 ms  be26.clevohek01r.midwest.rr.com [65.189.140.170]
  6    35 ms    35 ms    35 ms  bu-ether27.vinnva0510w-bcr00.tbone.rr.com [107.14.19.14]
  7    47 ms    47 ms    55 ms  bu-ether12.nwrknjmd67w-bcr00.tbone.rr.com [66.109.6.29]
  8    40 ms    47 ms    47 ms  bu-ether12.nycmny837aw-bcr00.tbone.rr.com [66.109.6.27]
  9    40 ms    39 ms    40 ms  0.ae1.pr1.nyc20.tbone.rr.com [107.14.17.218]
 10    40 ms    41 ms    40 ms  24.27.236.129
 11    40 ms    50 ms    40 ms  104.160.132.35
 12    41 ms    41 ms    42 ms  ae31-br01.chi01.riotdirect.net [104.160.159.14]
 13    44 ms    44 ms    43 ms  104.160.131.1

Trace complete.

Highlighted
Not applicable

Re: League of legends high latency

I've been having the very same issue for about a month now and it is very frustrating! My situation is extremely similar to yours, with my ping being ridiculously high during peak hours, around 5PM to midnight.

 

I have been back and forth with Riot Support and they insist that it is my ISP having issues at a certain hop, and I don't know what to do anymore. There have been multiple announced server maintenances from both LOL and multiple internet issues in my area in the past month that have since been corrected on both ends from both companies, so I have no idea what to do.

 

I will try and post a tracert when peak hours hit and my ping becomes bad again.