Yeah I have been running on wired connection and here are the three WinMTR test that Riot Support had me run and an additional screenshot of how they explained it to me.
I hope i hid the right info.
Edit: Bigger Pictures
I have been having super high ping spikes with consistent high ping in League of Legends. I used to be at 30 - 35 ping before but now I m consistently getting 50 with ping spikes of around 200 - 300. I contacted Rogers Support and everything on my end seems to be working good. Then I contacted Riot Support and I was told that they have been getting a lot of reports of high ping from players on a rogers connection. I did a bunch of WinMTR tests which the riot support asked me to do and assured me that the issue is on rogers end. Who do i need to contact for this issue to be resolved?
Riot support is correct, because I have been getting the same problem as well. I used to be averaging a ping of 29ms, but now I am consistently getting a ping of 50ms. There could definitely be a problem on Rogers' end because my modem stats are all in-spec and I am always getting a consistent speed test result for my internet plan. For reference take a look at my tracert to one of the Riot's servers. The IP I am pinging is 220.127.116.11.
3 11 ms 8 ms 7 ms 8082-dgw02.mtnk.rmgt.net.rogers.com [18.104.22.168]
4 19 ms 18 ms 7 ms 3000-dgw01.mtnk.rmgt.net.rogers.com [22.214.171.124]
5 11 ms 10 ms 8 ms 126.96.36.199
6 11 ms 16 ms 19 ms 9404-cgw01.ym.rmgt.net.rogers.com [188.8.131.52]
7 54 ms 54 ms 51 ms 184.108.40.206
8 52 ms 49 ms 47 ms 220.127.116.11
9 49 ms 44 ms 46 ms 18.104.22.168
10 50 ms 49 ms 52 ms 22.214.171.124
There could be a peering issue between Rogers' servers and Riot's servers because if you look at nodes 6 and 7, the ping increases suddenly from 11ms to 54ms. Not sure why this is happening, but if you can foward this to the department responsible for server routing that would be great.
EDIT: The IP I am using to trace my route to the Riot Games server is from https://support.riotgames.com/hc/en-us/articles/201752674-Network-System-and-League-of-Legends-Logs. If you scroll down to the "TRACERT" drop down menu, it gives the IP is given to the North American server, which is what we are connecting to.
Thanks so much for the testing results .
Would it be possible to provide me with a traceroute using command prompt? Though WinMTR can be useful there's been notable discrepancy with results versus actual latency. This could be related to a timing issue but that wouldn't be a concern with command prompt. If the results through CMD though are consistent with your results in WinMTR showing latency impact on any hop outside of the Rogers network this can be tracked for you and with time could be resolved. Should the latency be visible within the Rogers network though I can track that and have it resolved for you relatively quickly.
If you do have any other questions though definitely let me know!
Sorry about the late response but the Riot Servers were super busy and I wasnt able to ping them
But here it is
Tracing route to 126.96.36.199 over a maximum of 30 hops
1 1 ms 1 ms 1 ms hitronhub.home [192.168.0.1]
2 16 ms 16 ms 170 ms My IP
3 6 ms 12 ms 141 ms 8082-dgw01.hnsn.rmgt.net.rogers.com [188.8.131.52]
4 17 ms 13 ms 14 ms 184.108.40.206
5 20 ms 17 ms 150 ms 9404-cgw01.ym.rmgt.net.rogers.com [220.127.116.11]
6 23 ms 27 ms 18 ms 18.104.22.168
7 100 ms 100 ms 106 ms 22.214.171.124
8 24 ms 27 ms 186 ms 126.96.36.199
9 23 ms 29 ms 21 ms 188.8.131.52
10 39 ms 34 ms 176 ms 184.108.40.206
Here is an image for better readability.
I pinged the same ip mentioned in
Thanks so much, so there definitely looks to be latency occurring within the Rogers network there. At this time I'd like you to send us a PM @CommunityHelps so I can look into this further for you. I'll have the ability to run the traceroute directly from your modem to validate the results. If that checks out a ticket can be escalated for you to our network team.
No worries, I'll get to the bottom of this for ya.
f you're not familiar with our PMing process, you can find instructions here.