Consistent increased latency issues when connecting to Riot Games servers returning issue.

[Bdor]

Between approximately February to March this issue disappeared, but now it has returned.

When connecting to Riot Games servers whether for League of Legends or Valorant, instead of getting a stable 23ms latency, I get either a stable 37ms latency or a stable 50ms latency -- however these latencies usually actually feel like its more than the number that's being shown.

**Labels Added**

[JBeach]

I am also having this issue and support has done nothing to help.

Can you do a traceroute to riots server by typing "tracert 104.160.131.1" in cmd, then post the results. I find the issue is with a Rogers server in the last hop before it connects to Riots server.

[sharpenel]

Not the original poster, however I'm also having latency issues with Riot/League of Legends. Stable 30-50 ms using CloudFlare DNS servers, which will spike to 100-180 ms infrequently. 

Tracing route to 104.160.131.1 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 192.168.50.1
2 19 ms 17 ms 15 ms 99.247.72.1
3 17 ms 15 ms 16 ms 24.156.142.169
4 24 ms 16 ms 17 ms so-5-1-1.gw02.mtnk.phub.net.cable.rogers.com [24.153.4.134]
5 18 ms 17 ms 16 ms 9404-cgw01.ym.rmgt.net.rogers.com [209.148.233.90]
6 41 ms 42 ms 46 ms 209.148.237.21
7 54 ms 53 ms 53 ms eqix-ch2.chi01.riotdirect.net [208.115.136.235]
8 95 ms 92 ms 95 ms ae1.er02.chi01.riotdirect.net [104.160.143.91]
9 94 ms 94 ms 100 ms ae2.er02.lax01.riotdirect.net [104.160.159.186]
10 100 ms 92 ms 103 ms ae1.er01.lax01.riotdirect.net [104.160.151.134]
11 98 ms 85 ms 91 ms 104.160.131.1

Trace complete.

[Twendelboe]

I have had a ticket in for over a week. From what I gather, It won't be fixed. Switch ISPs to Fibre or even ADSL if fibre isn't available. 

Rogers cable (or a reseller) is literally my only choice and I am excited for the continued rollout of a local fibre option. 

For the time being, I currently take my zoom calls via Telus cellphone and limit gaming to mostly single player.