on 01-11-2023 20:45
Hi,
Ive noticed a dramatic drop in speeds over the past few days. im on the 1GB package and running a speed test on a cabled device im only pulling off 90Mbps this has only started the past few days.
I checked the routers Network log and there does seem to be alot of errors :
01-11-2023 01:31:36 | notice | REGISTRATION COMPLETE - Waiting for Operational status |
01-11-2023 01:31:36 | warning | TCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
01-11-2023 01:30:42 | 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-11-2023 01:30:42 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
01-11-2023 01:30:37 | 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; |
01-11-2023 01:30:26 | warning | DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
01-11-2023 01:30:24 | notice | Honoring MDD; IP provisioning mode = IPv4 |
01-11-2023 01:30:01 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
01-11-2023 01:24:54 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
01-11-2023 01:24:50 | warning | ToD request sent - No Response received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
01-11-2023 01:24:49 | 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; |
01-11-2023 01:24:24 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
01-11-2023 01:24:23 | 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; |
01-11-2023 01:23:22 | 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; |
01-11-2023 01:23:22 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
01-11-2023 01:22:40 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
01-11-2023 01:22:39 | 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; |
01-11-2023 01:21:40 | warning | MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
01-11-2023 01:21:40 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
01-11-2023 01:21:34 | warning | MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
01-11-2023 01:21: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; |
01-11-2023 01:21:33 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
01-11-2023 00:31:04 | 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; |
31-10-2023 20:15:50 | 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; |
31-10-2023 19:12:01 | 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; |
29-10-2023 10:50:01 | critical | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
29-10-2023 10:50:01 | 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; |
29-10-2023 10:48:53 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
25-10-2023 22:37:30 | error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
25-10-2023 17:52:02 | 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; |
25-10-2023 16:48:13 | 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; |
25-10-2023 06:10:06 | 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-11-2023 21:03 - edited 01-11-2023 21:04
Check what this site shows:
https://samknows.com/realspeed/
There have been reported cases where the HUB 5 drops to 10/100 Ethernet speeds, which is a fault.
01-11-2023 22:06 - edited 01-11-2023 22:07
What cabled device is it?
A speed of just under 100 is usually due to one of these..
The ethernet cable has failed" causing it to drop to these speeds - get a new Cat6e cable and test with that.
Check the network card in the device is set to 1Gb and not dropped its setting to 100 - also check the drivers are up to date.
Is there a network switch in the "connection chain"? - if so... remove it and test again - theses do fail too.
Finally, go into the Hub settings and turn off/disable the wifi and also disconnect all ethernet cables from the Hub, except your one device. This ensures that NO other devices are connected
Then test speeds at https://speedtest.samknows.com/ - or https://www.speedtest.net/ - try on 2 different browsers - as Chrome sometimes gives odd results.
If they are still low – boot your device into safe+networking mode - to disable any potentially interfering software - and try again.
There are many posts on here (I have a list of ~30!) where QoS software, anti-virus, unknown/flaky software, old network card drivers, corrupted browsers, bad cables or other connected devices are limiting speeds on tests.
_________________
Report back what these get.
on 03-11-2023 09:01
Having the same issues. Tested on multiple devices, tried wifi from 2 phones, laptop, and ethernet from laptop. Getting as little as 0.5Mbps down with as much as 100Mbps up on the same speed-test.
Started for me about 3 days ago.
Almost certainly a QoS issue. Have an engineer booked, but given my experience with an ongoing transient disconnections issue, I don't have high hopes.
Virgin tend to send out engineers to just replace the hub and mark the issue "resolved" without asking the customer.
I suggest that you start the complaints process now, as early as possible. You have to give Virgin 8 weeks to resolve the issue (they won't) before you can escalate to the ombudsman.
on 03-11-2023 09:18
The OP appears as mentioned above to have a network cable link that has de-rated to 100Mb/s or is crossing a Powerline adaptor or network switch that have 10/100 ports. The effect of this is a significant drop in Download rate and a smaller less obvious drop in Upload rates.
WorseISP - To stand a chance of getting help, create a new thread to report an unrelated problem.
on 05-11-2023 17:43
Hi keiran7210,
Thanks for taking the time to contact us via the Community. It's lovely having you on board with us in the Forums. ⭐
We're sorry to hear you are having issues with your broadband connection. 😔 Our diagnostics on your home network and Hub have not found any issues that could account for the issues you've mentioned. We've run a check on the overall area and there are no open faults which could be affecting you either.
We need to concentrate on ensuring you are getting the correct speed via an ethernet cable first. Make sure you are plugged in to the hub using a Cat 6 cable and can you also check the network card on your laptop or PC to ensure this is 1GB. Once you have checked these, reboot your Laptop or PC into safe mode with networking and doing a speed test via speedtest.net. Please post the results back here 🙂
Thanks,