My two home servers run three staggered speedtests each every night - around 3am / 4am / 5am. They run so they don't happen at the same time, obviously.Looking over recent results, I can see that my usual 100mbps upload speed has broadly halved since 10th feb. Not just a one-off, but halved across the board, every day, every speedtest, on separate machines. Both ethernet-wired so no wifi flucuations involved.Server 1 graph - https://imgur.com/OZgW3JEServer 2 graph - https://imgur.com/6yxGrQvWhat happened on 10th Feb to cause this? Nothing in my network has changed in this period.

nothing's changed as far as i can see. my max upload speed is still capped at 110000274 bpsmy logs are full of warnings and notices, but nothing new there. it literally always shows those: Time Priority Description01-03-2024 18:53:11noticeGUI Login Status - Login Success from LAN interface01-03-2024 17:57:54warningDBC-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;01-03-2024 17:57:54noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;01-03-2024 17:56:08warningDBC-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;01-03-2024 17:56:08noticeUS 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;01-03-2024 17:55:13warningDBC-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;01-03-2024 17:55:13noticeUS 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;01-03-2024 17:20:31criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;01-03-2024 16:48:27noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;01-03-2024 16:48:27warningDBC-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;01-03-2024 16:33:29warningDBC-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;01-03-2024 16:33:29noticeUS 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;01-03-2024 16:18:44noticeCM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;01-03-2024 16:15:23noticeCM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;01-03-2024 16:04:27noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;01-03-2024 16:04:27warningDBC-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;01-03-2024 14:55:42noticeUS 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;01-03-2024 14:55:42warningDBC-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;01-03-2024 14:20:33noticeCM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;01-03-2024 14:14:10noticeCM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;01-03-2024 14:12:02noticeCM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;01-03-2024 14:09:52noticeCM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;01-03-2024 12:23:32warningTCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;01-03-2024 12:22:32noticeUS 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;01-03-2024 12:22:32warningDBC-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;01-03-2024 12:22:32criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;01-03-2024 12:22:27noticeREGISTRATION COMPLETE - Waiting for Operational status01-03-2024 12:22:27warningDynamic Range Window violation01-03-2024 12:22:27warningRNG-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;01-03-2024 12:22:26warningTCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;01-03-2024 12:22:22criticalNo Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;01-03-2024 12:22:14warningRNG-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;01-03-2024 12:22:14warningDynamic Range Window violationTime Priority Description01-03-2024 18:53:11noticeGUI Login Status - Login Success from LAN interface01-03-2024 17:57:54warningDBC-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;01-03-2024 17:57:54noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;01-03-2024 17:56:08warningDBC-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;01-03-2024 17:56:08noticeUS 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;01-03-2024 17:55:13warningDBC-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;01-03-2024 17:55:13noticeUS 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;01-03-2024 17:20:31criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;01-03-2024 16:48:27noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;01-03-2024 16:48:27warningDBC-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;01-03-2024 16:33:29warningDBC-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;01-03-2024 16:33:29noticeUS 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;01-03-2024 16:18:44noticeCM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;01-03-2024 16:15:23noticeCM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;01-03-2024 16:04:27noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;01-03-2024 16:04:27warningDBC-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;01-03-2024 14:55:42noticeUS 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;01-03-2024 14:55:42warningDBC-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;01-03-2024 14:20:33noticeCM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;01-03-2024 14:14:10noticeCM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;01-03-2024 14:12:02noticeCM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;01-03-2024 14:09:52noticeCM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;01-03-2024 12:23:32warningTCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;01-03-2024 12:22:32noticeUS 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;01-03-2024 12:22:32warningDBC-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;01-03-2024 12:22:32criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;01-03-2024 12:22:27noticeREGISTRATION COMPLETE - Waiting for Operational status01-03-2024 12:22:27warningDynamic Range Window violation01-03-2024 12:22:27warningRNG-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;01-03-2024 12:22:26warningTCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;01-03-2024 12:22:22criticalNo Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;01-03-2024 12:22:14warningRNG-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;01-03-2024 12:22:14warningDynamic Range Window violation

How about the stats on the upstream channels?

3.0 Upstream channelsChannel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID 049600000475120QAM 64114310000046.85120QAM 64223660000046.85120QAM 64333010000047.35120QAM 64442360000047.55120QAM 6453.0 Upstream channelsChannel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts 0ATDMA03001ATDMA03202ATDMA03103ATDMA03004ATDMA03103.1 Upstream channelsChannel Channel Width (MHz) Power (dBmV) FFT Type Modulation 61041.22KQAM 2563.1 Upstream channelsChannel Channel Type Number of Active Subcarriers First Active Subcarrier (Hz) T3 Timeouts T4 Timeouts 6OFDMA2007400000000

Looks ok to me, other than the timeouts.

Upload speed has halved after 10th Feb - What happened on that date?

Client62

Alessandro Volta

