on 26-10-2022 04:02
having bad packet loss for last couple of days randomly started happening seems to be between 5%-30% area faults show no known faults if someone could take a look at my stats and see if theres anything out of spec.
have got a BQM setup but will post it when its had time to generate
on 26-10-2022 04:03
Cable Modem Status | Online | DOCSIS 3.1 |
Primary downstream channel | Locked | SC-QAM |
DOCSIS 3.0 channels | 31 | 4 |
DOCSIS 3.1 channels | 1 | 0 |
on 26-10-2022 04:03
25 | 331000000 | 6 | 39 | QAM256 | 25 |
6 | 179000000 | 6.6 | 39 | QAM256 | 6 |
7 | 187000000 | 6.8 | 39 | QAM256 | 7 |
8 | 195000000 | 6.8 | 40.4 | QAM256 | 8 |
9 | 203000000 | 7 | 40.4 | QAM256 | 9 |
10 | 211000000 | 7 | 40.4 | QAM256 | 10 |
11 | 219000000 | 7 | 40.4 | QAM256 | 11 |
12 | 227000000 | 7 | 40.4 | QAM256 | 12 |
13 | 235000000 | 7.2 | 40.4 | QAM256 | 13 |
14 | 243000000 | 7.2 | 40.4 | QAM256 | 14 |
15 | 251000000 | 7 | 39 | QAM256 | 15 |
16 | 259000000 | 7.2 | 40.4 | QAM256 | 16 |
17 | 267000000 | 6.9 | 40.4 | QAM256 | 17 |
18 | 275000000 | 6.8 | 39 | QAM256 | 18 |
19 | 283000000 | 7 | 40.4 | QAM256 | 19 |
20 | 291000000 | 7 | 40.4 | QAM256 | 20 |
21 | 299000000 | 6.6 | 40.4 | QAM256 | 21 |
22 | 307000000 | 6 | 40.9 | QAM256 | 22 |
23 | 315000000 | 5.7 | 40.4 | QAM256 | 23 |
24 | 323000000 | 5.8 | 40.4 | QAM256 | 24 |
26 | 339000000 | 6.4 | 40.4 | QAM256 | 26 |
27 | 347000000 | 6.5 | 40.4 | QAM256 | 27 |
28 | 355000000 | 6.4 | 39 | QAM256 | 28 |
29 | 363000000 | 6.6 | 39 | QAM256 | 29 |
30 | 371000000 | 6.3 | 40.4 | QAM256 | 30 |
31 | 379000000 | 5.8 | 39 | QAM256 | 31 |
32 | 387000000 | 5.9 | 40.4 | QAM256 | 32 |
33 | 491000000 | 5.8 | 40.4 | QAM256 | 33 |
34 | 499000000 | 5.7 | 39 | QAM256 | 34 |
35 | 507000000 | 5.5 | 39 | QAM256 | 35 |
36 | 515000000 | 5.8 | 39 | QAM256 | 36 |
25 | Locked | 38.983261 | 0 | 0 |
6 | Locked | 38.983261 | 0 | 0 |
7 | Locked | 38.983261 | 0 | 0 |
8 | Locked | 40.366287 | 0 | 0 |
9 | Locked | 40.366287 | 0 | 0 |
10 | Locked | 40.366287 | 0 | 0 |
11 | Locked | 40.366287 | 0 | 0 |
12 | Locked | 40.366287 | 0 | 0 |
13 | Locked | 40.366287 | 0 | 0 |
14 | Locked | 40.366287 | 0 | 0 |
15 | Locked | 38.983261 | 0 | 0 |
16 | Locked | 40.366287 | 0 | 0 |
17 | Locked | 40.366287 | 0 | 0 |
18 | Locked | 38.983261 | 0 | 0 |
19 | Locked | 40.366287 | 0 | 0 |
20 | Locked | 40.366287 | 0 | 0 |
21 | Locked | 40.366287 | 0 | 0 |
22 | Locked | 40.946209 | 0 | 0 |
23 | Locked | 40.366287 | 0 | 0 |
24 | Locked | 40.366287 | 0 | 0 |
26 | Locked | 40.366287 | 0 | 0 |
27 | Locked | 40.366287 | 0 | 0 |
28 | Locked | 38.983261 | 0 | 0 |
29 | Locked | 38.983261 | 0 | 0 |
30 | Locked | 40.366287 | 0 | 0 |
31 | Locked | 38.983261 | 0 | 0 |
32 | Locked | 40.366287 | 0 | 0 |
33 | Locked | 40.366287 | 0 | 0 |
34 | Locked | 38.983261 | 0 | 0 |
35 | Locked | 38.983261 | 0 | 0 |
36 | Locked | 38.983261 | 0 | 0 |
159 | 96 | 4K | 1880 | QAM4096 | 759 |
159 | Locked | 41 | 6.5 | 2793723 | 0 |
on 26-10-2022 04:04
1 | 23600000 | 32.5 | 5120 KSym/sec | 16QAM | 14 |
2 | 32600000 | 33.5 | 5120 KSym/sec | 32QAM | 13 |
3 | 39400000 | 34 | 5120 KSym/sec | 32QAM | 12 |
4 | 46200000 | 34.5 | 5120 KSym/sec | 32QAM | 11 |
1 | US_TYPE_STDMA | 0 | 0 | 17 | 0 |
2 | US_TYPE_STDMA | 0 | 0 | 0 | 0 |
3 | US_TYPE_STDMA | 0 | 0 | 0 | 0 |
4 | US_TYPE_STDMA | 0 | 0 | 1 | 0 |
on 26-10-2022 04:05
Network access | true |
Maximum Number of CPEs | 1 |
Baseline Privacy | true |
DOCSIS Mode | 3.1 |
Config file | ;kfoA,.iyewrkldJKDHSUBsgv |
SFID | 8954 |
Max Traffic Rate | 1200000450 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
SFID | 8953 |
Max Traffic Rate | 55000270 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
Max Concatenated Burst | 16320 |
Scheduling Type | bestEffort |
Thu 01/01/1970 00:01:26 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 25/10/2022 17:29:15 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 01/01/1970 00:01:25 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 25/10/2022 17:43:24 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 25/10/2022 17:43:34 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 26/10/2022 02:42:13 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 26/10/2022 02:42:35 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
on 26-10-2022 07:37
BQM
https://www.thinkbroadband.com/broadband/monitoring/quality/share/6b3c82d231b856b6aba2e300787bc1c04ddb8efa
on 28-10-2022 08:45
Hey @Exil,
Welcome to the community and thanks for taking the time to post here on the forums.
I’m sorry to hear of the issues that you’re having with your connection at the moment, I have looked into this and cannot see any problems with your connection or in the local area.
How has your connection been working since you last posted, any improvements at all?
Kind Regards,
Steven_L
on 28-10-2022 08:55
hello yes, my connection has since been fixed I'm guessing it was a small area issue that has now been fixed thanks