09-18-2024 11:15 PM - last edited on 09-18-2024 11:22 PM by RogersJermaine
Hello all, I posted about a year ago about constant latency issues and it appears to be back. Again!
Last time I posted, there was a "network enhancement" in my neighbourhood, but now I'm not sure what's happening again. It appears to be throughout the day as well. Doesn't make meetings fun, for sure. I have done the ping tests, traceroute, and have posted my signal levels just in case. Any insight would be really appreciated.
Ping Tests
Sept 16 and Sept 18
Traceroute
Signals
Downstream
|
Channel Bonding Value | ||||||||||||||||||||||||||||||||||
18
|
7
|
8
|
9
|
2
|
3
|
4
|
5
|
6
|
10
|
11
|
12
|
13
|
14
|
15
|
16
|
17
|
1
|
19
|
20
|
21
|
22
|
23
|
24
|
25
|
26
|
27
|
28
|
29
|
30
|
31
|
32
|
0
|
0
|
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
|
663000000
|
591000000
|
597000000
|
603000000
|
849000000
|
855000000
|
861000000
|
579000000
|
585000000
|
609000000
|
615000000
|
621000000
|
633000000
|
639000000
|
645000000
|
651000000
|
657000000
|
627000000
|
669000000
|
675000000
|
681000000
|
687000000
|
693000000
|
699000000
|
705000000
|
711000000
|
717000000
|
723000000
|
825000000
|
831000000
|
837000000
|
843000000
|
|
|
352800000
|
922800000
|
38.605377
|
37.355988
|
37.636276
|
37.355988
|
37.355988
|
37.636276
|
37.355988
|
37.355988
|
37.636276
|
37.636276
|
37.636276
|
37.636276
|
38.983261
|
38.605377
|
38.605377
|
38.983261
|
38.983261
|
38.605377
|
38.983261
|
38.605377
|
38.605377
|
38.605377
|
38.983261
|
38.983261
|
38.605377
|
38.605377
|
37.636276
|
37.636276
|
37.355988
|
37.636276
|
37.636276
|
37.355988
|
|
|
41.05 dB
|
38.04 dB
|
-4.500000
|
-5.500000
|
-5.400002
|
-5.400002
|
-6.700001
|
-6.599998
|
-6.500000
|
-5.799999
|
-5.900002
|
-5.500000
|
-5.000000
|
-4.700001
|
-4.400002
|
-4.599998
|
-4.299999
|
-4.099998
|
-4.200001
|
-4.299999
|
-4.400002
|
-4.400002
|
-4.099998
|
-4.500000
|
-4.599998
|
-4.700001
|
-4.799999
|
-4.799999
|
-5.500000
|
-5.599998
|
-6.799999
|
-6.599998
|
-6.700001
|
-6.700001
|
|
|
-0.700001 dBmV
|
-6.000000 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
|
OFDM
|
Upstream
|
Channel Bonding Value | |||
2
|
4
|
3
|
1
|
10
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
25900000
|
38700000
|
32300000
|
21100000
|
45700000-84950000
|
5120 KSym/sec
|
5120 KSym/sec
|
5120 KSym/sec
|
2560 KSym/sec
|
0 KSym/sec
|
37.770599
|
38.770599
|
38.270599
|
33.760300
|
48.891663
|
64QAM
|
64QAM
|
64QAM
|
64QAM
|
OFDMA
|
US_TYPE_ATDMA
|
US_TYPE_ATDMA
|
US_TYPE_ATDMA
|
US_TYPE_TDMA_ATDMA
|
US_TYPE_OFDMA
|
CM Error Codewords | |||||||||||||||||||||||||||||||||
18
|
7
|
8
|
9
|
2
|
3
|
4
|
5
|
6
|
10
|
11
|
12
|
13
|
14
|
15
|
16
|
17
|
1
|
19
|
20
|
21
|
22
|
23
|
24
|
25
|
26
|
27
|
28
|
29
|
30
|
31
|
32
|
0
|
0
|
3432882676
|
3430151345
|
3430160672
|
3430168706
|
3430174142
|
3430178609
|
3430178736
|
3430182445
|
3430155441
|
3430187841
|
3430192169
|
3430196456
|
3430202031
|
3430197324
|
3430206891
|
3430165485
|
3430211377
|
3430211923
|
3430216433
|
3430220986
|
3430239207
|
3430243755
|
3430225404
|
3430252865
|
3430257431
|
3430261939
|
3430230171
|
3430266876
|
3430248380
|
3430267003
|
3430234751
|
3430271596
|
0
|
0
|
347
|
311
|
150
|
1195
|
290
|
435
|
138
|
1201
|
372
|
350
|
104
|
784
|
9
|
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
|
32
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
***Edited Labels***
09-20-2024 11:27 PM
Hello @Markham1,
Thank you for reaching back out to us here with an update, and we appreciate the troubleshooting steps that you have completed so far. If the issue you had before has returned, we can certainly take a further look into this for you.
Please feel free to send us a private message to @CommunityHelps so we can assist you further. For more information on how our private messaging system works, please check out our blog.
Regards,
RogersJermaine