2 years ago

Is there a street level fault ?.. call 0800 561 0061 to find out.

Is there an Upstream connection modulation rate or hard error issue ?

Has the configuration of the Hub unexpectedly changed to a lower Upstream Max Traffic Rate ?

chrisbm

On our wavelength

2 years ago

nothing's changed as far as i can see. my max upload speed is still capped at 110000274 bps

my logs are full of warnings and notices, but nothing new there. it literally always shows those:

Time Priority Description

01-03-2024 18:53:11	notice	GUI Login Status - Login Success from LAN interface
01-03-2024 17:57:54	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;
01-03-2024 17:57:54	notice	US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 13.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
01-03-2024 17:56: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;
01-03-2024 17:56:08	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;
01-03-2024 17:55:13	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;
01-03-2024 17:55:13	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;
01-03-2024 17:20:31	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
01-03-2024 16:48:27	notice	US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 13.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
01-03-2024 16:48:27	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;
01-03-2024 16:33:29	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;
01-03-2024 16:33:29	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;
01-03-2024 16:18:44	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
01-03-2024 16:15:23	notice	CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
01-03-2024 16:04:27	notice	US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
01-03-2024 16:04:27	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;
01-03-2024 14:55:42	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;
01-03-2024 14:55:42	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;
01-03-2024 14:20:33	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
01-03-2024 14:14:10	notice	CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
01-03-2024 14:12:02	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
01-03-2024 14:09:52	notice	CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
01-03-2024 12:23:32	warning	TCS Partial Service;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
01-03-2024 12:22:32	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;
01-03-2024 12:22:32	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;
01-03-2024 12:22:32	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
01-03-2024 12:22:27	notice	REGISTRATION COMPLETE - Waiting for Operational status
01-03-2024 12:22:27	warning	Dynamic Range Window violation
01-03-2024 12:22:27	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;
01-03-2024 12:22:26	warning	TCS Partial Service;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
01-03-2024 12:22:22	critical	No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
01-03-2024 12:22:14	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;
01-03-2024 12:22:14	warning	Dynamic Range Window violation

Time Priority Description

01-03-2024 18:53:11	notice	GUI Login Status - Login Success from LAN interface
01-03-2024 17:57:54	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;
01-03-2024 17:57:54	notice	US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 13.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
01-03-2024 17:56: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;
01-03-2024 17:56:08	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;
01-03-2024 17:55:13	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;
01-03-2024 17:55:13	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;
01-03-2024 17:20:31	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
01-03-2024 16:48:27	notice	US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 13.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
01-03-2024 16:48:27	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;
01-03-2024 16:33:29	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;
01-03-2024 16:33:29	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;
01-03-2024 16:18:44	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
01-03-2024 16:15:23	notice	CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
01-03-2024 16:04:27	notice	US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
01-03-2024 16:04:27	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;
01-03-2024 14:55:42	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;
01-03-2024 14:55:42	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;
01-03-2024 14:20:33	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
01-03-2024 14:14:10	notice	CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
01-03-2024 14:12:02	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
01-03-2024 14:09:52	notice	CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
01-03-2024 12:23:32	warning	TCS Partial Service;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
01-03-2024 12:22:32	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;
01-03-2024 12:22:32	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;
01-03-2024 12:22:32	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
01-03-2024 12:22:27	notice	REGISTRATION COMPLETE - Waiting for Operational status
01-03-2024 12:22:27	warning	Dynamic Range Window violation
01-03-2024 12:22:27	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;
01-03-2024 12:22:26	warning	TCS Partial Service;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
01-03-2024 12:22:22	critical	No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
01-03-2024 12:22:14	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;
01-03-2024 12:22:14	warning	Dynamic Range Window violation

carl_pearce
Superstar
2 years ago
How about the stats on the upstream channels?
- chrisbm
  On our wavelength
  2 years ago
  3.0 Upstream channels
  Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
  0 49600000 47 5120 QAM 64 1
  1 43100000 46.8 5120 QAM 64 2
  2 36600000 46.8 5120 QAM 64 3
  3 30100000 47.3 5120 QAM 64 4
  4 23600000 47.5 5120 QAM 64 5
  3.0 Upstream channels
  Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
  0 ATDMA 0 3 0 0
  1 ATDMA 0 3 2 0
  2 ATDMA 0 3 1 0
  3 ATDMA 0 3 0 0
  4 ATDMA 0 3 1 0
  3.1 Upstream channels
  Channel Channel Width (MHz) Power (dBmV) FFT Type Modulation
  6 10 41.2 2K QAM 256
  3.1 Upstream channels
  Channel Channel Type Number of Active Subcarriers First Active Subcarrier (Hz) T3 Timeouts T4 Timeouts
  6 OFDMA 200 74000000 0 0
