11-04-2022 10:15 PM - last edited on 11-04-2022 10:40 PM by RogersJermaine
I'm a little tired of this issue to be honest. It's been ongoing for 3 weeks. I've had 2 technicians come out so far. The first technician took out a coaxial splitter, it didn't change much. The issue seems to be worse during around 8-12 at night. It is very random aswell that sometimes support doesn't see any issues at all - When they run their tests, everything seems to come fine, that makes sense since the issue is completely random. I had another technician come today and he changed the router. Issue seemed okay for a bit, until peak hours.
Keep in mind this issue is persistent across all devices connected not just my computer.
Here are some tests I just ran and it is obviously not normal.
Here is a ping test that I ran to roger's dns server off my computer that is connected by ethernet directly to the router. This is at ~9:33pm.
I currently have ignite internet with the white modem
Here's the same test ran again:
After running this test, I decided to change my password so that Only my computer is connected to the network, to test if there is a device that is hogging bandwidth on my local network.
Nothing seemed to change.
This is a ping test to rogers' DNS server again but with only 1 device connected to the network, which is my PC connected via ethernet.
As you can see, the round trip-times are very variable. This is similar to what I get when I try to game. It'll be fine for a minute or two. I'll then see a huge spike for a minute or two. It'll settle down for a minute or two then repeat.
Here is some more information :
IndexLock StatusFrequencySNRPower LevelModulation
Downstream
|
Channel Bonding Value | ||||||||||||||||||||||||||||||||
7
|
8
|
9
|
10
|
2
|
3
|
4
|
5
|
6
|
1
|
11
|
12
|
13
|
14
|
15
|
16
|
17
|
18
|
19
|
20
|
21
|
22
|
23
|
24
|
25
|
26
|
27
|
28
|
29
|
30
|
31
|
32
|
0
|
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
|
591000000
|
597000000
|
603000000
|
609000000
|
849000000
|
855000000
|
861000000
|
579000000
|
585000000
|
279000000
|
615000000
|
621000000
|
633000000
|
639000000
|
645000000
|
651000000
|
657000000
|
663000000
|
669000000
|
675000000
|
681000000
|
687000000
|
693000000
|
699000000
|
705000000
|
711000000
|
717000000
|
723000000
|
825000000
|
831000000
|
837000000
|
843000000
|
|
352800000
|
40.946209
|
40.946209
|
40.946209
|
40.366287
|
40.946209
|
40.946209
|
40.366287
|
40.366287
|
40.366287
|
40.366287
|
40.946209
|
40.946209
|
40.366287
|
40.946209
|
40.946209
|
40.366287
|
40.946209
|
40.946209
|
40.366287
|
40.946209
|
40.946209
|
40.366287
|
40.366287
|
40.946209
|
40.366287
|
40.946209
|
40.946209
|
40.366287
|
40.946209
|
40.366287
|
40.946209
|
40.366287
|
|
42.37 dB
|
4.900002
|
4.699997
|
4.400002
|
4.500000
|
6.099998
|
5.400002
|
5.300003
|
4.500000
|
4.800003
|
1.400002
|
4.300003
|
4.599998
|
4.699997
|
4.699997
|
4.699997
|
4.599998
|
4.699997
|
4.900002
|
4.800003
|
4.599998
|
4.599998
|
4.400002
|
4.300003
|
4.300003
|
4.599998
|
4.800003
|
4.500000
|
4.800003
|
6.699997
|
6.699997
|
6.400002
|
6.099998
|
|
2.599998 dBmV
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
|
OFDM
|
IndexLock StatusFrequencySymbol RatePower LevelModulationChannel Type
Upstream
|
Channel Bonding Value | ||
1
|
2
|
3
|
4
|
Locked
|
Locked
|
Locked
|
Locked
|
38700000
|
21100000
|
32300000
|
25900000
|
5120 KSym/sec
|
2560 KSym/sec
|
5120 KSym/sec
|
5120 KSym/sec
|
39.020599
|
36.010300
|
39.020599
|
39.020599
|
64QAM
|
64QAM
|
64QAM
|
64QAM
|
US_TYPE_ATDMA
|
US_TYPE_TDMA_ATDMA
|
US_TYPE_ATDMA
|
US_TYPE_ATDMA
|
Unerrored CodewordsCorrectable CodewordsUncorrectable Codewords
CM Error Codewords | ||||||||||||||||||||||||||||||||
20907
|
20770
|
20582
|
20441
|
20214
|
19906
|
19756
|
19527
|
19358
|
19074
|
18851
|
18330
|
18186
|
18048
|
17884
|
17677
|
17507
|
17379
|
17176
|
16988
|
16848
|
16703
|
16518
|
16337
|
16220
|
15990
|
15776
|
15646
|
15509
|
15324
|
15199
|
15060
|
63
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
Here's a speedtest:
Here's a traceroute to dns.cp.net.rogers.com
***Edited Labels***
11-04-2022 11:39 PM - edited 11-04-2022 11:39 PM
@Zaffarkhan1962, even using a simple ping, you shouldn't see huge return times from the DNS, and, you should not be seeing lost packets either. So, something is amiss. The problem with using an ICMP ping is that it can be ignored by the server that you're attempting to ping, which could appear as a lot packet. However, I don't recall consistently seeing lost packets when pinging any of Rogers DNS addresses.
For now, can you run the following ping test to the Cable Modem Termination System (CMTS) (trace hop #2):
ping -n 3600 173.33.28.1
That will run for an hour and then terminate. I might ask you to run a much longer test depending on what the results are.
The purpose of running this test is to look for lost packets and high latency between your pc and the CMTS.
Lost packets would imply a cable signal level issue, although, your present signal levels look ok. High latency between the pc and CMTS could imply a cable signal level issue, or more likely, a CMTS with high loads during peak periods, resulting in high latency.
I believe that an hour's worth of results will still remain within the command box limit, so, if you see periods of high return times or numerous lost packets, you should be able to copy the result and send that to @CommunityHelps, looking for further assistance to sort this out.
Fwiw, Pingplotter can be used to record tests such as these, but, Rogers will not accept those results. Text ping results should be accepted. I use Wireshark to record the ping tests and to plot the results. Pingplotter isn't the ideal application to record and display long test results such as 24 hours or longer due to its data compression that the users aren't warned about. Wireshark doesn't compress the data, but, its has its own limitations in terms of the minimal number of time intervals that can be used to display the data.
11-06-2022 01:21 AM
Ping statistics for 173.33.28.1:
Packets: Sent = 3600, Received = 3595, Lost = 5 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 3ms, Maximum = 3538ms, Average = 139ms