cancel
Showing results for 
Search instead for 
Did you mean: 

1 GIG how long

nuzikdude
On our wavelength

I got my connection activated last night and since then my speeds have been slower. I wonder how long it took for the 1 gig to activate and be connected properly. Ive done a sam knows real speed test and that goes up and then ends up on 360mb which is some 300 slower than the previous. 
I have issues with Virgin and them not entirely being honest or even answering questions correctly on the phone so help me out here. 

Also what speeds do people get on their phones etc. 

 

1 ACCEPTED SOLUTION

Accepted Solutions

Network LogTime Priority Description
Thu 01/01/1970 00:01:224Missing Mandatory MDD TLV on primary DS Channel;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 01/01/1970 00:01:513No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 14/09/2021 17:38:085MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 14/09/2021 17:41:046SW Download INIT - Via Config file cmreg-vmdg640-bbt076+voc-b.cm
Tue 14/09/2021 17:42:256SW download Successful - Via Config file
Tue 14/09/2021 17:44:555MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 01/01/1970 00:01:223No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 14/09/2021 17:50:315MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 14/09/2021 18:17:414DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 01/01/1970 00:01:193No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 14/09/2021 19:03:375MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 14/09/2021 19:03:475RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 14/09/2021 19:04:026CM-STATUS message sent. Event Type Code: 5; Chan ID: 33; 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 14/09/2021 19:47:434DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 14/09/2021 19:47:454DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 14/09/2021 23:45:033No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 15/09/2021 08:21:505MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 01/01/1970 00:01:203No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 15/09/2021 08:53:495MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 15/09/2021 09:00:335RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 15/09/2021 09:00:556CM-STATUS message sent. Event Type Code: 4; Chan ID: 33; 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;
Wed 15/09/2021 12:19:285MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 15/09/2021 12:48:415RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 15/09/2021 12:48:536CM-STATUS message sent. Event Type Code: 5; Chan ID: 33; 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;
Wed 15/09/2021 15:03:275MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

See where this Helpful Answer was posted

21 REPLIES 21

hortonj88
Fibre optic

Upgrades done over the phone should be activated within minutes, they just push a new config file to your modem and reboot it.

 

Using a mobile to gauge what kind of speeds you're getting isn't optimal.

 

I'm on BT FTTP and I don't get anywhere near my package speed when I test through my phone or any WIFI based connection.

But testing through a wired ethernet connection shows speeds around my quoted package speed.

 

Also keep in mind that you'll never see the full 1000 mbs due to hardware limitations both on your end and with the hub itself.  Gigabit lan usually maxes out at around 930 mbs.



********************************************************
Left Virgin Media in 2020 after being fobbed off one too many times about over utilisation.


Now: BT FTTP 900/110 connected an ASUS RT-AC86U router.


https://www.speedtest.net/result/12098955842.png

Ive tested via the Sam Knows Speed Router thing and that's supposed to go through. 

 

My whole connections have gone slower. 

I figured it should take minutes but the call centre are like 24 hours and you know how helpful these are!

Screenshot_2021-09-15-08-55-53-28_40deb401b9ffe8e1df2f1cc5ba480b12.jpg

Screenshot_2021-09-15-10-13-32-19_40deb401b9ffe8e1df2f1cc5ba480b12.jpgScreenshot_20**:**:**:**:**:**-62_40deb401b9ffe8e1df2f1cc5ba480b12.jpgScreenshot_2021-09-15-10-13-26-12_40deb401b9ffe8e1df2f1cc5ba480b12.jpgScreenshot_2021-09-15-10-13-20-45_40deb401b9ffe8e1df2f1cc5ba480b12.jpgScreenshot_2021-09-15-10-13-17-69_40deb401b9ffe8e1df2f1cc5ba480b12.jpgScreenshot_2021-09-15-10-13-14-26_40deb401b9ffe8e1df2f1cc5ba480b12.jpg

What the router shows

and now im back down to a great 170mbs! nice one VIRGIN. Glad I'm paying for 1gig

