Very low upstream speed Hub 5,wired and wireless

[Reidos]

Guys, first post be gentle.

The last few days I'm getting very low to occasionally zero upstream speeds both on wired and wireless.

Hub is in modem mode and i have had my existing set up for a number of months.

Below is lifted from the Hub, tried various power downs, cable security etc to no avail.

Earlier it cut of completely, any assistance appreciated.

Cheers

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

0	60300000	36.3	5120	QPSK	5
1	53700000	36.3	5120	QPSK	6
2	46200000	36.5	5120	QPSK	7
3	39400000	36.8	5120	QPSK	8

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

0	ATDMA	0	0	17	0
1	ATDMA	0	0	24	0
2	ATDMA	0	0	16	0
3	ATDMA	0	0	14	0

Network Log

Time Priority Description

14-03-2023 18:49:24	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
14-03-2023 18:49:01	notice	REGISTRATION COMPLETE - Waiting for Operational status
14-03-2023 18:48:54	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;
14-03-2023 18:48:51	notice	TLV-11 - unrecognized OID;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
14-03-2023 18:48:48	warning	DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
14-03-2023 18:48:46	notice	Honoring MDD; IP provisioning mode = IPv4
14-03-2023 18:48:31	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
14-03-2023 18:48:24	critical	DHCP FAILED - Request sent, No response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
14-03-2023 18:48:20	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
14-03-2023 18:46:22	critical	DHCP FAILED - Discover sent, no offer received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
14-03-2023 18:46:19	notice	Honoring MDD; IP provisioning mode = IPv4
14-03-2023 18:46:12	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
14-03-2023 18:46:02	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
14-03-2023 18:32:05	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
14-03-2023 18:31:22	critical	TFTP failed - configuration file NOT FOUND;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
14-03-2023 18:31:17	warning	ToD request sent - No Response received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
14-03-2023 18:31:16	warning	DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
14-03-2023 18:31:01	critical	DHCP FAILED - Request sent, No response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
14-03-2023 18:30:52	notice	Honoring MDD; IP provisioning mode = IPv4
14-03-2023 18:30:50	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
14-03-2023 18:30:48	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
14-03-2023 18:30:41	critical	DHCP FAILED - Discover sent, no offer received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
14-03-2023 18:29:57	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
14-03-2023 18:29:36	critical	DHCP FAILED - Discover sent, no offer received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
14-03-2023 18:28:40	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
14-03-2023 18:27:32	critical	DHCP FAILED - Discover sent, no offer received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
14-03-2023 18:27:28	notice	Honoring MDD; IP provisioning mode = IPv4
14-03-2023 18:27:20	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
14-03-2023 18:27:09	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
14-03-2023 18:27:08	warning	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
14-03-2023 18:26:56	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
14-03-2023 18:26:54	critical	DHCP FAILED - Discover sent, no offer received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

[legacy1]

You have bad upstream you need someone round to fix it.

[jem101]

Oh now come on, we’re always gentle, well most of us anyway!

You have a cable fault, look at the very first table you posted, the modulation being all QPSK is a sign of the hub not being able to communicate properly with the CMTS (that’s the big device at the far end of the cable) due to excessive interference or noise being introduced. And the most likely source of noise is a bad cable joint.

Probably this will require a tech visit to find the issue, but in the meantime, what you can do is to start at the hub and systematically trace the cables back from it all the way to the ‘omnibox’ on the outside front wall and just check that all the connections are good, not become loose and no obvious signs of damage to the cable. The connections really only need to be ‘finger tight’, it’s sometimes best to disconnect and then reconnect them!

Failing that and finding something obviously wrong then, alas, you’ll need to brave the VM customer service provision and try to get them to agree to send someone out and not just opt for the much cheaper, ‘turn it off and on again and wait 15 minutes’!

[Reidos]

Thanks for the tip, I'll remove/reconnect all the connections and then check the hub to compare both tables . 

[Reidos]

Updated table after disconnecting then reconnecting all relevant cables 

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

0	60300000	36	5120	QPSK	5
1	53700000	36	5120	QPSK	6
2	46200000	36.3	5120	QPSK	7
3	39400000	36.5	5120	QPSK	8

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

0	ATDMA	0	0	0	0
1	ATDMA	0	0	7	0
2	ATDMA	0	0	0	0
3	ATDMA	0	0	0	0

Network Log

TimePriorityDescription15-03-2023 18:20:13noticeCM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;15-03-2023 18:15:51noticeCM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;15-03-2023 18:11:12noticeCM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;15-03-2023 18:10:31criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;15-03-2023 18:08:53noticeCM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;15-03-2023 17:56:47noticeREGISTRATION COMPLETE - Waiting for Operational status15-03-2023 17:56:40noticeDS 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;15-03-2023 17:56:39noticeTLV-11 - unrecognized OID;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;15-03-2023 17:56:36criticalDHCP FAILED - Request sent, No response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;15-03-2023 17:56:36warningDHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;15-03-2023 17:56:27noticeHonoring MDD; IP provisioning mode = IPv415-03-2023 17:56:17criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;15-03-2023 17:43:51criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;15-03-2023 17:43:46criticalReceived Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;15-03-2023 17:42:56criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;15-03-2023 17:42:55criticalReceived Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;15-03-2023 17:42:50criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;15-03-2023 17:42:49criticalReceived Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;15-03-2023 17:42:19criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;15-03-2023 17:42:18criticalReceived Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;15-03-2023 17:39:57criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;15-03-2023 17:39:56warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;15-03-2023 17:39:53criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;14-03-2023 18:49:24criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;14-03-2023 18:49:01noticeREGISTRATION COMPLETE - Waiting for Operational status14-03-2023 18:48:54noticeDS 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;14-03-2023 18:48:51noticeTLV-11 - unrecognized OID;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;14-03-2023 18:48:48warningDHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;14-03-2023 18:48:46noticeHonoring MDD; IP provisioning mode = IPv414-03-2023 18:48:31criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;14-03-2023 18:48:24criticalDHCP FAILED - Request sent, No response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;14-03-2023 18:48:20criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1

[Reidos]

There certainly is upstream speed improvement doing a speed test, unsure if the tables reflect that but it still isn't how I reckon it should be.

[Client62]

Check for a known local fault : 0800 561 0061 - seeing QPSK modulation is quite unusual.

[Reidos]

The response on the call suggested an issue but 'as it is very complicated it is taking longer than usual'.

Strange as when i check the postcode online it says the broadband is fine. 

My parents live in the same street and are virgin subscribers so I'll pop round there and check theirs. 

[Client62]

The 0800 561 0061 number is by far the most local focused and up to date.

Half of Colchester has to have blank TV screens and / or an Internet outage before "Check service status" link starts to report issues.

[Martin_N]

Hi Reidos,

Thank you for your post and welcome to the community. 

I'm very sorry to hear about the issue with your broadband service. 

I have taken a look on our side and can see there is a reported intermittent issue in your area. 

The reference for this is: F010545920.

The estimated fix date is: 23 MAR 2023 09:55.

^Martin