on 03-05-2022 18:47
Hey I'm getting major packet loss spikes:
BQM monitor: https://www.thinkbroadband.com/broadband/monitoring/quality/share/f68d01995f6dfc458a57fdb0a95f6a9b0b...
Downstream:
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
25 | 331000000 | -1.700001 | 40.366287 | QAM256 | 25 |
1 | 139000000 | 1.200001 | 40.366287 | QAM256 | 1 |
2 | 147000000 | 1.000000 | 40.366287 | QAM256 | 2 |
3 | 155000000 | 0.900002 | 40.946209 | QAM256 | 3 |
4 | 163000000 | 0.799999 | 40.366287 | QAM256 | 4 |
5 | 171000000 | 0.500000 | 40.366287 | QAM256 | 5 |
6 | 179000000 | 0.400002 | 40.366287 | QAM256 | 6 |
7 | 187000000 | 0.400002 | 40.366287 | QAM256 | 7 |
8 | 195000000 | 0.200001 | 40.946209 | QAM256 | 8 |
9 | 203000000 | 0.000000 | 40.946209 | QAM256 | 9 |
10 | 211000000 | 0.099998 | 40.946209 | QAM256 | 10 |
11 | 219000000 | -0.099998 | 40.946209 | QAM256 | 11 |
12 | 227000000 | -0.200001 | 40.366287 | QAM256 | 12 |
13 | 235000000 | 0.000000 | 40.946209 | QAM256 | 13 |
14 | 243000000 | -0.700001 | 40.366287 | QAM256 | 14 |
15 | 251000000 | -1.099998 | 40.366287 | QAM256 | 15 |
16 | 259000000 | -1.000000 | 40.366287 | QAM256 | 16 |
17 | 267000000 | -1.299999 | 40.366287 | QAM256 | 17 |
18 | 275000000 | -1.200001 | 40.366287 | QAM256 | 18 |
19 | 283000000 | -1.599998 | 40.946209 | QAM256 | 19 |
20 | 291000000 | -1.700001 | 40.946209 | QAM256 | 20 |
21 | 299000000 | -2.000000 | 40.366287 | QAM256 | 21 |
22 | 307000000 | -1.799999 | 40.366287 | QAM256 | 22 |
23 | 315000000 | -1.700001 | 40.946209 | QAM256 | 23 |
24 | 323000000 | -1.500000 | 38.983261 | QAM256 | 24 |
26 | 339000000 | -1.900002 | 40.366287 | QAM256 | 26 |
27 | 347000000 | -2.099998 | 40.366287 | QAM256 | 27 |
28 | 355000000 | -2.200001 | 38.983261 | QAM256 | 28 |
29 | 363000000 | -2.400002 | 40.366287 | QAM256 | 29 |
30 | 371000000 | -2.700001 | 38.983261 | QAM256 | 30 |
31 | 379000000 | -2.900002 | 40.946209 | QAM256 | 31 |
Channel Lock Status RxMER (dB) Pre RS Errors Post RS Errors
25 | Locked | 40.366287 | 0 | 0 |
1 | Locked | 40.366287 | 0 | 0 |
2 | Locked | 40.366287 | 0 | 0 |
3 | Locked | 40.946209 | 0 | 0 |
4 | Locked | 40.366287 | 0 | 0 |
5 | Locked | 40.366287 | 0 | 0 |
6 | Locked | 40.366287 | 0 | 0 |
7 | Locked | 40.366287 | 0 | 0 |
8 | Locked | 40.946209 | 0 | 0 |
9 | Locked | 40.946209 | 0 | 0 |
10 | Locked | 40.946209 | 0 | 0 |
11 | Locked | 40.946209 | 0 | 0 |
12 | Locked | 40.366287 | 0 | 0 |
13 | Locked | 40.946209 | 0 | 0 |
14 | Locked | 40.366287 | 0 | 0 |
15 | Locked | 40.366287 | 0 | 0 |
16 | Locked | 40.366287 | 0 | 0 |
17 | Locked | 40.366287 | 0 | 0 |
18 | Locked | 40.366287 | 0 | 0 |
19 | Locked | 40.946209 | 0 | 0 |
20 | Locked | 40.946209 | 0 | 0 |
21 | Locked | 40.366287 | 0 | 0 |
22 | Locked | 40.366287 | 0 | 0 |
23 | Locked | 40.946209 | 0 | 0 |
24 | Locked | 38.983261 | 0 | 0 |
26 | Locked | 40.366287 | 0 | 0 |
27 | Locked | 40.366287 | 0 | 0 |
28 | Locked | 38.983261 | 0 | 0 |
29 | Locked | 40.366287 | 0 | 0 |
30 | Locked | 38.983261 | 0 | 0 |
31 | Locked | 40.946209 | 0 | 0 |
on 03-05-2022 18:48
Upstream:
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 60300000 | 44.270599 | 5120 KSym/sec | 64QAM | 1 |
2 | 53700000 | 44.020599 | 5120 KSym/sec | 64QAM | 2 |
3 | 39400000 | 43.270599 | 5120 KSym/sec | 64QAM | 4 |
4 | 46200000 | 43.520599 | 5120 KSym/sec | 32QAM | 3 |
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 | US_TYPE_STDMA | 0 | 0 | 1 | 0 |
2 | US_TYPE_STDMA | 0 | 0 | 0 | 0 |
3 | US_TYPE_STDMA | 0 | 0 | 0 | 0 |
4 | US_TYPE_STDMA | 0 | 0 | 0 | 0 |
Network log:
Time Priority Description
Thu Jan 1 00:01:26 1970 | 3 | No Ranging Response received - T3 time-out; |
Fri Apr 29 16:56:41 2022 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1; |
Fri Apr 29 18:55:30 2022 | 3 | No Ranging Response received - T3 time-out; |
Mon May 2 10:37:37 2022 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option; |
Mon May 2 21:59:10 2022 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1; |
Mon May 2 22:18:08 2022 | 3 | No Ranging Response received - T3 time-out; |
on 03-05-2022 21:51
on 03-05-2022 22:56
Oh so its not just me, its a network wide issue? The packet loss has only started affecting my service in the last few days.
on 03-05-2022 23:02