Periods of high ping

[rafehchau]

Hi, I'm having an issue with Rogers Ignite. My speeds are fine, and general browsing and downloads are great. I'm hooked up with ethernet and I get the promised download speeds.

The main issue is online gaming. Some days/ weeks the pings are amazingly good. And some days its down right terrible.

To say, when I first got it I had 25ms to league of legends, then for a couple months it 55-60ms. And then for a few weeks it went down to 25 and now its back up at 60ms. 

Can anyone help me identify what's going on. I have a tech coming over, but I'm not sure that would resolve it.

I have net logs of some of the games I played: 

2023 - 11 - 11    2:46PM                                                           2023 - 11 - 10

and this was 2 weeks prior.

Is my area congested? It turns into a terrible experience, and there is a noticeable delay between the clicks.

*Added Labels*

[RogersTony]

Hello, @rafehchau 

Welcome to the Rogers Community Forums!

I can understand how hard to can be to game online when your experiencing high ping issues.

We definitely want to look into this for you. We'll need to review ping tests and traceroutes done using the command prompt to determine latency. You can find the specific steps here.

We look forward to reviewing your results.

RogersTony

[rafehchau]

Hi Tony. This seems like a routing issue. I used exitlag, wtfast kind of vpns and rerouting software, and it lowered the ping. Went from 55 to 30, but not stable all the time. Every game has a different stable ping normally, so I feel like most of the times the game is connecting through a suboptimal route.

Tracing route to www.google.com [2607:f8b0:4020:805::2004]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 2607:fea8:bdc0:da00:4abd:ceff:fe93:63c7
2 17 ms 11 ms 13 ms 2607:f798:80c:b6::1
3 11 ms 10 ms 10 ms 2607:f798:10:38ac:0:672:3122:2241
4 57 ms 31 ms 27 ms 2607:f798:10:ea15:0:2091:4823:8078
5 28 ms 14 ms 34 ms 2607:f798:10:501c:0:721:3913:9190
6 13 ms 15 ms 25 ms 2607:f798:14:61:0:2091:4821:5158
7 * 25 ms 20 ms 2001:4860:0:1::7b23
8 32 ms 24 ms 21 ms 2001:4860:0:1::991
9 44 ms 42 ms 46 ms yul02s05-in-x04.1e100.net [2607:f8b0:4020:805::2004]

Trace complete.

