Broadband down in dy8 postcode
No broadband in dy8 area affecting me an neighbours so not isolated nothing on status checkers or 0800
Forum Discussion
38 Replies
Well I am in modem mode so you won't be able to have done any checks. I will reply to your message but I thought I still had the ongoing issue from Feb 2023 open with sabrina as she said she would not close it yet but I got cut off....
Thanks Steven for checking in and eventually getting through security checks for everyone else I am now back in router mode this morning and BQM looks like this -
and now for 24 hours +
Hi Fizz,
Thanks for PMing Kath about the issue that has now seemed to have returned 😥
Could you share a bit more information about this here please so we're following our Community standards?Thanks 🤗
Meg
For information after a long time I have eventually got something sorted for the problem above. turns out it may have been a network / cabiniet issue which hopefully is being attended too.
However due to the rules I have come back to here to now say I have had 3 weeks (with a week off in the middle after I had a troublesome pinhole reset where the details for my wifi would not clear when reset) I am experiencing reboots of the hub every day at 230ish am. I believe normally this could be a sign of a failed update which is why I reset in last week but it has come back again now. After the trouble with the pinhole reset could I have a router problem developing? Hopeully someone picks this up soon.
Megan. What do you want to know... my broadband has been fixed so I don't actually have a returning issue as such it is now I have noticed my modem now appears to be rebooting at 2.30am every day. I did a pinhole reset a week ago and had some issues in that I had to do it 5 times as it seemed to retain the SSID and wifi passwords even after holding for two minutes. in the end I had to power off for 10 mins or so and do a pinhole reset from power on to loose previous settings. however it has been ok for a week now but has started rebooting at 2.30 am again since Tuesday. I am presuming (as this happened before hence the pinhole reset) it is either an update failing or work going on but I cannot tell that.
Network log says "Cable Modem Reboot because of - unknown". Everything else is now great gone are the latency problems above, the pre-rs errors are really low and no connection issues or dropped connections or slowness so I re-itterate no issues are present the stats look the same as when I was fixed (because the engineer Sam dillegently made a note of them all) and we are all good here.
The reboots may be ok but I don't want them happening every night again like I had from the 9th to the 17th.
and for anyone interstedmy router stats
3.0 Downstream channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID1 331000000 5 38 QAM 256 25 2 139000000 6.3 38 QAM 256 1 3 163000000 5.8 38 QAM 256 4 4 171000000 5.6 38 QAM 256 5 5 187000000 5.4 38 QAM 256 7 6 195000000 5.5 38 QAM 256 8 7 211000000 5.8 38 QAM 256 10 8 219000000 5.7 38 QAM 256 11 9 227000000 5.6 38 QAM 256 12 10 235000000 5.4 38 QAM 256 13 11 243000000 5.2 38 QAM 256 14 12 251000000 5 38 QAM 256 15 13 259000000 4.9 38 QAM 256 16 14 267000000 4.8 38 QAM 256 17 15 275000000 4.8 38 QAM 256 18 16 283000000 4.8 38 QAM 256 19 17 307000000 4.9 38 QAM 256 22 18 315000000 4.8 38 QAM 256 23 19 339000000 5.2 38 QAM 256 26 20 347000000 5.2 38 QAM 256 27 21 371000000 4.9 38 QAM 256 30 22 379000000 4.9 38 QAM 256 31 23 403000000 4.5 38 QAM 256 34 24 411000000 4.5 38 QAM 256 35 25 435000000 4.4 38 QAM 256 38 26 443000000 4.4 38 QAM 256 39 27 451000000 4.5 38 QAM 256 40 28 467000000 4.1 38 QAM 256 42 29 475000000 4.1 38 QAM 256 43 30 499000000 3.4 38 QAM 256 46 31 507000000 3.2 38 QAM 256 47 32 515000000 3 38 QAM 256 48 3.0 Downstream channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors1 Locked 38 0 0 2 Locked 38 0 0 3 Locked 38 0 0 4 Locked 38 0 0 5 Locked 38 0 0 6 Locked 38 0 0 7 Locked 38 0 0 8 Locked 38 0 0 9 Locked 38 0 0 10 Locked 38 0 0 11 Locked 38 0 0 12 Locked 38 0 0 13 Locked 38 0 0 14 Locked 38 0 0 15 Locked 38 0 0 16 Locked 38 0 0 17 Locked 38 0 0 18 Locked 38 0 0 19 Locked 38 0 0 20 Locked 38 0 0 21 Locked 38 0 0 22 Locked 38 0 0 23 Locked 38 0 0 24 Locked 38 0 0 25 Locked 38 1 0 26 Locked 38 2 0 27 Locked 38 0 0 28 Locked 38 0 0 29 Locked 38 2 0 30 Locked 38 3 0 31 Locked 38 2 0 32 Locked 38 3 0 3.1 Downstream channels
Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)159 190 4K 3736 QAM 4096 148 3.1 Downstream channels
Channel ID Locked Status RxMER Data (dB) PLC Power (dBmV) Corrected errors (Active Profile) Uncorrectable errors (Active Profile)159 Locked 39 4.2 630295006 0 3.0 Upstream channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID0 49600000 46.3 5120 QAM 64 1 1 43100000 46 5120 QAM 64 2 2 36600000 46.3 5120 QAM 64 3 3 30100000 46 5120 QAM 64 4 4 23600000 45.5 5120 QAM 64 5 3.0 Upstream channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts0 ATDMA 0 0 0 0 1 ATDMA 0 0 0 0 2 ATDMA 0 0 0 0 3 ATDMA 0 0 0 0 4 ATDMA 0 0 0 0 3.1 Upstream channels
Channel Channel Width (MHz) Power (dBmV) FFT Type Modulation6 10 40.2 2K QAM 256 3.1 Upstream channels
Channel Channel Type Number of Active Subcarriers First Active Subcarrier (Hz) T3 Timeouts T4 Timeouts6 OFDMA 200 74000000 0 0 Network Log
Time Priority Description24-07-2024 02:40:08 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-07-2024 02:40:08 notice US profile assignment change. US Chan ID: 6; Previous Profile: 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 24-07-2024 02:40:04 notice REGISTRATION COMPLETE - Waiting for Operational status 24-07-2024 02:39:58 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; 24-07-2024 02:39:58 warning Dynamic Range Window violation 24-07-2024 02:39:58 warning RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 24-07-2024 02:39:58 warning REG-RSP-MP 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-07-2024 02:39:58 warning Dynamic Range Window violation 24-07-2024 02:39:58 warning Dynamic Range Window violation 24-07-2024 02:39:58 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; 24-07-2024 02:39:58 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; 24-07-2024 02:39:58 warning Dynamic Range Window violation 24-07-2024 02:39:52 notice DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 24-07-2024 02:39:49 notice TLV-11 - unrecognized OID;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 24-07-2024 02:39:47 warning DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 24-07-2024 02:39:44 notice Honoring MDD; IP provisioning mode = IPv4 24-07-2024 02:39:34 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 24-07-2024 02:39:33 critical Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 24-07-2024 02:39:26 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 24-07-2024 02:39:25 critical Cable Modem Reboot because of - unknown 23-07-2024 02:38:09 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 23-07-2024 02:38:05 critical Cable Modem Reboot because of - unknown 23-07-2024 02:38:05 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; Reboot overnight again
All quiet again now
- David_Bn
Forum Team
Thanks for the update fizz, have any further issues been apparent since your most recent post?
Have you set up a broadband quality monitor at all?
Referring to the hub, there doesn't appear to be any disconnections over the last 10 days..
Thanks,
David_Bn
@David_Bn
<Have you set up a broadband quality monitor at all? > Did you actually read my post and see my signature? and
<Referring to the hub, there doesn't appear to be any disconnections over the last 10 days>
you are wrong...
it rebooted at 2am is on 21st, 23rd, 24th, and 25th with reason as unknown..... and also for whole week a couple of weeks ago which is why I came back and which seem like a disconnection to me!!! and my last post on Saturday states I had not had any reboots for a couple of days and this is still the case..
Rebooting happened again last night. This is rediculous that I was having a problem and even though it was not solved I was still told to revert back to the forum and now still four weeks down the line nobody has actually picked this up other than to suggest I set up a BQM (which I have had for years) and that I have had no disconnections (rebooting at 2am for a month!). It is rediculous that even after 18 months I am still getting problems with my services and nothing has really ever been 'fixed' enough to call stable. You now want to double my contract price for the services I have (and that was at a 'reduced' rate from retentions and I am fed up with all of this now to be honest) come September and all being well with other ISP's I shall be leaving the virgin fold for good I think.
30-07-2024 02:43:04 critical Cable Modem Reboot because of - unknown
25-07-2024 02:08:37 critical Cable Modem Reboot because of - unknown
24-07-2024 02:39:25 critical Cable Modem Reboot because of - unknown
23-07-2024 02:38:05 critical Cable Modem Reboot because of - unknownI don't know if the reboots (reason unknown) are a failed update or work in the area... I did a pinhole reset two / three weeks ago and had many problems with it not resetting fully (retaining information of wifi connections and not resetting the settings properly and not setting wifi security to enabled and not allowing me to either) and eventually after 5 attempts got it to reset. but the reboots have started again for a week then stopped for a couple of days and are now starting again. The problems with pinhole reset have been apparent with this modem since around November last year but it has not been changed or caused issue. So the reboots happening overnight are causing NAS disconnection which then sends me alerts in the middle of the night. every now and then I can handle but not every night. and as for replying to Davids post (Megan) this is now the third reply..
