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
Highlighted
Resident Expert
Resident Expert
Posts: 1,292

Re: Brutal latency/ping Recently


@kpaddle wrote:

I have been having constant ping spikes on my ignite gigabit connection for a while now (over 1000 ping on some occasions) and I average around 300-400mbps when running speed tests on ethernet.

I am running my Technicolor CGM4140COM in bridge mode connected to a pfsense router (dual core 4 thread i3 with 8GB RAM) and a tp-link gigabit switch.  I have tried connecting direct to the Rogers gateway with the same results.


Welcome to the Community!

 

Your Downstream signal levels actually look pretty normal but they only tell part of the picture.  If the Rogers network is introducing latency, it could be happening in the "CMTS router"... and nothing out of the ordinary would show up on your downstream or upstream signal levels, error stats, or in the modem's Events log.  You would need to perform additional tests to localize where latency spikes and/or packet loss is occurring and those tests would also need to rule out anything on your side as the cause.

 

I don't use pfSense and I certainly don't mean to bash it in any way.  However, if you search the Internet for pfsense "ping spikes" , you will get a bunch of hits where other users are describing pretty much the same issue that you are seeing, including the 1000 ms ping spikes.

 

You mentioned that the performance issues also occur with a direct connection to the Rogers modem.  In that case, I would take your XB6 out of bridge mode, connect a computer directly over Ethernet, run your tests to confirm that the performance issues still reproduce consistently, and contact Rogers Tech Support to report the problem.  Get them to check the signal levels to your modem, noise levels in your area, check the loads on your local node, and check for other possible problems affecting your area.  You can also send a private message to @CommunityHelps  to report the problem and ask them to investigate and open a ticket on your behalf.



Highlighted
I Plan to Stick Around
Posts: 9

Re: Brutal latency/ping Recently

been having this issue for about 1 year and 2 months now, words cannot describe the frustration i have built up on this subject.

Highlighted
I've Been Here Awhile
Posts: 3

Re: Brutal latency/ping Recently

Thank you for your help and sorry for the late reply. I have treated with a new software (untangle) and same issue, i then retested with the roger router/modem in gateway mode and still have the same issue directly connected to it with ethernet. I will contact Rogers tech support. Thanks again
Highlighted
I've Been Here Awhile
Posts: 3

Re: Brutal latency/ping Recently

Are these signal levels causing my Latency Issue
 
Been having latency issues for the past few months when playing online games the connection is not stable at all. Last time I called in and talked to someone I was told everything looked good on their end. I am no pro but Channel 1 and 33 of the downstream don't look right when every other channel is close to 0

Index Lock Status Frequency SNR Power Level Modulation
Downstream
Channel Bonding Value
17
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
 
