Brutal latency/ping Recently

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
-G-
Resident Expert
Resident Expert
Posts: 1,742

Re: Brutal latency/ping Recently


@lethalsniper wrote:
And that won’t put a load on the node if I ping 8.8.8.8 for 1 hour ?

No.  If you are just sending traffic to and from another server on the Internet, that's fine because it does not put any load on the node's processor modules.

 

 

FYI, I just sent 100 pings to 8.8.8.8 and to my local CMTS router and got the following results:

 

Ping statistics for 8.8.8.8:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 8ms, Maximum = 17ms, Average = 10ms

 

Ping statistics for [deleted]:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 5ms, Maximum = 17ms, Average = 9ms

 

That's normal for me now.  Note that the ping round trip times to dns.google and the CMTS router are also almost identical.. so the CMTS router is responding to my pings immediately, indicating that its CPU is not under any significant load.

 

Going back 9 months ago, when things were REALLY bad in my area, the ping RTTs to dns.google were spiking to > 10000ms and the RTTs for corresponding pings to the CMTS router were spiking to > 12000ms.  My local router was responding instantaneously.  I also ran pings and traceroutes from my XB6 gateway and confirmed that my local node basically stopped forwarding traffic for up to 10 seconds at a time, which is practically an eternity in network time.  On top of that, the CMTS router was taking 2000ms to respond to pings, confirming that its processor was under very heavy load, and whatever it was doing likely put the node into a state where it could not forward packets for several thousand milliseconds at a time... which also caused traffic to build up in the input queues and caused some traffic to get lost if any queues overflowed.

 

If you are seeing periodic ping spikes but the ping RTTs to dns.google and the CMTS are almost the same, the node is probably just getting loaded due to traffic volumes.  Rogers should be able to confirm that.

 

If the CMTS router is taking hundreds or thousands of milliseconds longer to respond than dns.google, then your node's processer is extraordinarily busy doing something that that might cause your node to cease forwarding network packets.  Your average Rogers support tech may not be able to confirm this.

 

If traffic is getting backed up in the node for whatever reason, the signal and line stats to your modem could still look perfectly normal... which may result in a support tech saying that there is no problem on the Rogers network.



-G-
Resident Expert
Resident Expert
Posts: 1,742

Re: Brutal latency/ping Recently


@lethalsniper wrote:

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=14ms TTL=116
Reply from 8.8.8.8: bytes=32 time=19ms TTL=116
Reply from 8.8.8.8: bytes=32 time=248ms TTL=116
Reply from 8.8.8.8: bytes=32 time=11ms TTL=116


Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 248ms, Average = 73ms


Rogers does not provide any service guarantees of any kind but even they say that you should not see ping RTTs (to a well-connected host) that exceed 100ms.  This is where a simultaneous ping test to the CMTS router comes in handy; if it takes as long (or longer) for the CMTS router to respond, then the latency is almost certainly being introduced by the local node.



lethalsniper
I'm an Enthusiast
Posts: 1,009

Re: Brutal latency/ping Recently

Ping statistics for 172.217.1.164: www.google.com
Packets: Sent = 1452, Received = 1443, Lost = 9 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 4ms, Maximum = 516ms, Average = 13ms

And as for the CMTS when pinging I’m getting roughly 528 ms
AngryChicken
I Plan to Stick Around
Posts: 24

Re: Brutal latency/ping Recently

I just received a pleasant surprise. An agent from the office of the president of Rogers called me. We had a pleasant chat while I laid out very calmly the challenges my community has been having with Rogers’ Internet service. I was left with the feeling that he agreed with my points and he said he would do what he could to escalate and move up the planned late summer network upgrade to address these congestion issues. Colour me impressed.
borisnet
I Plan to Stick Around
Posts: 9

Re: Brutal latency/ping Recently

Thank you for the reply @AngryChicken  - while there is no way to confirm your statement, it seems to point at network congestion.

It is still a bit bizarre that the congestion happens so punctually and not for a longer period of time.

 

