cancel
Showing results for 
Search instead for 
Did you mean: 

GIG 1 Slow Speed

worsley
On our wavelength

Hi all, I've posted previously regarding slow speeds. I've gone from the M500 to M600 and now i'm on the the GIG 1 Package. My speeds are averaging around the 500 - 600 mark. I've pulled the plug on the back of the router. I've also removed my ASUS router from the mix and changed the Hub 4 back in to default router. any ideas on how I can improve the speeds? I'm testing wired to the hub via a CAT 7 cable.The day I upgraded I tested it once it had completed and I did see a result of 946 mbps but since then its been no where near this. When I run the test it begins and shoots up to 800-850 ish but then drops and settles around the figures shown

ss (2021-10-17 at 02.41.02).png

9 REPLIES 9

worsley
On our wavelength

3.0 Downstream channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

253307500000.70000138.605377QAM25625
11387500003.50000040.366287QAM2561
21467500003.20000140.366287QAM2562
31547500003.09999840.366287QAM2563
41627500002.50000040.366287QAM2564
51707500002.00000040.366287QAM2565
61787500001.59999840.366287QAM2566
71867500001.59999840.946209QAM2567
81947500001.29999940.366287QAM2568
92027500001.09999840.366287QAM2569
102107500001.40000240.366287QAM25610
112187500001.50000040.366287QAM25611
122267500001.59999840.366287QAM25612
132347500002.00000040.366287QAM25613
142427500002.29999940.366287QAM25614
152507500002.09999840.366287QAM25615
162587500002.40000240.366287QAM25616
172667500002.29999940.366287QAM25617
182747500001.90000240.366287QAM25618
192827500001.90000240.366287QAM25619
202907500001.79999940.366287QAM25620
212987500002.09999840.946209QAM25621
223067500001.79999940.366287QAM25622
233147500001.40000238.983261QAM25623
243227500000.70000138.983261QAM25624
263387500000.79999940.946209QAM25626
273467500000.79999938.983261QAM25627
283547500000.90000238.983261QAM25628
293627500000.79999938.983261QAM25629
303707500000.59999838.983261QAM25630
313787500000.50000038.605377QAM25631



3.0 Downstream channels

Channel Lock Status RxMER (dB) Pre RS Errors Post RS Errors

25Locked38.60537700
1Locked40.36628700
2Locked40.36628700
3Locked40.36628700
4Locked40.36628700
5Locked40.36628700
6Locked40.36628700
7Locked40.94620900
8Locked40.36628700
9Locked40.36628700
10Locked40.36628700
11Locked40.36628700
12Locked40.36628700
13Locked40.36628700
14Locked40.36628700
15Locked40.36628700
16Locked40.36628700
17Locked40.36628700
18Locked40.36628700
19Locked40.36628700
20Locked40.36628700
21Locked40.94620900
22Locked40.36628700
23Locked38.98326100
24Locked38.98326100
26Locked40.94620900
27Locked38.98326100
28Locked38.98326100
29Locked38.98326100
30Locked38.98326100
31Locked38.60537700



3.1 Downstream channelsChannel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)
37964K1880QAM4096759


3.1 Downstream channelsChannel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)
37Locked422.145954240

 

worsley
On our wavelength
3.0 Upstream channelsChannel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
15370000041.7705995120 KSym/sec64QAM6
23940000041.0205995120 KSym/sec64QAM8
36030000042.5205995120 KSym/sec64QAM5
44620000041.0205995120 KSym/sec64QAM7


3.0 Upstream channelsChannel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1US_TYPE_STDMA0000
2US_TYPE_STDMA0000
3US_TYPE_STDMA0000
4US_TYPE_STDMA0000
General Configuration
Network access
true
Maximum Number of CPEs
1
Baseline Privacy
true
DOCSIS Mode
3.1
Config file
cmreg-vmdg640-bbt076+voc-b.cm


Primary Downstream Service Flow
SFID
703632
Max Traffic Rate
1230000450
Max Traffic Burst
42600
Min Traffic Rate
0


Primary Upstream Service Flow
SFID
703631
Max Traffic Rate
55000270
Max Traffic Burst
42600
Min Traffic Rate
0
Max Concatenated Burst
42600
Scheduling Type
bestEffort
Network LogTime Priority Description
Thu Jan 1 00:01:22 19703No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Oct 12 19:59:49 20215MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:01:19 19703No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Oct 12 20:02:53 20215MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Oct 12 20:03:03 20215RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Oct 12 20:03:07 20216SW Download INIT - Via Config file cmreg-vmdg640-bbt076+voc-b.cm
Tue Oct 12 20:03:29 20216CM-STATUS message sent. Event Type Code: 5; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Oct 12 20:04:28 20216SW download Successful - Via Config file
Tue Oct 12 20:07:00 20215MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:01:22 19703No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Oct 12 20:21:02 20215MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Oct 12 20:40:11 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Oct 12 23:15:28 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Oct 16 09:34:54 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:01:21 19703No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Oct 16 15:31:19 20215MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

 

Hi worsley,

Thank you for your post. I'm very sorry to hear about the speed issue you're having. 

I have been able to locate your account and run some checks and it does look like a engineer is required for this.

What I will do is private message you to get some information. 

^Martin

Hi worsley,

We hope you're well. 

To just to keep you updated we have now been advised there is a reported area fault in your area. 

This is an SNR fault. The fault reference is: F009373103. 

The estimated fix date is: 03 NOV 2021 09:00

^Martin

worsley
On our wavelength

Hi thanks for the update Martin, what is an SNR fault exactly and would the effect my speeds? 

Thanks for coming back to us @worsley.

 

A SNR fault means there is an with the signal to noise ratio of the connection in your area, this is most likely caused by some sort of interference on the network in your local area.

 

The problems can be caused by issues with our street equipment such as the cabinets and distribution points but can also be caused by customers equipment. The reason it takes a while to resolve these issues as we have to find the source of the interference on the network.

 

I hope that helps to explain what it means.

 

Regards,

Steven_L

worsley
On our wavelength

Hi Steven,

thanks for that info, hopefully once virgin have found the issue I should see constant speeds. Would this SNR fault impact my speed? I can sit and run test after test etc 1 result I’d see i.e 700 and the next result could be 200 or less but then straight back up to 800 it’s mad how much it’s fluctuating.

 

thanks again for that info  

legacy1
Alessandro Volta
Run a speed test run speed test run!

---------------------------------------------------------------

Thanks for coming back to us @worsley.

 

The SNR could have an impact on the speeds that you're seeing as this affects the stability of your connection.

 

The current estimated fix date and time is still 03/11 @ 9am.

 

Regards,

Steven_L