High ping spikes / jitter. Speed is normal.

Need Help?

That's what we're here for! The goal of the Rogers Community is to help you find answers on everything Rogers. Can't find what you're looking for? Just ask!
cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
I'm Here A Lot
Posts: 5

Re: High ping spikes / jitter. Speed is normal.

@lvectorA :

 

I think it mainly comes down to the fact that they don't care about the ping, as long as you're getting the speeds you pay for, your internet is good in their eyes. Like I said their policy of getting 100ms or lower is atrocious for gamers like us. This policy is perfectly fine for them since they are appleaing to the general population and not specifically gamers. I am sure there's a lot of things going on here but you won't get these kind of speeds over DSL.

 

I mainly play Overwatch at the moment, and on my previous internet which was DSL, I always got a stable ping of 33-35ms with no jitter. Now when the internet is normal, my ping is 38-40ms. This is when it's working properly. As soon as primetime hits and my upload speeds are less than half, then I get anywhere from 50 - 80ms. The worst thing are the spikes that you stated since those don't let you get used to the current ping. I really do hope they do something about this but I highly doubt it unless someone from Rogers says they are working on it. But I definitely agree, one of the "best" ISPs in Canada shouldn't be like this.

 

I would like to note that this is just speculation on my part and I could be completely wrong.

Highlighted
I'm a Regular
Posts: 272

Re: High ping spikes / jitter. Speed is normal.

same problem here ... i'm using a CGN3ROG advanced modem ... it seems the lag is present in all advanced and rocket modems except for one 

 

see datalink's response at the end of this thread:

http://communityforums.rogers.com/t5/forums/forumtopicpage/board-id/Getting_connected/message-id/366...

Highlighted
I'm a Regular
Posts: 272

Re: High ping spikes / jitter. Speed is normal.

Quiet on my home network and lag still occurs (version 4.2.4.6 on a CGN3ROG).   It's happening with all the Hitron's except the one Datalink mentions at the link in my previous post

 

C:\WINDOWS\system32>ping -t 192.168.0.1

Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=10ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=11ms TTL=64
Reply from 192.168.0.1: bytes=32 time=9ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=7ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=8ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=12ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=106ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=125ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=17ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=62ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=10ms TTL=64
Reply from 192.168.0.1: bytes=32 time=14ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=10ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=13ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=10ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=8ms TTL=64
Reply from 192.168.0.1: bytes=32 time=7ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=7ms TTL=64
Reply from 192.168.0.1: bytes=32 time=7ms TTL=64
Reply from 192.168.0.1: bytes=32 time=105ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=51ms TTL=64
Reply from 192.168.0.1: bytes=32 time=8ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=7ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=9ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=13ms TTL=64
Reply from 192.168.0.1: bytes=32 time=11ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=13ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64

Ping statistics for 192.168.0.1:
Packets: Sent = 75, Received = 75, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 125ms, Average = 10ms

Highlighted
I'm a Regular
Posts: 902

Re: High ping spikes / jitter. Speed is normal.

If your a gamer go with bell. Me and 10 other gamers are switching over to bell soon as it's avail which will be soon due to high pings and jitter, also have few friends over at Ottawa with rogers and bell the ones using Rogers having issues when playing online but the ones with bell are not , same game same console same time
Highlighted
I Plan to Stick Around
Posts: 13

Re: High ping spikes / jitter. Speed is normal.

http://image.prntscr.com/image/3a7d63704a654e71b7929e50a40f66e8.png

 

Does this freaking ping and jitter sound normal to anyone???

 

I am sorry but i just simply cannot play any online game with this or even stream HD videos without interruption.

 

Simply pathethic.

Highlighted
I'm a Regular
Posts: 902

Re: High ping spikes / jitter. Speed is normal.

No that's not normal. Rogers only good for speed that's about it but that means nothing for gaming. I have friends on bell Internet with 5mbs/ 1mb up with no issues at all pong 1-2 ms and jitter 1-3
Highlighted
I'm a Regular
Posts: 272

Re: High ping spikes / jitter. Speed is normal.

I am getting one or two T3 timeouts a day, sometimes three or more.  Today I have four.  Is this as good as it gets?  I'm still using the advanced CGN3ROG, not a rocket modem.  A tech came out yesterday and dampened the power levels which are now around 0+-.3 and noise ratios around 40.366.  It hasn't fixed the problem.  I've been insisting that this is a netork issue.  It's no worse, just hasn't improved.  Concerned it's a symptom of a bigger problem.  The performance gets slow and the modem gets hung now and again, can't even ping it when it happens.  Having to reboot too many times.  What can be done?  Anything?

 

1 10/23/16 04:31:49 82000200 critical No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2 10/23/16 04:38:17 90000000 warning MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
3 10/23/16 07:12:14 82000200 critical No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
4 10/23/16 11:29:25 90000000 warning MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:17:10:91:8b:0a;CM-QOS=1.1;CM-VER=3.0;
5 10/23/16 11:29:59 73027100 error T6 Timeout and retries exceeded;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
6 10/23/16 11:29:59 73000200 critical REG RSP not received;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
7 10/23/16 11:30:31 82000200 critical No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
8 10/23/16 11:30:43 90000000 warning MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
9 10/23/16 13:41:21 82000200 critical No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0
Highlighted
I'm Here A Lot
Posts: 5

Re: High ping spikes / jitter. Speed is normal.

 @jszentir I have been experiencing the T3 timeouts as well and have horrible ping/jitter. 3 (1 senior) technicians have come and no imporvement or an answer as to why it's happening. My suspicion is that it's most likely caused by congestion in my area but I don't think that is going to get resolved anytime soon so looking to switch to Bell by the end of this week. My download speeds for the most part are fine and it's just the upload speed affected which in turn effects my ping in game. Really unfortunate to be having these problems from the moment I switched around 3 weeks ago.

Highlighted
I Plan to Stick Around
Posts: 13

Re: High ping spikes / jitter. Speed is normal.

You guys are lucky that you can switch to bell.

 

My apartment has only Rogers available.

 

Bell only offers 5/1 in my building which is not enough for my whole family.

 

Don't think switching to other providers will solve the problem as they all use Rogers line under a different name, though it won't hurt to try. Thinking of switching soon myself. Hope Rogers can solve this problem or they will be losing a lot of customers.

Highlighted
I'm a Regular
Posts: 272

Re: High ping spikes / jitter. Speed is normal.

There are two separate issues here.  

 

1.  The modems have inherent lag.  The spikes are internal in the modem as we can all see when we ping our modems.  Bridging to your own does not solve the problem. Datalink has indicated that the latency has been fixed in only one model, the ACSMR.  See

http://communityforums.rogers.com/t5/forums/forumtopicpage/board-id/Getting_connected/message-id/366... third one down.  Unfortunately the 2.4Ghz band has been weakend by a second ghost SSID introduced.

 

2.  The T3 timeouts are strictly a network issue and cause disconnects.  The timeouts are nowhere near as frequent as the ping - lag - latency that is a problem with these modems.  

 

Some more about the modem latency at at http://communityforums.rogers.com/t5/forums/forumtopicpage/board-id/Getting_connected/thread-id/3286...