1Gig service only running at 60Mbps

Question

Hi thereHad 1Gig service installed and new router installed in September, all fine to being with. Now only seeing 60-80Mbps down and anything varying from 10Mbps-100Mbps up. Restarting router has no effect.https://www.thinkbroadband.com/speedtest/1695899013660814055https://www.thinkbroadband.com/speedtest/1701118164417975655https://www.thinkbroadband.com/broadband/monitoring/quality/share/335c72134d8c17a532eb8a78f490ab61ccdd23b8-27-11-2023&nbsp;I am hard wired to the box through CAT6 and a Netgear Router, so running hub bridged in modem mode with wifi off.&nbsp;Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID 04960000040.85120QAM 16114310000040.55120QAM 16223660000040.35120QAM 16333010000040.35120QAM 16442360000040.55120QAM 1693.0 Upstream channelsChannel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts 0ATDMA00001ATDMA00002ATDMA00003ATDMA00004ATDMA00003.1 Upstream channelsChannel Channel Width (MHz) Power (dBmV) FFT Type Modulation 101136.02KQAM 2563.1 Upstream channelsChannel Channel Type Number of Active Subcarriers First Active Subcarrier (Hz) T3 Timeouts T4 Timeouts 10OFDMA2207400000000&nbsp;&nbsp;&nbsp;General ConfigurationNetwork accessMaximum Number of CPEsBaseline PrivacyDOCSIS ModeConfig file Allowed3Enabled3.1cmreg-vmdg660-bbt076+voc-b.cmPrimary Downstream Service FlowSFIDMax Traffic RateMax Traffic BurstMin Traffic RateSFIDMax Traffic RateMax Traffic BurstMin Traffic Rate 42061230000450 bps42600bytes0 bps4208128000 bps3044bytes0 bpsPrimary Upstream Service FlowSFIDMax Traffic RateMax Traffic BurstMin Traffic RateMax Concatenated BurstScheduling TypeSFIDMax Traffic RateMax Traffic BurstMin Traffic RateMax Concatenated BurstScheduling Type 4205110000274 bps42600bytes0 bps42600bytesBest Effort4207128000 bps3044bytes0 bps1522bytesBest Effort&nbsp;&nbsp;Network LogTime Priority Description 27-11-2023 20:46:04noticeREGISTRATION COMPLETE - Waiting for Operational status27-11-2023 20:46:00noticeUS profile assignment change. US Chan ID: 10; Previous Profile: 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;27-11-2023 20:45: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;27-11-2023 20:45:51noticeTLV-11 - unrecognized OID;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;27-11-2023 20:45:48warningDHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;27-11-2023 20:45:46noticeHonoring MDD; IP provisioning mode = IPv427-11-2023 20:45:26criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;27-11-2023 20:45:24criticalCable Modem Reboot because of - Reboot UI24-11-2023 05:23:17criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;24-11-2023 05:23:15criticalCable Modem Reboot because of - unknown12-11-2023 13:26:24criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;12-11-2023 09:41:01criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;12-11-2023 09:41:01criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;12-11-2023 09:40:59criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;12-11-2023 09:40:56criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;12-11-2023 00:30:05criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;11-11-2023 21:22:53criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;11-11-2023 21:22: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;11-11-2023 21:21:58criticalReceived 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;11-11-2023 21:21:58criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;11-11-2023 21:21: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;11-11-2023 21:21:49criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;11-11-2023 21:21:18criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;11-11-2023 21:21: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;11-11-2023 21:20:34criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;11-11-2023 21:20:33criticalReceived 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;11-11-2023 21:18:59criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;11-11-2023 21:18:53criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;11-11-2023 21:18:51criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;06-11-2023 07:52:12critical16 consecutive T3 timeouts while trying to range on upstream channel 8;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;06-11-2023 07:52:12criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;06-11-2023 07:51:04criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

carl_pearce · Answer

Have you checked this site and run the additional tests?

https://www.virginmedia.com/support/help/service-status

It looks like either a local area issue, or a problem with your line (QAM on upstream should be 64. 16 indicates a 'noisy' line).

Check here also (The speed to your HUB over the VM network. Your HUB must be in router mode):

https://samknows.com/realspeed/

Adduxi · Answer

Also check the cables you are using.&nbsp; A "bad" cable can reduce the link speed to 100Mb,&nbsp; Try known good Cat 6 cables where possible.

Huntsekker · Answer

Thanks both, I am looking into your suggested reasons for the slow speed, will feed back once I have reconfigured and run some more tests&nbsp;👍

Lee_R · Answer

Hi Huntsekker thanks for getting back to us.
Sorry to hear you're receiving slower than expected speeds. &nbsp;We've checked our systems from our side and cannot find anything that explains this. &nbsp;I am going send you a private message, so that we can confirm some details. &nbsp;Please keep an eye on your inbox in the top right of your screen &nbsp;Also, have you checked the link that carl_pearce provided to test the speeds going to your hub?
Regards
Lee_R

Forum Discussion

1Gig service only running at 60Mbps

4 Replies

Related Content

City Fibre - up and running

customer service complaint.

New Hub 5 Ethernet ports running slow

Long cable run - install conduit

Signed a new contract yet keeps telling me contract running out

0	49600000	40.8	5120	QAM 16	1
1	43100000	40.5	5120	QAM 16	2
2	36600000	40.3	5120	QAM 16	3
3	30100000	40.3	5120	QAM 16	4
4	23600000	40.5	5120	QAM 16	9

27-11-2023 20:46:04	notice	REGISTRATION COMPLETE - Waiting for Operational status
27-11-2023 20:46:00	notice	US profile assignment change. US Chan ID: 10; Previous Profile: 13; New Profile: 12 13.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
27-11-2023 20:45: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;
27-11-2023 20:45:51	notice	TLV-11 - unrecognized OID;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
27-11-2023 20:45:48	warning	DHCP WARNING - Non-critical field invalid in response ;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
27-11-2023 20:45:46	notice	Honoring MDD; IP provisioning mode = IPv4
27-11-2023 20:45: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;
27-11-2023 20:45:24	critical	Cable Modem Reboot because of - Reboot UI
24-11-2023 05:23:17	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-11-2023 05:23:15	critical	Cable Modem Reboot because of - unknown
12-11-2023 13:26:24	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
12-11-2023 09:41:01	critical	No Ranging Response received - T3 time-out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
12-11-2023 09:41:01	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
12-11-2023 09:40:59	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
12-11-2023 09:40:56	critical	No Ranging Response received - T3 time-out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
12-11-2023 00:30:05	critical	No Ranging Response received - T3 time-out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
11-11-2023 21:22:53	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
11-11-2023 21:22:46	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;
11-11-2023 21:21:58	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;
11-11-2023 21:21:58	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
11-11-2023 21:21: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;
11-11-2023 21:21:49	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
11-11-2023 21:21:18	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
11-11-2023 21:21:18	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;
11-11-2023 21:20: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;
11-11-2023 21:20:33	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;
11-11-2023 21:18:59	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
11-11-2023 21:18:53	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
11-11-2023 21:18:51	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
06-11-2023 07:52:12	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;
06-11-2023 07:52:12	critical	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
06-11-2023 07:51:04	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;

0	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