Locked
Locked
Locked
Locked
Locked
Locked
Locked
Locked
Locked
Locked
Locked
Locked
Locked
Locked
Locked
Locked
Locked
Locked
Locked
Locked
Locked
Locked
Locked
Locked
Locked
Locked
Locked
Locked
Locked
Locked
Locked
Locked
Locked
Locked
657 MHz
279 MHz
849 MHz
855 MHz
861 MHz
579 MHz
585 MHz
591 MHz
597 MHz
603 MHz
609 MHz
615 MHz
621 MHz
633 MHz
639 MHz
645 MHz
651 MHz
663 MHz
669 MHz
675 MHz
681 MHz
687 MHz
693 MHz
699 MHz
705 MHz
711 MHz
717 MHz
723 MHz
825 MHz
831 MHz
837 MHz
843 MHz
350 MHz
275600000
36.5 dB
40.9 dB
33.8 dB
33.5 dB
33.2 dB
38.8 dB
38.2 dB
37.8 dB
37.7 dB
37.6 dB
37.8 dB
38.2 dB
38.5 dB
38.5 dB
38.4 dB
38.0 dB
37.0 dB
36.1 dB
36.5 dB
36.1 dB
37.1 dB
37.2 dB
36.6 dB
36.3 dB
36.2 dB
35.8 dB
35.9 dB
36.1 dB
35.1 dB
35.1 dB
35.1 dB
34.6 dB
40.6 dB
NA
0.9 dBmV
8.6 dBmV
-3.6 dBmV
-4.2 dBmV
-4.6 dBmV
2.2 dBmV
1.3 dBmV
0.7 dBmV
0.8 dBmV
0.3 dBmV
0.7 dBmV
1.2 dBmV
1.5 dBmV
1.7 dBmV
1.4 dBmV
0.7 dBmV
0.1 dBmV
-1.3 dBmV
-1.0 dBmV
0.2 dBmV
0.2 dBmV
0.1 dBmV
0.4 dBmV
-1.1 dBmV
-1.3 dBmV
-1.6 dBmV
-1.6 dBmV
-1.4 dBmV
-2.5 dBmV
-2.5 dBmV
-2.3 dBmV
-2.8 dBmV
7.5 dBmV
NA
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
256 QAM
OFDM
OFDM
IndexLock StatusFrequencySymbol RatePower LevelModulationChannel Type
Upstream
Channel Bonding Value
1
2
3
4
Locked
Locked
Locked
Locked
21 MHz
25 MHz
32 MHz
38 MHz
2560
5120
5120
5120
36.8 dBmV
37.5 dBmV
37.8 dBmV
39.0 dBmV
QAM
QAM
QAM
QAM
TDMA_AND_ATDMA
ATDMA
ATDMA
ATDMA
Highlighted
Moderator
Moderator
Posts: 986

Re: Brutal latency/ping Recently

Hello, @TheBings

 

Welcome to the Rogers Community Forums!

 

Thanks so much for posting your concern. I know how frustrating it can be to deal with latency while gaming. 

 

There doesn't appear to be an issue with the signal levels as it is still within the acceptable range. Latency can be tricky to diagnose but we can learn a lot from a ping test and traceroute. Please follow the steps outlined in our Troubleshooting Latency (Wired Devices) Knowledge Base article. Post the results of the ping test and traceroute so the community can review it. 

 

Please ensure to redact the IP address in the first hop on the traceroute as this is personal information that should not be shared in a public forum.

 

We look forward to reviewing your test results.

 

RogersTony

Highlighted
I've Been Here Awhile
Posts: 3

Re: Brutal latency/ping Recently

Hi, Tony and thanks for the help just to let you know the tests were done on my pc connected directly to the modem with ethernet. I added more than you asked for just trying to give you as much information to possibly help my situation.

 

Rogers-Ping for two hours

Ping statistics for 64.71.255.204:
Packets: Sent = 7200, Received = 7198, Lost = 2 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 3ms, Maximum = 596ms, Average = 19ms

 

Google-Ping for two hours

Ping statistics for 172.217.0.228:
Packets: Sent = 7200, Received = 7200, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 5ms, Maximum = 253ms, Average = 24ms

 

Ping statistics for 172.217.164.196:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 14ms, Maximum = 153ms, Average = 43ms

 

Wan Default Gateway

Ping statistics for 99.xxx.xx.x:
Packets: Sent = 3600, Received = 3600, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 3ms, Maximum = 211ms, Average = 28ms


