Saturday - last edited Saturday by RogersJermaine
Hi there. Any idea if this chart is okay, or should I ask for a tech? I sometimes get high latency spikes for a second randomly at times which effects gaming (on wired connection). Thanks.
Channel IDLock StatusFrequencySNRPower LevelModulation
Downstream
|
Channel Bonding Value | ||||||||||||||||||||||||||||||||
16
|
1
|
2
|
3
|
4
|
5
|
6
|
7
|
8
|
9
|
10
|
11
|
12
|
13
|
14
|
15
|
17
|
18
|
19
|
20
|
21
|
22
|
23
|
24
|
25
|
26
|
27
|
28
|
29
|
30
|
31
|
32
|
33
|
34
|
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
|
651 MHz
|
303 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
|
657 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
|
350000000
|
920000000
|
39.0 dB
|
38.8 dB
|
39.7 dB
|
39.7 dB
|
39.6 dB
|
38.6 dB
|
38.5 dB
|
38.5 dB
|
38.5 dB
|
38.5 dB
|
38.6 dB
|
38.3 dB
|
38.6 dB
|
38.8 dB
|
38.7 dB
|
38.8 dB
|
39.1 dB
|
39.1 dB
|
39.2 dB
|
38.7 dB
|
39.1 dB
|
39.2 dB
|
39.2 dB
|
39.2 dB
|
39.3 dB
|
39.3 dB
|
39.1 dB
|
39.2 dB
|
39.3 dB
|
39.3 dB
|
39.8 dB
|
39.7 dB
|
38.1 dB
|
39.3 dB
|
1.9 dBmV
|
0.1 dBmV
|
2.6 dBmV
|
2.5 dBmV
|
2.6 dBmV
|
1.3 dBmV
|
1.2 dBmV
|
1.2 dBmV
|
1.2 dBmV
|
1.2 dBmV
|
1.2 dBmV
|
1.2 dBmV
|
1.3 dBmV
|
1.7 dBmV
|
1.7 dBmV
|
1.9 dBmV
|
1.9 dBmV
|
2.1 dBmV
|
2.2 dBmV
|
2.0 dBmV
|
2.1 dBmV
|
2.2 dBmV
|
2.3 dBmV
|
2.3 dBmV
|
2.5 dBmV
|
2.5 dBmV
|
2.5 dBmV
|
2.7 dBmV
|
2.3 dBmV
|
2.3 dBmV
|
2.8 dBmV
|
2.5 dBmV
|
0.5 dBmV
|
3.1 dBmV
|
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
|
Upstream
|
Channel Bonding Value | |||
5
|
6
|
7
|
8
|
11
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
21 MHz
|
25 MHz
|
32 MHz
|
38 MHz
|
42 MHz
|
2560
|
5120
|
5120
|
5120
|
0
|
44.0 dBmV
|
42.8 dBmV
|
44.0 dBmV
|
45.0 dBmV
|
40.7 dBmV
|
QAM
|
QAM
|
QAM
|
QAM
|
OFDMA
|
TDMA_AND_ATDMA
|
ATDMA
|
ATDMA
|
ATDMA
|
TDMA
|
CM Error Codewords | |||||||||||||||||||||||||||||||||
16
|
1
|
2
|
3
|
4
|
5
|
6
|
7
|
8
|
9
|
10
|
11
|
12
|
13
|
14
|
15
|
17
|
18
|
19
|
20
|
21
|
22
|
23
|
24
|
25
|
26
|
27
|
28
|
29
|
30
|
31
|
32
|
33
|
34
|
2778235650
|
3472494278
|
3473284595
|
3473292308
|
3473298186
|
3473304998
|
3473305290
|
3473373304
|
3473365458
|
3473382003
|
3473349352
|
3473364305
|
3473363595
|
3473373144
|
3473383887
|
3473395228
|
3473394578
|
3402460974
|
3240117521
|
3332507967
|
3307326964
|
3473436225
|
3473436789
|
3473426721
|
3436324262
|
3473441974
|
3473443504
|
3473456021
|
3456150279
|
3473456173
|
3473467379
|
3473472524
|
388809737
|
2778235650
|
1422241967
|
5421
|
1472
|
1514
|
1791
|
531
|
562
|
620
|
532
|
619
|
625
|
650
|
655
|
636
|
628
|
525
|
562
|
18506
|
12952
|
20583
|
14937
|
802
|
1221
|
3875
|
5230
|
491
|
646
|
633
|
5476
|
4799
|
1492
|
1550
|
4106530697
|
1422241967
|
30
|
8402
|
84
|
69
|
93
|
178
|
194
|
165
|
171
|
176
|
165
|
178
|
172
|
154
|
150
|
163
|
150
|
24523
|
31683
|
67322
|
50256
|
178
|
759
|
13234
|
16196
|
137
|
140
|
160
|
8591
|
6394
|
100
|
85
|
7041
|
30
|
***Edited Labels***
yesterday
@andrewr55 Your power levels and SNR, downstream and upstream, all look okay. As for the uncorrectables, you need to look to see at what rate the counts are climbing. If the counters are all steady, the uncorrectables could have been caused by maintenance work done on the node. It's also possible that there are physical problems with the plant, that may only affect your connection or it could be a neighbourhood issue.
Unforrectable codeword errors are packet loss, so you may see burstiness in your traffic as a result of timeouts and data retransmission. Not technically latency but it could be perceived that way. Latency and jitter are caused by other factors.
I would advise rebooting the Gateway first thing in the morning to clear the counters, then check your stats again a few hours later. If you are still seeing a number of uncorrectables after a few hours, and you are still seeing performance issues, then I would certainly contact Rogers and have them investigate. If you send a private message to @CommunityHelps , one of the Mods can check your node stats and test your modem's connection. From there, they may dispatch a tech or they might find that there is already an open ticket to resolve problems in your area.