carl_pearce
Superstar
2 years ago
Looks ok to me, other than the timeouts.
- chrisbm
  On our wavelength
  2 years ago
  indeed. it's clear from the data that something suddenly changed across the board on 10th Feb and has stayed that way ever since
  nothing in my network changed, and the download speed is unaffected, which suggests to me it's someting external
Client62
Alessandro Volta
2 years ago
Something has changed, problems are solved with facts not assumptions.

If you have a Hub 5, are you affected by the recent firmware LG-RDK_7.6.15-2306.5 that has affected the 2.5Gb/s port ? https://community.virginmedia.com/t5/Tech-Chatter/Hub-5-Firmware-Upgrade/td-p/5480079

With the VM Hub in Router mode use the link below to confirm the service speed to / from the Hub:
https://www.samknows.com/realspeed/
Once the test begins click on: Run full test to see all the stats.
It only take a short time and will answer the question of is this a VM service speed issue.
- chrisbm
  On our wavelength
  2 years ago
  Client62 wrote:
  If you have a Hub 5, are you affected by the recent firmware LG-RDK_7.6.15-2306.5 that has affected the 2.5Gb/s port ? https://community.virginmedia.com/t5/Tech-Chatter/Hub-5-Firmware-Upgrade/td-p/5480079
  Ah now that could be interesting, I had no idea there was an update.
  I run my hub 5 in modem mode and have an orbi router and mesh connected to the 2.5G port on the hub.
  The two affected machines are wired, as I mentioned. One directly into the orbi router and the other also to the orbi router but via a switch.
  The macbook I'm typing this on right now reaches close to 100mbps upload when testing, and that's on wifi to the orbi router.
  So it seems to be only the cabled machines having the issue, which makes sense with some of the comments in that thread. How to fix it though? I have no idea.
Client62
Alessandro Volta
2 years ago
If the Macbook reaches close to 100 on Wi-Fi, the network link from the Hub 5 to the Orbi also reaches close to 100 Mb/s of Upstream which is as expected.

The route from the Orbi via the Switch to the servers is the segment that only reaches 50 Mb/s on Upstream.
- chrisbm
  On our wavelength
  2 years ago
  not quite. as i mentioned, one of the machine is wired directly into the orbi and the other is wired via a switch, so a switch isn't a common factor here. Both machines were happily reaching 100mpbs up as you can see from my original data, one direct and one indirect. The orbi is connected to the hub 5 via the 2.5g port.
  However, the fact that wifi will reach 100 up is baffling and it would suggest somehow all the ethernet ports on the orbi degraded to half speed at exactlyn the same time. but that seems unlikley?
  Something changed on or around 10th Feb. That thread referring to a firmware update around that date, and mentioning issues with the 2.5g port seems a bit too...coincidental? Especially when considering not a single thing in my network infrastructure has changed and it's all been working perfectly for as long as i can recall.
chrisbm
On our wavelength
2 years ago
lol so, I'm in no way a conspiracy theorist right.. but every single day since mid-feb my upload speed has halved. Then yesterday evening I post this thread, the speedtests ran overnight as usual, and suddenly these results for each server:
100mbps upload again, out of nowhere, with precisely zero change in my network environment.
legacy1
Alessandro Volta
2 years ago
Connect by wire to the hub without a router and in modem mode and test speed
- carl_pearce
  Superstar
  2 years ago
  legacy1 wrote:
  Connect by wire to the hub without a router and in modem mode and test speed
  What exactly is that going to achieve when speeds have returned to normal?
  - jbrennand
    Very Insightful Person
    2 years ago
    Looks to me like VM were doing (unannounced) changes to their network. They often do that in the wee small hours but it usually only runs for a few days ... but they may have extended it in your area?
    Next time check on the Service Status number - 0800 561 0061 - which usually gives the most up to date info. and tells you of more local issues and fix estimates, down to street cab/ postcode level - and see if anything is being reported on there
Lisa_CC
Moderator
2 years ago
Hello,

A gentle reminder to please keep replies polite, respectful and relevant, some posts have been removed

Thanks,

Lisa
- chrisbm
  On our wavelength
  2 years ago
  lmao who got upset over my upload speed?
  - carl_pearce
    Superstar
    2 years ago
    chrisbm wrote:
    lmao who got upset over my upload speed?
    
    Not upset, just pointing out posts that aren't helpful.

Forum Discussion

Upload speed has halved after 10th Feb - What happened on that date?

Related Content

emails @blueyonder.co.uk. What's happening?

Upgrade to 360 not happening

Upgrade not happened yet

Download and Upload Speeds

Email account locked, just had this happen out of the blue.

0	49600000	47	5120	QAM 64	1
1	43100000	46.8	5120	QAM 64	2
2	36600000	46.8	5120	QAM 64	3
3	30100000	47.3	5120	QAM 64	4
4	23600000	47.5	5120	QAM 64	5

0	ATDMA	3	0
1	ATDMA	3	2
2	ATDMA	3	1
3	ATDMA	3	0
4	ATDMA	3	1