Tracing route to www.google.com [172.217.1.164]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms 10.0.0.1
2 31 ms 14 ms 33 ms 99.xxx.xx.x
3 28 ms 75 ms 140 ms gi-1-0-0.cmts02.ym.phub.net.cable.rogers.com [66.185.90.25]
4 38 ms 36 ms 136 ms 9015-cgw01.mtnk.asr9k.rmgt.net.rogers.com [209.148.224.177]
5 40 ms 23 ms 36 ms 209.148.233.46
6 78 ms 53 ms 48 ms 72.14.222.87
7 120 ms 89 ms 34 ms 108.170.250.225
8 26 ms 19 ms 25 ms 108.170.226.223
9 38 ms 84 ms 89 ms yyz10s04-in-f4.1e100.net [172.217.1.164]

 

Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 10.0.0.1
2 66 ms 32 ms 14 ms 99.xxx.xx.x
3 40 ms 23 ms 56 ms gi-1-0-0.cmts02.ym.phub.net.cable.rogers.com [66.185.90.25]
4 39 ms 34 ms 30 ms 9015-cgw01.mtnk.asr9k.rmgt.net.rogers.com [209.148.224.177]
5 59 ms 32 ms 71 ms 209.148.233.46
6 * * * Request timed out.
7 71 ms 41 ms 66 ms 108.170.250.225
8 173 ms 66 ms 36 ms 216.239.35.235
9 17 ms 50 ms 24 ms dns.google [8.8.8.8]

 

Tracing route to www.google.com [172.217.1.4]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 10.0.0.1
2 46 ms 28 ms 51 ms 99.xxx.xx.x
3 33 ms 115 ms 56 ms gi-1-0-0.cmts02.ym.phub.net.cable.rogers.com [66.185.90.25]
4 76 ms 77 ms 12 ms 9015-cgw01.mtnk.asr9k.rmgt.net.rogers.com [209.148.224.177]
5 25 ms 14 ms 69 ms 209.148.233.46
6 29 ms 37 ms 16 ms 72.14.222.87
7 43 ms 15 ms 46 ms 108.170.250.225
8 48 ms 59 ms 26 ms 216.239.35.235
9 29 ms 37 ms 47 ms iad23s25-in-f4.1e100.net [172.217.1.4]

 

Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:

1 1 ms <1 ms 1 ms 10.0.0.1
2 59 ms 24 ms 27 ms 99.xxx.xx.x
3 71 ms 43 ms 18 ms gi-1-0-0.cmts02.ym.phub.net.cable.rogers.com [66.185.90.25]
4 50 ms 45 ms 17 ms 9015-cgw01.mtnk.asr9k.rmgt.net.rogers.com [209.148.224.177]
5 44 ms 38 ms 54 ms 209.148.233.46
6 * * * Request timed out.
7 108 ms 17 ms 34 ms 108.170.250.225
8 16 ms 20 ms 39 ms 216.239.35.235
9 36 ms 29 ms 88 ms dns.google [8.8.8.8]

 

Tracing route to resolver1.opendns.com [208.67.222.222]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.1
2 49 ms 34 ms 110 ms 99.xxx.xx.x
3 112 ms 34 ms 23 ms 66.185.90.29
4 49 ms 44 ms 53 ms 9015-cgw01.ym.rmgt.net.rogers.com [209.148.224.181]
5 74 ms 28 ms 65 ms 209.148.235.218
6 34 ms 33 ms 53 ms opendns.ip4.torontointernetxchange.net [206.108.34.229]
7 30 ms 65 ms 44 ms resolver1.opendns.com [208.67.222.222]

 

Tracing route to resolver1.opendns.com [208.67.222.222]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.1
2 96 ms 34 ms 18 ms 99.xxx.xx.x
3 35 ms 27 ms 100 ms 66.185.90.29
4 65 ms 40 ms 44 ms 9015-cgw01.ym.rmgt.net.rogers.com [209.148.224.181]
5 11 ms 46 ms 43 ms 209.148.235.218
6 69 ms 81 ms 24 ms opendns.ip4.torontointernetxchange.net [206.108.34.229]
7 72 ms 15 ms 90 ms resolver1.opendns.com [208.67.222.222]

Highlighted
Moderator
Moderator
Posts: 1,159

Re: Brutal latency/ping Recently

@TheBings, thank you for running and posting the ping test and traceroute results. We'd like to run additional tests for you. Please reach out to us via PM @CommunityHelps for further assistance :). If you're not familiar with our private messaging system, please click here to learn more :).

 

 

 

RogersZia