on 08-12-2022 12:59
Since I've joined in ~June, I have unstable connection. It seems works kind of ok, but during the day I have few seconds connection drops. It sounds as not a big deal, but affects me significantly especially when I am on a video call or similar.
I've had 5 or so engineer visits already, they have replaced all possible connectors and wires in the house. but it seems does not help. For couple few months I have permanent "issues in your postcode affecting your services", I've called technical support several times, they usually promise fix by tomorrow or so but there is no any progress in the fixing the issue. I have BQM installed:
on 24-02-2023 22:04
Still not fixed, just had another ~30 seconds gap. This is very disappointing experience. Could you please suspend the billing until the issue is fully resolved?
Network Log
Time | Priority | Description |
24-02-2023 21:56:05 | warning | DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
24-02-2023 21:55:53 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
24-02-2023 21:55:52 | critical | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
24-02-2023 21:55:52 | critical | 16 consecutive T3 timeouts while trying to range on upstream channel 8;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
24-02-2023 21:51:37 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
on 27-02-2023 14:33
We understand your frustration kan-izh, from checking your connection and equipment there does appear to be some power level issues on your downstream channels, with some errors on your upstream channel. Disconnections wise we can see one late on Friday around 9.50pm which is what you have referred to in your post but none since.
Have you noticed any improvement since that time?
Rob
on 07-03-2023 19:49
on 15-03-2023 21:19
on 17-03-2023 09:58
Another glitch just now:
17-03-2023 09:54:53 | warning | Dynamic Range Window violation |
17-03-2023 09:54:53 | warning | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
17-03-2023 09:54:18 | warning | DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
17-03-2023 09:53:17 | error | DBC-ACK not received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
17-03-2023 09:53:15 | warning | DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
17-03-2023 09:53:15 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
17-03-2023 09:53:13 | warning | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Channel | Frequency (Hz) | Power (dBmV) | Symbol Rate (ksps) | Modulation | Channel ID |
0 | 49600000 | 44.3 | 5120 | QAM 64 | 1 |
1 | 43100000 | 45.3 | 5120 | QAM 64 | 2 |
2 | 36600000 | 46.3 | 5120 | QAM 64 | 3 |
3 | 30100000 | 47.3 | 5120 | QAM 64 | 4 |
4 | 23600000 | 48.8 | 5120 | QAM 64 | 5 |
on 19-03-2023 11:26
Thank you for keeping us updated kan-izh.
I have taken a look on our side and it does indicate an engineer visit may help improve the issue.
I will private message you now to confirm your details.
^Martin