borisnet
I Plan to Stick Around
Posts: 9

Re: Brutal latency/ping Recently

This is now becoming unbearable.

The frequency has increased to every few hours now so I am kind of leaning towards capacity issue now and no improvement in sight. So sad and frustrating since support cannot do anything about large capacity issue.

 

 

lethalsniper
I'm an Enthusiast
Posts: 1,009

Re: Brutal latency/ping Recently

I know what you mean it does get frustrating especially when it keeps on happening all the time with no fix ..
stepy2015
I Plan to Stick Around
Posts: 104

Re: Brutal latency/ping Recently

Its happening pretty much all day everyday for me now I am DONE and no updates on my ticket, what is going on Rogers we need transparency 

jasonchan
I've Been Here Awhile
Posts: 3

Re: Brutal latency/ping Recently

For me, my zoom calls have been brutal - I just checked and the ping is reasonable, but there's still some lost packets.

 

Reply from 8.8.8.8: bytes=32 time=4ms TTL=116
Reply from 8.8.8.8: bytes=32 time=12ms TTL=116
Reply from 8.8.8.8: bytes=32 time=10ms TTL=116
Reply from 8.8.8.8: bytes=32 time=7ms TTL=116
Reply from 8.8.8.8: bytes=32 time=14ms TTL=116
Reply from 8.8.8.8: bytes=32 time=22ms TTL=116
Reply from 8.8.8.8: bytes=32 time=10ms TTL=116
Reply from 8.8.8.8: bytes=32 time=9ms TTL=116
Reply from 8.8.8.8: bytes=32 time=9ms TTL=116
Reply from 8.8.8.8: bytes=32 time=14ms TTL=116
Reply from 8.8.8.8: bytes=32 time=11ms TTL=116
Reply from 8.8.8.8: bytes=32 time=9ms TTL=116
Reply from 8.8.8.8: bytes=32 time=7ms TTL=116
Reply from 8.8.8.8: bytes=32 time=9ms TTL=116
Reply from 8.8.8.8: bytes=32 time=4ms TTL=116
Reply from 8.8.8.8: bytes=32 time=14ms TTL=116
Reply from 8.8.8.8: bytes=32 time=11ms TTL=116
Reply from 8.8.8.8: bytes=32 time=10ms TTL=116
Reply from 8.8.8.8: bytes=32 time=15ms TTL=116
Reply from 8.8.8.8: bytes=32 time=16ms TTL=116
Reply from 8.8.8.8: bytes=32 time=11ms TTL=116
Reply from 8.8.8.8: bytes=32 time=12ms TTL=116
Reply from 8.8.8.8: bytes=32 time=17ms TTL=116
Reply from 8.8.8.8: bytes=32 time=8ms TTL=116
Reply from 8.8.8.8: bytes=32 time=9ms TTL=116
Reply from 8.8.8.8: bytes=32 time=11ms TTL=116
Reply from 8.8.8.8: bytes=32 time=9ms TTL=116
Reply from 8.8.8.8: bytes=32 time=14ms TTL=116
Reply from 8.8.8.8: bytes=32 time=12ms TTL=116
Reply from 8.8.8.8: bytes=32 time=6ms TTL=116
Reply from 8.8.8.8: bytes=32 time=11ms TTL=116
Reply from 8.8.8.8: bytes=32 time=11ms TTL=116
Reply from 8.8.8.8: bytes=32 time=10ms TTL=116
Reply from 8.8.8.8: bytes=32 time=14ms TTL=116
Reply from 8.8.8.8: bytes=32 time=9ms TTL=116
Reply from 8.8.8.8: bytes=32 time=7ms TTL=116
Reply from 8.8.8.8: bytes=32 time=13ms TTL=116
Reply from 8.8.8.8: bytes=32 time=11ms TTL=116
Reply from 8.8.8.8: bytes=32 time=7ms TTL=116
Reply from 8.8.8.8: bytes=32 time=5ms TTL=116
Reply from 8.8.8.8: bytes=32 time=12ms TTL=116
Reply from 8.8.8.8: bytes=32 time=12ms TTL=116
Reply from 8.8.8.8: bytes=32 time=10ms TTL=116
Reply from 8.8.8.8: bytes=32 time=11ms TTL=116
Reply from 8.8.8.8: bytes=32 time=9ms TTL=116
Reply from 8.8.8.8: bytes=32 time=14ms TTL=116
Reply from 8.8.8.8: bytes=32 time=10ms TTL=116
Reply from 8.8.8.8: bytes=32 time=9ms TTL=116
Reply from 8.8.8.8: bytes=32 time=11ms TTL=116
Reply from 8.8.8.8: bytes=32 time=13ms TTL=116
Reply from 8.8.8.8: bytes=32 time=10ms TTL=116
Reply from 8.8.8.8: bytes=32 time=11ms TTL=116
Reply from 8.8.8.8: bytes=32 time=4ms TTL=116
Reply from 8.8.8.8: bytes=32 time=12ms TTL=116
Reply from 8.8.8.8: bytes=32 time=8ms TTL=116
Reply from 8.8.8.8: bytes=32 time=8ms TTL=116
Reply from 8.8.8.8: bytes=32 time=6ms TTL=116
Reply from 8.8.8.8: bytes=32 time=9ms TTL=116
Reply from 8.8.8.8: bytes=32 time=12ms TTL=116
Reply from 8.8.8.8: bytes=32 time=13ms TTL=116
Reply from 8.8.8.8: bytes=32 time=18ms TTL=116
Reply from 8.8.8.8: bytes=32 time=7ms TTL=116
Reply from 8.8.8.8: bytes=32 time=10ms TTL=116
Reply from 8.8.8.8: bytes=32 time=17ms TTL=116
Reply from 8.8.8.8: bytes=32 time=8ms TTL=116
Reply from 8.8.8.8: bytes=32 time=10ms TTL=116
Reply from 8.8.8.8: bytes=32 time=10ms TTL=116
Reply from 8.8.8.8: bytes=32 time=10ms TTL=116
Reply from 8.8.8.8: bytes=32 time=10ms TTL=116
Reply from 8.8.8.8: bytes=32 time=13ms TTL=116
Reply from 8.8.8.8: bytes=32 time=11ms TTL=116
Reply from 8.8.8.8: bytes=32 time=5ms TTL=116
Reply from 8.8.8.8: bytes=32 time=9ms TTL=116
Reply from 8.8.8.8: bytes=32 time=8ms TTL=116
Reply from 8.8.8.8: bytes=32 time=9ms TTL=116
Reply from 8.8.8.8: bytes=32 time=6ms TTL=116
Reply from 8.8.8.8: bytes=32 time=12ms TTL=116
Reply from 8.8.8.8: bytes=32 time=13ms TTL=116
Reply from 8.8.8.8: bytes=32 time=11ms TTL=116
Reply from 8.8.8.8: bytes=32 time=8ms TTL=116
Reply from 8.8.8.8: bytes=32 time=12ms TTL=116
Reply from 8.8.8.8: bytes=32 time=8ms TTL=116
Reply from 8.8.8.8: bytes=32 time=7ms TTL=116
Reply from 8.8.8.8: bytes=32 time=11ms TTL=116
Reply from 8.8.8.8: bytes=32 time=9ms TTL=116
Reply from 8.8.8.8: bytes=32 time=10ms TTL=116
Reply from 8.8.8.8: bytes=32 time=11ms TTL=116
Reply from 8.8.8.8: bytes=32 time=24ms TTL=116
Reply from 8.8.8.8: bytes=32 time=11ms TTL=116
Reply from 8.8.8.8: bytes=32 time=10ms TTL=116
Reply from 8.8.8.8: bytes=32 time=11ms TTL=116
Reply from 8.8.8.8: bytes=32 time=14ms TTL=116
Reply from 8.8.8.8: bytes=32 time=14ms TTL=116
Reply from 8.8.8.8: bytes=32 time=8ms TTL=116
Reply from 8.8.8.8: bytes=32 time=10ms TTL=116
Request timed out.
Reply from 8.8.8.8: bytes=32 time=17ms TTL=116
Reply from 8.8.8.8: bytes=32 time=8ms TTL=116
Reply from 8.8.8.8: bytes=32 time=10ms TTL=116
Reply from 8.8.8.8: bytes=32 time=12ms TTL=116
Reply from 8.8.8.8: bytes=32 time=7ms TTL=116
Reply from 8.8.8.8: bytes=32 time=14ms TTL=116
Request timed out.
Reply from 8.8.8.8: bytes=32 time=13ms TTL=116
Reply from 8.8.8.8: bytes=32 time=10ms TTL=116
Reply from 8.8.8.8: bytes=32 time=4ms TTL=116
Reply from 8.8.8.8: bytes=32 time=13ms TTL=116
Reply from 8.8.8.8: bytes=32 time=7ms TTL=116
Reply from 8.8.8.8: bytes=32 time=7ms TTL=116
Reply from 8.8.8.8: bytes=32 time=8ms TTL=116
Reply from 8.8.8.8: bytes=32 time=9ms TTL=116
Reply from 8.8.8.8: bytes=32 time=5ms TTL=116
Reply from 8.8.8.8: bytes=32 time=12ms TTL=116
Reply from 8.8.8.8: bytes=32 time=9ms TTL=116
Reply from 8.8.8.8: bytes=32 time=9ms TTL=116
Reply from 8.8.8.8: bytes=32 time=10ms TTL=116
Reply from 8.8.8.8: bytes=32 time=22ms TTL=116
Reply from 8.8.8.8: bytes=32 time=10ms TTL=116
Reply from 8.8.8.8: bytes=32 time=12ms TTL=116
Reply from 8.8.8.8: bytes=32 time=10ms TTL=116
Reply from 8.8.8.8: bytes=32 time=9ms TTL=116
Reply from 8.8.8.8: bytes=32 time=8ms TTL=116
Reply from 8.8.8.8: bytes=32 time=8ms TTL=116
Reply from 8.8.8.8: bytes=32 time=8ms TTL=116
Reply from 8.8.8.8: bytes=32 time=27ms TTL=116
Reply from 8.8.8.8: bytes=32 time=7ms TTL=116
Reply from 8.8.8.8: bytes=32 time=9ms TTL=116
Reply from 8.8.8.8: bytes=32 time=7ms TTL=116
Reply from 8.8.8.8: bytes=32 time=6ms TTL=116
Reply from 8.8.8.8: bytes=32 time=11ms TTL=116
Reply from 8.8.8.8: bytes=32 time=12ms TTL=116
Reply from 8.8.8.8: bytes=32 time=12ms TTL=116
Reply from 8.8.8.8: bytes=32 time=12ms TTL=116
Reply from 8.8.8.8: bytes=32 time=13ms TTL=116
Reply from 8.8.8.8: bytes=32 time=10ms TTL=116
Reply from 8.8.8.8: bytes=32 time=11ms TTL=116
Reply from 8.8.8.8: bytes=32 time=9ms TTL=116
Reply from 8.8.8.8: bytes=32 time=15ms TTL=116
Reply from 8.8.8.8: bytes=32 time=7ms TTL=116
Reply from 8.8.8.8: bytes=32 time=10ms TTL=116
Reply from 8.8.8.8: bytes=32 time=11ms TTL=116
Reply from 8.8.8.8: bytes=32 time=11ms TTL=116
Reply from 8.8.8.8: bytes=32 time=14ms TTL=116
Reply from 8.8.8.8: bytes=32 time=8ms TTL=116
Reply from 8.8.8.8: bytes=32 time=16ms TTL=116
Reply from 8.8.8.8: bytes=32 time=9ms TTL=116
Reply from 8.8.8.8: bytes=32 time=14ms TTL=116
Reply from 8.8.8.8: bytes=32 time=7ms TTL=116
Reply from 8.8.8.8: bytes=32 time=7ms TTL=116
Reply from 8.8.8.8: bytes=32 time=7ms TTL=116
Reply from 8.8.8.8: bytes=32 time=10ms TTL=116
Reply from 8.8.8.8: bytes=32 time=4ms TTL=116
Reply from 8.8.8.8: bytes=32 time=11ms TTL=116
Reply from 8.8.8.8: bytes=32 time=11ms TTL=116
Reply from 8.8.8.8: bytes=32 time=10ms TTL=116
Reply from 8.8.8.8: bytes=32 time=5ms TTL=116
Reply from 8.8.8.8: bytes=32 time=8ms TTL=116
Reply from 8.8.8.8: bytes=32 time=9ms TTL=116
Reply from 8.8.8.8: bytes=32 time=12ms TTL=116

