cancel
Showing results for 
Search instead for 
Did you mean: 

1Gig service only running at 60Mbps

Huntsekker
Tuning in

Hi there

Had 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/1695899013660814055

https://www.thinkbroadband.com/speedtest/1701118164417975655

https://www.thinkbroadband.com/broadband/monitoring/quality/share/335c72134d8c17a532eb8a78f490ab61cc... 

I am hard wired to the box through CAT6 and a Netgear Router, so running hub bridged in modem mode with wifi off.

 

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
04960000040.85120QAM 161
14310000040.55120QAM 162
23660000040.35120QAM 163
33010000040.35120QAM 164
42360000040.55120QAM 169

3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
0ATDMA0000
1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA0000

3.1 Upstream channels

Channel Channel Width (MHz) Power (dBmV) FFT Type Modulation
101136.02KQAM 256

3.1 Upstream channels

Channel Channel Type Number of Active Subcarriers First Active Subcarrier (Hz) T3 Timeouts T4 Timeouts
10OFDMA2207400000000

 

 

 

General Configuration

Network accessMaximum Number of CPEsBaseline PrivacyDOCSIS ModeConfig file
Allowed
3
Enabled
3.1
cmreg-vmdg660-bbt076+voc-b.cm

Primary Downstream Service Flow

SFIDMax Traffic RateMax Traffic BurstMin Traffic RateSFIDMax Traffic RateMax Traffic BurstMin Traffic Rate
4206
1230000450 bps
42600bytes
0 bps
4208
128000 bps
3044bytes
0 bps

Primary Upstream Service Flow

SFIDMax Traffic RateMax Traffic BurstMin Traffic RateMax Concatenated BurstScheduling TypeSFIDMax Traffic RateMax Traffic BurstMin Traffic RateMax Concatenated BurstScheduling Type
4205
110000274 bps
42600bytes
0 bps
42600bytes
Best Effort
4207
128000 bps
3044bytes
0 bps
1522bytes
Best Effort

 

 

Network Log

Time Priority Description
27-11-2023 20:46:04noticeREGISTRATION COMPLETE - Waiting for Operational status
27-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 = IPv4
27-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 UI
24-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 - unknown
12-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;
4 REPLIES 4

carl_pearce
Wise owl

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
Very Insightful Person
Very Insightful Person

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

I'm a Very Insightful Person, I'm here to share knowledge, I don't work for Virgin Media. Learn more

Have I helped? Click Mark as Helpful Answer or use Kudos to say thanks

Huntsekker
Tuning in

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 👍

Hi @Huntsekker thanks for getting back to us.

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

Regards

Lee_R