Rogers Community

Richard_D · ‎11-22-2024

Hey there, I'm trying to see something here. Ever since roughly 2020, I've had somewhat inconsistent ping while playing League of Legends and Valorant. I have historically played at 22-27ms stable. Out of seemingly nowhere, I want to say late 2019-early 2020 i noticed my ping being a bit unusual, sometimes it would jump by 10-20 and i thought it was just things fluctuating from time to time. Fast forward some months, and it became a constant. I went from stable 22-27 (feeling smooth) to anywhere between 40-55ms in league specifically.

I contacted both Riot and Rogers (Several times), and both pointed me to the other. Frankly, playing felt horrible. My ping may have been "only" 45 but you could feel a stark difference in character response, it was bad. I've had countless technicians arrive, each time telling me my signal to the modem was low, or that there was nothing wrong.

I've done every troubleshooting task they've given me to do. Tracerts, DNS flushes, Modem resets, different cables, upgrading to Ignite with the PROMISE it would fix my issue. Nothing has changed since.

I have effectively stopped playing league of legends due to this as it was difficult to remain accurate with my movement AND with my abilities. For those of you who know League, I peaked Diamond 4 100LP in 2019. At the time, that was roughly the top 1-2% of the bracket. I've been gaming competitively for a long time now and I've grown accustomed to feeling changes in response times, and I know when something is off. This is not the inane rambling of someone who blames their ISP at first issue because they died a single time to some minor lag spike.

I returned to play a few matches the other day and sure enough, upon utilizing their built in Log Reader, my average latency was 48.89ms. This was the same for every match I played and it feels like utter garbage.

I found solace in other games, and for some reason Valorant was seemingly immune to this ping difference, which was even more confusing. But now here i am again, because the same thing is suddenly happening to Valorant as well. I used to play with 17ms, i am now at 36. What's going on here?

For four years now I've been in a back and forth of nothing happening I've checked some online forums and i feel like I'm seeing more and more threads of similar problems as if it's now some sweeping plague of ping increases.

If you're seeing this thread it's likely because you're investigating your own issues, so finally here i am with the question.