Ping statistics for 8.8.8.8:
Packets: Sent = 204, Received = 202, Lost = 2 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 4ms, Maximum = 27ms, Average = 10ms

 

 

 

Downstream Overview
Port IDFrequency (MHz)ModulationSignal strength (dBmV)Channel IDSignal noise ratio (dB)
1669000000QAM2568.4001938.983
2657000000QAM2569.0001740.366
3663000000QAM2568.4001840.366
4651000000QAM2569.4001640.366
5597000000QAM25610.400840.946
6603000000QAM25610.199940.366
7609000000QAM25610.0991040.946
8615000000QAM2569.9001140.946
9621000000QAM2569.9001240.366
10633000000QAM25610.3001340.366
11639000000QAM2569.5001440.366
12645000000QAM2568.9001540.946
13279000000QAM2568.400140.946
14579000000QAM25610.300540.366
15585000000QAM25610.500640.366
16591000000QAM25610.599740.946
17675000000QAM2568.4002040.366
18681000000QAM2568.0002140.366
19687000000QAM2567.9002238.983
20693000000QAM2568.4002340.366
21699000000QAM2567.9002438.983
22705000000QAM2567.9002538.983
23711000000QAM2568.0002638.983
24717000000QAM2567.4002738.605
25723000000QAM2566.0002838.605
26825000000QAM2567.5992938.605
27831000000QAM2567.6993038.605
28837000000QAM2567.0003138.605
29843000000QAM2566.9003238.605
30849000000QAM2567.300238.605
31855000000QAM2566.900338.605
32861000000QAM2566.699438.605
OFDM Downstream Overview
ReceiverFFT typeSubcarr 0 Frequency(MHz)PLC lockedNCP lockedMDC1 lockedPLC power(dBmv)
0NANANONONONA
14K275600000YESYESYES10.400002
Upstream Overview
Port IDFrequency (MHz)ModulationSignal strength (dBmV)Channel IDBandwidth
13870000064QAM40.02086400000
22110000064QAM39.01053200000
33230000064QAM39.52076400000
42590000064QAM39.27066400000
50QAM_NONE----1600000
60QAM_NONE----1600000
70QAM_NONE----1600000
80QAM_NONE----1600000
OFDM/OFDMA Overview
Channel IndexStatelin Digital AttDigital AttBW (sc's*fft)Report PowerReport Power1_6FFT Size
0DISABLED0.00000.00000.00000.00000.00002K
1DISABLED0.00000.00000.00000.00000.00002K
lethalsniper
I'm an Enthusiast
Posts: 1,009

Re: Brutal latency/ping Recently

Once again Rogers tech a no show .. waisted my time and superintendent time was supposed to be here from 8-10 am for a upload noise issue .. no call . Nothing .. how can I escalate this issue? Unprofessional! This is not the first time this has happened.. @rogerstony @Datalink @RogersRob @CommunityHelps