Pinging www.google.com [2607:f8b0:4020:805::2004] with 32 bytes of data:
Reply from 2607:f8b0:4020:805::2004: time=28ms
Reply from 2607:f8b0:4020:805::2004: time=52ms
Reply from 2607:f8b0:4020:805::2004: time=117ms
Reply from 2607:f8b0:4020:805::2004: time=18ms
Reply from 2607:f8b0:4020:805::2004: time=27ms
Reply from 2607:f8b0:4020:805::2004: time=50ms
Reply from 2607:f8b0:4020:805::2004: time=28ms
Reply from 2607:f8b0:4020:805::2004: time=60ms
Reply from 2607:f8b0:4020:805::2004: time=58ms
Reply from 2607:f8b0:4020:805::2004: time=23ms
Reply from 2607:f8b0:4020:805::2004: time=34ms
Reply from 2607:f8b0:4020:805::2004: time=29ms
Reply from 2607:f8b0:4020:805::2004: time=29ms
Reply from 2607:f8b0:4020:805::2004: time=15ms
Reply from 2607:f8b0:4020:805::2004: time=48ms
Reply from 2607:f8b0:4020:805::2004: time=18ms
Reply from 2607:f8b0:4020:805::2004: time=36ms
Reply from 2607:f8b0:4020:805::2004: time=21ms
Reply from 2607:f8b0:4020:805::2004: time=67ms
Reply from 2607:f8b0:4020:805::2004: time=16ms
Reply from 2607:f8b0:4020:805::2004: time=13ms
Reply from 2607:f8b0:4020:805::2004: time=63ms
Reply from 2607:f8b0:4020:805::2004: time=100ms
Reply from 2607:f8b0:4020:805::2004: time=15ms
Reply from 2607:f8b0:4020:805::2004: time=45ms
Reply from 2607:f8b0:4020:805::2004: time=22ms
Reply from 2607:f8b0:4020:805::2004: time=19ms
Reply from 2607:f8b0:4020:805::2004: time=12ms
Reply from 2607:f8b0:4020:805::2004: time=41ms
Reply from 2607:f8b0:4020:805::2004: time=19ms
Reply from 2607:f8b0:4020:805::2004: time=21ms
Reply from 2607:f8b0:4020:805::2004: time=24ms
Reply from 2607:f8b0:4020:805::2004: time=45ms
Reply from 2607:f8b0:4020:805::2004: time=23ms
Reply from 2607:f8b0:4020:805::2004: time=22ms
Reply from 2607:f8b0:4020:805::2004: time=28ms
Reply from 2607:f8b0:4020:805::2004: time=22ms
Reply from 2607:f8b0:4020:805::2004: time=50ms
Reply from 2607:f8b0:4020:805::2004: time=16ms
Reply from 2607:f8b0:4020:805::2004: time=58ms
Reply from 2607:f8b0:4020:805::2004: time=18ms
Reply from 2607:f8b0:4020:805::2004: time=22ms
Reply from 2607:f8b0:4020:805::2004: time=24ms
Reply from 2607:f8b0:4020:805::2004: time=10ms
Reply from 2607:f8b0:4020:805::2004: time=35ms
Reply from 2607:f8b0:4020:805::2004: time=16ms
Reply from 2607:f8b0:4020:805::2004: time=66ms
Reply from 2607:f8b0:4020:805::2004: time=77ms
Reply from 2607:f8b0:4020:805::2004: time=25ms
Reply from 2607:f8b0:4020:805::2004: time=52ms

Ping statistics for 2607:f8b0:4020:805::2004:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 117ms, Average = 35ms

[RogersCorey]

Is this happening everytime you play games or only at certain times of day?

Regards,

RogersCorey

[rafehchau]

It happens all the time.

For a few weeks it was great but then it has started again. Using Wt -fast fixed it for me if I use their exit server that routes to Chicago through Toronto. If I use the servers that route through New York, Montreal or through Virginia or whatever. It's bad then. I live in Ottawa.

Although sucks I have to pay an additional subscription just to play one game without feeling all that jitter and unresponsiveness.

[lll7]

I'm having the same issue you're describing but in Kitchener. Ping was fine until about two weeks ago. It used to sit at 22 - 25 and now it's 38 - 60. I'm being told it has nothing to do with Rogers internet which I find hard to believe..

[RogersTony]

Hello, @rafehchau & @lll7 

Thanks for those additional details.

@rafehchau - We will need to run some tests and gather more details from you to determine what is causing the latency issues you've described. Please send a private message to @CommunityHelps so we can get started. Not familiar with our private messaging system? No worries, click here. 

@lll7 - We definitely want to help you with this issue. We'll need some examples of the latency you are experiencing. Please provide us with a ping test and a traceroute by following the steps outlined here. 

We look forward to hearing from you both.

Regards,

CommunityHelps

RogersTony

[Safwaan]

Same issue I'm having in Cambridge. Had around 50 ms in games right after we installed the router and hasn't gotten better at all

[trevorholden]

Exactly same scenario and timeline for me. Also in Kitchener.

[trevorholden]

Will also mention that friends that are with other ISPs living in this area have elite ping compared to me.
Has to be on Rogers side. 

[RogersZia]

Hello @Safwaan and @trevorholden and welcome to the Community!

We'd be happy to troubleshoot the issue with you two. Please refer to RogersTony's post here for next steps. 

RogersZia

[JBeach]

I've had this issue on and off, more on, for about 8+ months. It's a Rogers only problem, all other ISP's that my friends have don't have these issues. I have been in contact with support the entire time. They have yet to find a solution. They said they will do work in my area that will take +3 more months to even start might fix it. 🙂

[FedUp5000]

38 - 60 and your complaining?

I sit at around 120 with spikes up to 6000+ now and cant get any help!

Id kill for 38-60