Are you guys having this too?
Does my issue sound annoyingly familiar?
How long (4-5 years for me) has it been happening and how many technicians (I'm beyond 10 at this point) have arrived to tell you the signal is low?
How many times have you had your modem swapped(2-3)?
What games have you spotted this in? (First league, then Valorant, and now Counterstrike as well).
What was your before/after ping?
Are you as frustrated as I am?

If yes, please leave a comment here giving some details of your woes so hopefully it can be known it's just not a one-off situation and maybe they'll be able to escalate it a bit higher.

As a final note, I do appreciate the Rogers team and the resident experts/advisors, I see you're trying to help and it's a wonderful beacon of light trying to get some direction. At the end of the day I'm just paying too much to see another "I can understand how frustrating it is to deal with latency issues." response and have another non-rogers subcontractor come out, just to waste each others time.

RogersTony · ‎11-24-2024

Hello,

We definitely want to help you investigate the latency issues you are facing.

We'll need some specific tests to see where the latency is occurring. Please provide us with a ping test and traceroute. You can find the steps here: https://communityforums.rogers.com/t5/Internet/Troubleshooting-Latency-Wired-Devices/ta-p/462951

We look forward to reviewing your results.

RogersTony

Richard_D · 2 weeks ago

Hey there, apologies for the late response. Thank you for reaching out. As I've mentioned in this initial post, my issue related to a sudden increase in ping to the same server locations I've always played on. This thread (VALORANT ping issues (Illinois) - Rogers Community) and the comments within are the effectively the exact same scenario, just in my case in particular it includes League of Legends, AND Valorant, both riot games.

As for the data, I've run 2 ping tests and a 3 tracert's to www.google.com. Results are below.

Riot support's Valorant section for troubleshooting provides IP's to use for North America. My results will be at the very bottom. "How to Use Tracert to Obtain Network Logs – VALORANT Support"

PING TEST 1____________________________________________________________________________

C:\Users\Rich>ping -n 50 www.google.com

Pinging www.google.com [2607:f8b0:400b:80c::2004] with 32 bytes of data:
Reply from 2607:f8b0:400b:80c::2004: time=13ms
Reply from 2607:f8b0:400b:80c::2004: time=12ms
Reply from 2607:f8b0:400b:80c::2004: time=18ms
Reply from 2607:f8b0:400b:80c::2004: time=9ms
Reply from 2607:f8b0:400b:80c::2004: time=13ms
Reply from 2607:f8b0:400b:80c::2004: time=13ms
Reply from 2607:f8b0:400b:80c::2004: time=10ms
Reply from 2607:f8b0:400b:80c::2004: time=14ms
Reply from 2607:f8b0:400b:80c::2004: time=13ms
Reply from 2607:f8b0:400b:80c::2004: time=12ms
Reply from 2607:f8b0:400b:80c::2004: time=14ms
Reply from 2607:f8b0:400b:80c::2004: time=11ms
Reply from 2607:f8b0:400b:80c::2004: time=15ms
Reply from 2607:f8b0:400b:80c::2004: time=11ms
Reply from 2607:f8b0:400b:80c::2004: time=11ms
Reply from 2607:f8b0:400b:80c::2004: time=12ms
Reply from 2607:f8b0:400b:80c::2004: time=20ms
Reply from 2607:f8b0:400b:80c::2004: time=12ms
Reply from 2607:f8b0:400b:80c::2004: time=11ms
Reply from 2607:f8b0:400b:80c::2004: time=10ms
Reply from 2607:f8b0:400b:80c::2004: time=11ms
Reply from 2607:f8b0:400b:80c::2004: time=13ms
Reply from 2607:f8b0:400b:80c::2004: time=18ms
Reply from 2607:f8b0:400b:80c::2004: time=12ms
Reply from 2607:f8b0:400b:80c::2004: time=13ms
Reply from 2607:f8b0:400b:80c::2004: time=13ms
Reply from 2607:f8b0:400b:80c::2004: time=12ms
Reply from 2607:f8b0:400b:80c::2004: time=12ms
Reply from 2607:f8b0:400b:80c::2004: time=12ms
Reply from 2607:f8b0:400b:80c::2004: time=15ms
Reply from 2607:f8b0:400b:80c::2004: time=10ms
Reply from 2607:f8b0:400b:80c::2004: time=11ms
Reply from 2607:f8b0:400b:80c::2004: time=13ms
Reply from 2607:f8b0:400b:80c::2004: time=12ms
Reply from 2607:f8b0:400b:80c::2004: time=12ms
Reply from 2607:f8b0:400b:80c::2004: time=10ms
Reply from 2607:f8b0:400b:80c::2004: time=13ms
Reply from 2607:f8b0:400b:80c::2004: time=15ms
Reply from 2607:f8b0:400b:80c::2004: time=12ms
Reply from 2607:f8b0:400b:80c::2004: time=12ms
Reply from 2607:f8b0:400b:80c::2004: time=29ms
Reply from 2607:f8b0:400b:80c::2004: time=12ms
Reply from 2607:f8b0:400b:80c::2004: time=11ms
Reply from 2607:f8b0:400b:80c::2004: time=10ms
Reply from 2607:f8b0:400b:80c::2004: time=9ms
Reply from 2607:f8b0:400b:80c::2004: time=11ms
Reply from 2607:f8b0:400b:80c::2004: time=17ms
Reply from 2607:f8b0:400b:80c::2004: time=10ms
Reply from 2607:f8b0:400b:80c::2004: time=10ms
Reply from 2607:f8b0:400b:80c::2004: time=10ms

Ping statistics for 2607:f8b0:400b:80c::2004:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 29ms, Average = 12ms

PING TEST 2____________________________________________________________________________

C:\Users\Rich>ping -n 50 www.google.com

Pinging www.google.com [2607:f8b0:400b:807::2004] with 32 bytes of data:
Reply from 2607:f8b0:400b:807::2004: time=12ms
Reply from 2607:f8b0:400b:807::2004: time=12ms
Reply from 2607:f8b0:400b:807::2004: time=12ms
Reply from 2607:f8b0:400b:807::2004: time=12ms
Reply from 2607:f8b0:400b:807::2004: time=11ms
Reply from 2607:f8b0:400b:807::2004: time=11ms
Reply from 2607:f8b0:400b:807::2004: time=13ms
Reply from 2607:f8b0:400b:807::2004: time=13ms
Reply from 2607:f8b0:400b:807::2004: time=13ms
Reply from 2607:f8b0:400b:807::2004: time=12ms
Reply from 2607:f8b0:400b:807::2004: time=11ms
Reply from 2607:f8b0:400b:807::2004: time=12ms
Reply from 2607:f8b0:400b:807::2004: time=14ms
Reply from 2607:f8b0:400b:807::2004: time=19ms
Reply from 2607:f8b0:400b:807::2004: time=11ms
Reply from 2607:f8b0:400b:807::2004: time=13ms
Reply from 2607:f8b0:400b:807::2004: time=12ms
Reply from 2607:f8b0:400b:807::2004: time=12ms
Reply from 2607:f8b0:400b:807::2004: time=11ms
Reply from 2607:f8b0:400b:807::2004: time=16ms
Reply from 2607:f8b0:400b:807::2004: time=18ms
Reply from 2607:f8b0:400b:807::2004: time=12ms
Reply from 2607:f8b0:400b:807::2004: time=18ms
Reply from 2607:f8b0:400b:807::2004: time=22ms
Reply from 2607:f8b0:400b:807::2004: time=22ms
Reply from 2607:f8b0:400b:807::2004: time=19ms
Reply from 2607:f8b0:400b:807::2004: time=14ms
Reply from 2607:f8b0:400b:807::2004: time=12ms
Reply from 2607:f8b0:400b:807::2004: time=12ms
Reply from 2607:f8b0:400b:807::2004: time=11ms
Reply from 2607:f8b0:400b:807::2004: time=13ms
Reply from 2607:f8b0:400b:807::2004: time=21ms
Reply from 2607:f8b0:400b:807::2004: time=11ms
Reply from 2607:f8b0:400b:807::2004: time=13ms
Reply from 2607:f8b0:400b:807::2004: time=18ms
Reply from 2607:f8b0:400b:807::2004: time=21ms
Reply from 2607:f8b0:400b:807::2004: time=19ms
Reply from 2607:f8b0:400b:807::2004: time=12ms
Reply from 2607:f8b0:400b:807::2004: time=12ms
Reply from 2607:f8b0:400b:807::2004: time=16ms
Reply from 2607:f8b0:400b:807::2004: time=9ms
Reply from 2607:f8b0:400b:807::2004: time=13ms
Reply from 2607:f8b0:400b:807::2004: time=19ms
Reply from 2607:f8b0:400b:807::2004: time=13ms
Reply from 2607:f8b0:400b:807::2004: time=17ms
Reply from 2607:f8b0:400b:807::2004: time=11ms
Reply from 2607:f8b0:400b:807::2004: time=17ms
Reply from 2607:f8b0:400b:807::2004: time=15ms
Reply from 2607:f8b0:400b:807::2004: time=13ms
Reply from 2607:f8b0:400b:807::2004: time=12ms

Ping statistics for 2607:f8b0:400b:807::2004:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 22ms, Average = 14ms

TRACERT 1_____________________________________________________________________________

C:\Windows\System32>tracert www.google.com

Tracing route to www.google.com [2607:f8b0:400b:807::2004]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 2607:fea8:4fa1:6200:e2db:d1ff:fe3e:d0ff
2 13 ms 13 ms 10 ms 2607:f798:804:9e::1
3 12 ms 10 ms 12 ms 2607:f798:10:10cb:0:690:6324:2197
4 12 ms 12 ms 13 ms 2607:f798:10:2f0:0:2091:4823:2041
5 12 ms 12 ms 12 ms 2607:f798:10:359:0:2091:4823:5210
6 11 ms 12 ms 12 ms 2607:f798:14:83::2
7 18 ms 12 ms 12 ms 2001:4860:0:1::7f51
8 13 ms 13 ms 10 ms 2001:4860:0:1::5b67
9 12 ms 12 ms 12 ms yyz12s07-in-x04.1e100.net [2607:f8b0:400b:807::2004]

Trace complete.
TRACERT 2_____________________________________________________________________________

C:\Windows\System32>tracert www.google.com

Tracing route to www.google.com [2607:f8b0:400b:807::2004]
over a maximum of 30 hops:

1 5 ms <1 ms <1 ms 2607:fea8:4fa1:6200:e2db:d1ff:fe3e:d0ff
2 18 ms 13 ms 11 ms 2607:f798:804:9e::1
3 11 ms 13 ms 12 ms 2607:f798:10:10cb:0:690:6324:2197
4 14 ms 22 ms 12 ms 2607:f798:10:2f0:0:2091:4823:2041
5 12 ms 11 ms 13 ms 2607:f798:10:359:0:2091:4823:5210
6 12 ms 14 ms 13 ms 2607:f798:14:83::2
7 14 ms 14 ms 15 ms 2001:4860:0:1::7f51
8 11 ms 12 ms 12 ms 2001:4860:0:1::5b67
9 14 ms 12 ms 12 ms yyz12s07-in-x04.1e100.net [2607:f8b0:400b:807::2004]

Trace complete.

TRACERT 3_____________________________________________________________________________

C:\Windows\System32>tracert www.google.com

Tracing route to www.google.com [2607:f8b0:400b:807::2004]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 2607:fea8:4fa1:6200:e2db:d1ff:fe3e:d0ff
2 13 ms 12 ms 11 ms 2607:f798:804:9e::1
3 14 ms 11 ms 11 ms 2607:f798:10:10cb:0:690:6324:2197
4 10 ms 13 ms 13 ms 2607:f798:10:2f0:0:2091:4823:2041
5 10 ms 12 ms 12 ms 2607:f798:10:359:0:2091:4823:5210
6 13 ms 12 ms 11 ms 2607:f798:14:83::2
7 13 ms 12 ms 12 ms 2001:4860:0:1::7f51
8 14 ms 20 ms 12 ms 2001:4860:0:1::5b67
9 12 ms 10 ms 11 ms yyz12s07-in-x04.1e100.net [2607:f8b0:400b:807::2004]

Trace complete.

C:\Windows\System32>tracert www.google.com

Tracing route to www.google.com [2607:f8b0:400b:807::2004]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 2607:fea8:4fa1:6200:e2db:d1ff:fe3e:d0ff
2 12 ms 20 ms 11 ms 2607:f798:804:9e::1
3 12 ms 10 ms 12 ms 2607:f798:10:10cb:0:690:6324:2197
4 12 ms 12 ms 19 ms 2607:f798:10:2f0:0:2091:4823:2041
5 11 ms 12 ms 12 ms 2607:f798:10:359:0:2091:4823:5210
6 13 ms 13 ms 12 ms 2607:f798:14:83::2
7 13 ms 12 ms 12 ms 2001:4860:0:1::7f51
8 12 ms 12 ms 12 ms 2001:4860:0:1::5b67
9 9 ms 11 ms 12 ms yyz12s07-in-x04.1e100.net [2607:f8b0:400b:807::2004]

Trace complete.

C:\Windows\System32>

TRACERT To Riot's NA IP._____________________________________________________________________________

Tracing route to 192.207.0.1 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 10.0.0.1
2 17 ms 13 ms 12 ms pool-99-246-12-1.cpe.net.cable.rogers.com [99.246.12.1]
3 12 ms 11 ms 15 ms 69.63.242.193
4 14 ms 11 ms 11 ms 3032-cgw01.wlfdle.rmgt.net.rogers.com [209.148.232.37]
5 26 ms 27 ms 26 ms 209.148.233.106
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
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.

RogersCorey · a week ago

Thank you for getting back to us @Richard_D.

In my experience, Riot games do seem to have the most complaints concerning latency. Are you lagging in any other games or just Riot games?

Could you please also post your computer specs here, including your network card?

~RogersCorey

Richard_D · yesterday

Primarily just Riot games. I have noticed an inconsistent but overall higher ping in Counter-Strike 2 as well, but i don't feel the same.. "delay" as i do with League of Legends in particular which feels noticeable BY FAR. I don't feel the latency as much in Valorant even if it's technically higher, but League feels horrifically delayed compared to the response feel of the last decade (Playing in 2013-2014 the ping was around 71 but they moved their servers and brought us in the GTA down to 20-30) The most common and egregious example has been League of Legends and Valorant. I'd imagine the complaints come from the unknown/unexplained sudden rise over the last while.

Strangely enough, It started with league of legends around the beginning of Covid, but Valorant was completely fine. Then suddenly it started hitting both of them a year or two later. I wish i knew the ping of my games from a few years back, but i had never paid attention to the values before the changes, I might not be of much help there diagnosing the difference between now and then in other titles sadly.

At one point i tried playing with Cloudflare WARP and it immediately brought my ping down to how it regularly feels and it genuinely felt fixed, although it would occasionally cause connection hiccups and occasional high ping spikes so it's not a permanent fix. I'm no network expert by any means but if that's possible just by using that tool, could this simply be a routing issue?

As for the computer specs, here you go:
CPU: Processor AMD Ryzen 7 5800X3D 8-Core Processor

GPU: Gigabyte Radeon RX 7900XTX

RAM: 32GB G.SKILL 3000MHZ

PSU: Asus Strix 850G

MOTHERBOARD: B550 AORUS ELITE AX V2 Rev. 1.5

I swapped out my motherboard mid 2024, the previous one i was using when the issue originally appeared was an Asus Prime x-370 Pro. Both circumstances i use the onboard networking, no dedicated network card.

Gigabyte:

Onboard WiFi 6E 802.11ax & BT 5.2

Realtek® 2.5GbE LAN chip (2.5 Gbit/1 Gbit/100 Mbit) For ethernet (I am using ethernet)

Realtek® Wi-Fi 6E RTL8852CE (For PCB rev. 1.4, 1.5) For Wifi (I do not use this but am providing it regardless just in case)

That should cover that, let me know if there's anything else o7

Rogers Community

Question for Valorant/League players regarding ping

Re: Question for Valorant/League players regarding ping

Re: Question for Valorant/League players regarding ping

Re: Question for Valorant/League players regarding ping

Re: Question for Valorant/League players regarding ping