on 02-07-2022 18:17
Dear all
I seem to have the same issue here as many others do on the forum. Upgraded to a gig service to find my wifi speed at approx 300-400 mbits.
Have done that sam knows and it shows 1gig getting to the router but the wifi speed is 300-400. Even wired, granted on an old laptop is poor
Prior to upgrading my m600 received 900 mbits.
Engineer even came round and replaced all connections, a fresh wifi router and the same exists. Even virgin are saying they can’t identify a problem.
i have read a number of posts and the things that come up are:
- issues with something in the BQM data
- the fact that the hub4 is not compatible for a gig speed ( virgin confirm that hub 4 is compatible with 1gig )
Would appreciate any help at all
Sincerely
sam
on 02-07-2022 18:40
@Spintheverbs wrote:Dear all
I seem to have the same issue here as many others do on the forum. Upgraded to a gig service to find my wifi speed at approx 300-400 mbits.
OK but what speed were you getting on WiFi before you upgraded?
Have done that sam knows and it shows 1gig getting to the router but the wifi speed is 300-400. Even wired, granted on an old laptop is poorWhat speed does it show on the laptop, could the laptop (if old) only have a 100Mb/s interface which would be the limiting factor? Also, importantly, what device are you using on WiFi to measure the speed? Many devices simply can’t connect to WiFI faster than than the 400 or so you mention.
Prior to upgrading my m600 received 900 mbits.
No, something isn’t right here, the M600 has an absolute limit of about 650 Mb/s, it isn’t possible that you were getting 900. If that’s what you were measuring then something had gone seriously askew with the speed test.
Engineer even came round and replaced all connections, a fresh wifi router and the same exists. Even virgin are saying they can’t identify a problem.i have read a number of posts and the things that come up are:
- issues with something in the BQM data
- the fact that the hub4 is not compatible for a gig speed ( virgin confirm that hub 4 is compatible with 1gig )
It is, in fact only the hub 4 and 5 ARE compatible with the 1 Gig tier
Would appreciate any help at all
Sincerely
sam
Responses in blue
on 02-07-2022 19:21
Before upgrading I was getting 400. After upgrading to the 1gig service I noticed multiple errors in my package eg: they forgot to add the the telephone package so they kept on correcting it
After a correction I noticed they had downgraded me to m600 on paper.
Probably at that time after a speed test I noticed for one day my m600 was registering 900 mbits.
Called up to make sure my package was on the 1gig service and that the price was correct. After much stress they sorted it out.
Perhaps the old lap top ( windows laptop) is maxed out at 100. For the wifi test I’m using a mixture of Apple devices:
iPhone 8 plus
Iphone 11
Macbook pro 2014 no Ethernet port
All in all the speed is terrible and I’m finding that things are juddering, dropping out, even zoom calls
Any advice is welcome on how to test this line properly
Thanks
on 02-07-2022 19:23
Ps: before upgrading to the gig I was on the m500 I believe
on 04-07-2022 11:26
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
25 | 330750000 | 0.9 | 38.6 | QAM256 | 25 |
1 | 138750000 | 2.9 | 39 | QAM256 | 1 |
2 | 146750000 | 2.8 | 38.6 | QAM256 | 2 |
3 | 154750000 | 2.8 | 38.6 | QAM256 | 3 |
4 | 162750000 | 2.6 | 39 | QAM256 | 4 |
5 | 170750000 | 2.4 | 38.6 | QAM256 | 5 |
6 | 178750000 | 2.2 | 38.6 | QAM256 | 6 |
7 | 186750000 | 2 | 38.6 | QAM256 | 7 |
8 | 194750000 | 1.8 | 38.6 | QAM256 | 8 |
9 | 202750000 | 1.7 | 38.6 | QAM256 | 9 |
10 | 210750000 | 1.3 | 39 | QAM256 | 10 |
11 | 218750000 | 0.8 | 38.6 | QAM256 | 11 |
12 | 226750000 | 0.6 | 39 | QAM256 | 12 |
13 | 234750000 | 0.6 | 38.6 | QAM256 | 13 |
14 | 242750000 | 0.8 | 38.6 | QAM256 | 14 |
15 | 250750000 | 0.8 | 38.6 | QAM256 | 15 |
16 | 258750000 | 1.1 | 38.6 | QAM256 | 16 |
17 | 266750000 | 2.3 | 39 | QAM256 | 17 |
18 | 274750000 | 2.4 | 38.6 | QAM256 | 18 |
19 | 282750000 | 1.9 | 38.6 | QAM256 | 19 |
20 | 290750000 | 1.6 | 38.6 | QAM256 | 20 |
21 | 298750000 | 1.7 | 38.6 | QAM256 | 21 |
22 | 306750000 | 1.7 | 39 | QAM256 | 22 |
23 | 314750000 | 1.4 | 39 | QAM256 | 23 |
24 | 322750000 | 1.1 | 38.6 | QAM256 | 24 |
26 | 338750000 | 0.9 | 39 | QAM256 | 26 |
27 | 346750000 | 1.1 | 39 | QAM256 | 27 |
28 | 354750000 | 1.1 | 39 | QAM256 | 28 |
29 | 362750000 | 0.9 | 38.6 | QAM256 | 29 |
30 | 370750000 | 0.5 | 38.6 | QAM256 | 30 |
31 | 378750000 | -0.1 | 38.6 | QAM256 | 31 |
Channel Lock Status RxMER (dB) Pre RS Errors Post RS Errors
25 | Locked | 38.605377 | 0 | 0 |
1 | Locked | 38.983261 | 0 | 0 |
2 | Locked | 38.605377 | 0 | 0 |
3 | Locked | 38.605377 | 0 | 0 |
4 | Locked | 38.983261 | 0 | 0 |
5 | Locked | 38.605377 | 0 | 0 |
6 | Locked | 38.605377 | 0 | 0 |
7 | Locked | 38.605377 | 0 | 0 |
8 | Locked | 38.605377 | 0 | 0 |
9 | Locked | 38.605377 | 0 | 0 |
10 | Locked | 38.983261 | 0 | 0 |
11 | Locked | 38.605377 | 0 | 0 |
12 | Locked | 38.983261 | 0 | 0 |
13 | Locked | 38.605377 | 0 | 0 |
14 | Locked | 38.605377 | 0 | 0 |
15 | Locked | 38.605377 | 0 | 0 |
16 | Locked | 38.605377 | 0 | 0 |
17 | Locked | 38.983261 | 0 | 0 |
18 | Locked | 38.605377 | 0 | 0 |
19 | Locked | 38.605377 | 0 | 0 |
20 | Locked | 38.605377 | 0 | 0 |
21 | Locked | 38.605377 | 0 | 0 |
22 | Locked | 38.983261 | 0 | 0 |
23 | Locked | 38.983261 | 0 | 0 |
24 | Locked | 38.605377 | 0 | 0 |
26 | Locked | 38.983261 | 0 | 0 |
27 | Locked | 38.983261 | 0 | 0 |
28 | Locked | 38.983261 | 0 | 0 |
29 | Locked | 38.605377 | 0 | 0 |
30 | Locked | 38.605377 | 0 | 0 |
31 | Locked | 38.605377 | 0 | 0 |
159 | 94 | 4K | 1840 | QAM4096 | 424 |
159 | Locked | 41 | 0.4 | 2042285081 | 0 |
on 04-07-2022 11:27
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 53700000 | 43.5 | 5120 KSym/sec | 64QAM | 2 |
2 | 39400000 | 42.8 | 5120 KSym/sec | 64QAM | 4 |
3 | 46200000 | 42.8 | 5120 KSym/sec | 64QAM | 3 |
4 | 60300000 | 44 | 5120 KSym/sec | 64QAM | 1 |
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 | US_TYPE_STDMA | 0 | 0 | 3 | 0 |
2 | US_TYPE_STDMA | 0 | 0 | 0 | 0 |
3 | US_TYPE_STDMA | 0 | 0 | 0 | 0 |
4 | US_TYPE_STDMA | 0 | 0 | 2 | 0 |
on 04-07-2022 11:28
Time Priority Description
Thu 01/01/1970 00:01:19 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 24/05/2022 09:04:34 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 24/05/2022 09:04:46 | 6 | SW Download INIT - Via Config file 87dsfd;kfoA,.iyewrkldJKDH |
Tue 24/05/2022 09:06:00 | 6 | SW download Successful - Via Config file |
Tue 24/05/2022 09:08:31 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 24/05/2022 09:36:18 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 24/05/2022 09:36:18 | 6 | DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 24/05/2022 10:35:19 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 24/05/2022 10:35:19 | 6 | DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 25/05/2022 10:33:09 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 27/05/2022 22:35:19 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 27/05/2022 22:35:19 | 6 | DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat 28/05/2022 23:07:59 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 31/05/2022 10:35:19 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 31/05/2022 10:35:19 | 6 | DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 31/05/2022 17:00:57 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 03/06/2022 22:35:19 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 03/06/2022 22:35:19 | 6 | DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon 06/06/2022 10:36:59 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon 06/06/2022 17:23:06 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 07/06/2022 23:46:37 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 08/06/2022 19:59:09 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 08/06/2022 19:59:09 | 6 | DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat 11/06/2022 03:56:55 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat 11/06/2022 08:52:38 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 12/06/2022 22:19:21 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 12/06/2022 22:19:21 | 6 | DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 14/06/2022 09:21:39 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 24; 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; |
Thu 16/06/2022 03:39:16 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 16/06/2022 03:39:16 | 6 | DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 19/06/2022 15:39:16 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 19/06/2022 15:39:16 | 6 | DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon 20/06/2022 08:21:48 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 23/06/2022 03:39:16 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 23/06/2022 03:39:16 | 6 | DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 23/06/2022 04:09:16 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 23/06/2022 04:09:16 | 6 | DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 26/06/2022 16:09:16 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 26/06/2022 16:09:16 | 6 | DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 29/06/2022 11:06:40 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 30/06/2022 04:09:16 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 30/06/2022 04:09:16 | 6 | DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 03/07/2022 16:09:16 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 03/07/2022 16:09:16 | 6 | DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
on 06-07-2022 13:24
Good Afternoon @Spintheverbs, thanks for your posts on our Community Forums, and a very warm welcome to you!
Sorry to hear of the speed of the services not being up to scratch, can you confirm if you've been able to open up a speed minimum guarantee complaint?
If so, do you know when this result is due to be issued back to you?
Looking into the stats of the hub, we seem to detect a possible issue with Wi-Fi connections only. Do you have any pieces of equipment located close to the hub that could be re-located or connected via an Ethernet cable?
Kindest regards,
David_Bn
on 02-08-2022 15:37
Hi there
I have opened a minimum speed complaint and they sent a second tech to investigate. He did all the checks and said there was nothing to find
I have yet to get the results of the complaint
I have turned all pieces of equipment which could interfere off to check
Of note the tech mentioned that i should perhaps request a hub5
on 02-08-2022 16:35
same problem here, "upgraded" a couple of weeks ago, now get constand lag/loss and struggle get 10mb download ;/