3.0 Downstream channelsChannel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
14110000000.337.6QAM2561
24190000000.237.6QAM2562
34270000000.237.4QAM2563
44350000000.737.4QAM2564
54430000000.837.6QAM2565
64510000000.737.4QAM2566
74590000000.537.6QAM2567
84670000000.737.6QAM2568
94750000000.338.6QAM2569
104830000000.938.6QAM25610
114910000000.839QAM25611
124990000000.637.6QAM25612
135070000000.738.6QAM25613
145150000001.538.6QAM25614
155230000001.139QAM25615
16531000000138.6QAM25616
175390000001.239QAM25617
185470000001.539QAM25618
195550000001.139QAM25619
205630000001.138.6QAM25620
215710000001.238.6QAM25621
225790000000.838.6QAM25622
235870000000.639QAM25623
245950000000.939QAM25624
256030000000.138.6QAM25625
26611000000-0.738.6QAM25626
27619000000-0.539QAM25627
28627000000-1.637.4QAM25628
29635000000-2.237.6QAM25629
30643000000-1.737.4QAM25630
31651000000-1.438.6QAM25631


3.0 Downstream channelsChannel Lock Status RxMER (dB) Pre RS Errors Post RS Errors
1Locked37.63627600
2Locked37.63627660
3Locked37.35598800
4Locked37.35598800
5Locked37.63627600
6Locked37.35598800
7Locked37.63627600
8Locked37.63627600
9Locked38.60537700
10Locked38.60537700
11Locked38.98326100
12Locked37.63627600
13Locked38.60537700
14Locked38.60537700
15Locked38.98326100
16Locked38.60537700
17Locked38.98326100
18Locked38.98326100
19Locked38.98326100
20Locked38.60537700
21Locked38.60537780
22Locked38.60537700
23Locked38.98326100
24Locked38.98326100
25Locked38.60537700
26Locked38.60537700
27Locked38.98326100
28Locked37.35598800
29Locked37.63627600
30Locked37.35598800
31Locked38.60537700


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


3.1 Downstream channelsChannel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)
33Locked39-3.12461720

3.0 Upstream channels

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

1 39400000 46.8 5120 KSym/sec 64QAM 4

2 46200000 46.5 5120 KSym/sec 64QAM 3

3 60300000 47.3 5120 KSym/sec 64QAM 1

4 53700000 46.8 5120 KSym/sec 64QAM 2

 

 

3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1 US_TYPE_STDMA 0 0 0 0

2 US_TYPE_STDMA 0 0 0 0

3 US_TYPE_STDMA 0 0 0 0

4 US_TYPE_STDMA 0 0 0 0

 

 

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
28836
Max Traffic Rate
1200000450
Max Traffic Burst
42600
Min Traffic Rate
0


Primary Upstream Service Flow
SFID
28835
Max Traffic Rate
55000270
Max Traffic Burst
42600
Min Traffic Rate
0
Max Concatenated Burst
42600
Scheduling Type
bestEffort

 

Network LogTime Priority Description
Thu 01/01/1970 00:01:224Missing Mandatory MDD TLV on primary DS Channel;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 01/01/1970 00:01:513No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 14/09/2021 17:38:085MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 14/09/2021 17:41:046SW Download INIT - Via Config file cmreg-vmdg640-bbt076+voc-b.cm
Tue 14/09/2021 17:42:256SW download Successful - Via Config file
Tue 14/09/2021 17:44:555MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 01/01/1970 00:01:223No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 14/09/2021 17:50:315MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 14/09/2021 18:17:414DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 01/01/1970 00:01:193No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 14/09/2021 19:03:375MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 14/09/2021 19:03:475RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 14/09/2021 19:04:026CM-STATUS message sent. Event Type Code: 5; Chan ID: 33; 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 14/09/2021 19:47:434DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 14/09/2021 19:47:454DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 14/09/2021 23:45:033No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 15/09/2021 08:21:505MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 01/01/1970 00:01:203No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 15/09/2021 08:53:495MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 15/09/2021 09:00:335RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 15/09/2021 09:00:556CM-STATUS message sent. Event Type Code: 4; Chan ID: 33; 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;
Wed 15/09/2021 12:19:285MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 15/09/2021 12:48:415RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 15/09/2021 12:48:536CM-STATUS message sent. Event Type Code: 5; Chan ID: 33; 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;
Wed 15/09/2021 15:03:275MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;