on 17-11-2021 18:35
Hi,
I have had the Gig1 service for over 6 months and it has been without doubt the best Internet service I've ever had...... until last week that is.
I used to consistently achieve downloads speeds of 1 or even 1.1Gbps according to various speed test sites such as Fast.com
However, for the last 10 days or so I've struggled to get even half that.
I've tried various speed test sites (including this one - https://www.samknows.com/realspeed/) and I sometimes see download speeds less than 400Mbps. This is the result of the Real Sam Knows test I ran just now :
I've also set up a Think Broadband Monitor which is hopefully visible here :
Can anyone help shed light on this ? Is there any other information I should provide ?
Thanks,
Paul
on 18-11-2021 13:56
Additional info from my Hub4
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
25 | 330750000 | 5.699997 | 40.366287 | QAM256 | 25 |
1 | 138750000 | 5.699997 | 40.946209 | QAM256 | 1 |
2 | 146750000 | 5.800003 | 40.946209 | QAM256 | 2 |
3 | 154750000 | 5.699997 | 40.946209 | QAM256 | 3 |
4 | 162750000 | 5.400002 | 40.946209 | QAM256 | 4 |
5 | 170750000 | 5.099998 | 40.946209 | QAM256 | 5 |
6 | 178750000 | 5.000000 | 40.366287 | QAM256 | 6 |
7 | 186750000 | 5.000000 | 40.366287 | QAM256 | 7 |
8 | 194750000 | 5.099998 | 40.946209 | QAM256 | 8 |
9 | 202750000 | 5.199997 | 40.366287 | QAM256 | 9 |
10 | 210750000 | 5.300003 | 40.946209 | QAM256 | 10 |
11 | 218750000 | 5.500000 | 40.946209 | QAM256 | 11 |
12 | 226750000 | 5.500000 | 40.366287 | QAM256 | 12 |
13 | 234750000 | 5.599998 | 40.366287 | QAM256 | 13 |
14 | 242750000 | 5.599998 | 40.946209 | QAM256 | 14 |
15 | 250750000 | 5.699997 | 40.946209 | QAM256 | 15 |
16 | 258750000 | 5.500000 | 40.366287 | QAM256 | 16 |
17 | 266750000 | 5.099998 | 40.946209 | QAM256 | 17 |
18 | 274750000 | 5.099998 | 40.366287 | QAM256 | 18 |
19 | 282750000 | 5.199997 | 40.946209 | QAM256 | 19 |
20 | 290750000 | 5.599998 | 40.946209 | QAM256 | 20 |
21 | 298750000 | 5.800003 | 40.366287 | QAM256 | 21 |
22 | 306750000 | 5.800003 | 40.366287 | QAM256 | 22 |
23 | 314750000 | 5.800003 | 40.946209 | QAM256 | 23 |
24 | 322750000 | 5.699997 | 40.366287 | QAM256 | 24 |
26 | 338750000 | 5.699997 | 40.366287 | QAM256 | 26 |
27 | 346750000 | 5.800003 | 40.366287 | QAM256 | 27 |
28 | 354750000 | 5.800003 | 40.946209 | QAM256 | 28 |
29 | 362750000 | 6.000000 | 40.946209 | QAM256 | 29 |
30 | 370750000 | 5.900002 | 40.946209 | QAM256 | 30 |
31 | 378750000 | 5.800003 | 40.946209 | QAM256 | 31 |
on 18-11-2021 13:57
Channel Lock Status RxMER (dB) Pre RS Errors Post RS Errors
25 | Locked | 40.366287 | 2 | 0 |
1 | Locked | 40.946209 | 0 | 0 |
2 | Locked | 40.946209 | 0 | 0 |
3 | Locked | 40.946209 | 2 | 0 |
4 | Locked | 40.946209 | 0 | 0 |
5 | Locked | 40.946209 | 0 | 0 |
6 | Locked | 40.366287 | 0 | 0 |
7 | Locked | 40.366287 | 1 | 0 |
8 | Locked | 40.946209 | 0 | 0 |
9 | Locked | 40.366287 | 0 | 0 |
10 | Locked | 40.946209 | 0 | 0 |
11 | Locked | 40.946209 | 0 | 0 |
12 | Locked | 40.366287 | 0 | 0 |
13 | Locked | 40.366287 | 0 | 0 |
14 | Locked | 40.946209 | 0 | 0 |
15 | Locked | 40.946209 | 0 | 0 |
16 | Locked | 40.366287 | 0 | 0 |
17 | Locked | 40.946209 | 0 | 0 |
18 | Locked | 40.366287 | 0 | 0 |
19 | Locked | 40.946209 | 0 | 0 |
20 | Locked | 40.946209 | 0 | 0 |
21 | Locked | 40.366287 | 0 | 0 |
22 | Locked | 40.366287 | 0 | 0 |
23 | Locked | 40.946209 | 0 | 0 |
24 | Locked | 40.366287 | 0 | 0 |
26 | Locked | 40.366287 | 0 | 0 |
27 | Locked | 40.366287 | 0 | 0 |
28 | Locked | 40.946209 | 0 | 0 |
29 | Locked | 40.946209 | 0 | 0 |
30 | Locked | 40.946209 | 0 | 0 |
31 | Locked | 40.946209 | 0 | 0 |
159 | 96 | 4K | 1880 | QAM4096 | 759 |
159 | Locked | 42 | 4.1 | 26622071 | 0 |
on 18-11-2021 13:57
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 46200000 | 40.020599 | 5120 KSym/sec | 64QAM | 11 |
2 | 39400000 | 40.020599 | 5120 KSym/sec | 64QAM | 12 |
3 | 53700000 | 39.770599 | 5120 KSym/sec | 64QAM | 10 |
4 | 60300000 | 40.020599 | 5120 KSym/sec | 64QAM | 9 |
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 |
on 18-11-2021 13:58
Network access | true |
Maximum Number of CPEs | 1 |
Baseline Privacy | true |
DOCSIS Mode | 3.1 |
Config file | 69834ncxv9873254k;fg87dsf |
SFID | 852 |
Max Traffic Rate | 1200000450 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
SFID | 851 |
Max Traffic Rate | 55000270 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
Max Concatenated Burst | 16320 |
Scheduling Type | bestEffort |
18-11-2021 15:06 - edited 18-11-2021 15:08
Check with Area faults on 0800 561 0061 or if you have a VM landline 150 as local faults are not shown on VM's status page.
Also post your network log for comment, as I can't see anything amiss with the power levels etc. The "sawtooth" BQM is odd however?
It may be worth while to do a full 60 second pin hole reset on the Hub. Do NOT reboot the Hub afterwards, just let it do it's thing. You will need to make sure the passwords are legible on the bottom of the Hub as these are needed after the reset.
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
on 18-11-2021 15:12
on 18-11-2021 16:55
Hi John,
Thanks for replying. No, I'm not in Modem Mode, just the standard Router Mode. The only device connected to the Hub via ethernet is the PC I'm typing this reply on now. The Hub4 is on my window ledge and the PC has about 3 feet of CAT5 cable connecting it to the Hub.
The odd things is that my results from various speed tests are all over the place whereas they used to be consistently hitting the 1Gbps or even 1.1Gbps mark every single time - this behaviour was consistent for a good 6 months or so and only changed in the last few weeks.
I haven't made any changes which would affect the WAN side of my connection but I have obviously had various Windows (and Dell) updates installed during this time - but that was also true of the previous 6 months so I'm suspecting that there must be a fault on either the Hub or the WAN side of my connection.
What do you think ? Also, and apologies if you can't answer this, can I expect a response on this forum from a representative of VM Tech Support ? I've seen various other threads where people have had a response and even an engineer callout.
Thanks again,
Paul
on 18-11-2021 17:04
Hi,
Thanks for replying.
When I browse to the Hub I can see a 'Check router status' link which I can get to without having to authenticate. There I can see a 'Networklog' tab - is this the log you are referring to ? Is there any difference between this log and the one you get to see if you actually log into the router ?
Thanks,
Paul
Time Priority Description
Mon Sep 20 07:48:55 2021 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon Sep 20 07:48:55 2021 | 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 Sep 23 19:48:56 2021 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu Sep 23 19:48:56 2021 | 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; |
Fri Sep 24 18:42:05 2021 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon Sep 27 07:48:56 2021 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon Sep 27 07:48:56 2021 | 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 Sep 28 03:29:18 2021 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu Sep 30 19:48:57 2021 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu Sep 30 19:48:57 2021 | 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 Sep 30 21:41:56 2021 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon Oct 4 07:48:57 2021 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon Oct 4 07:48:57 2021 | 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 Oct 5 12:37:56 2021 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu Oct 7 19:48:58 2021 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu Oct 7 19:48:58 2021 | 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 Oct 10 04:15:31 2021 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon Oct 11 07:48:59 2021 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon Oct 11 07:48:59 2021 | 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 Oct 14 19:49:00 2021 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu Oct 14 19:49:00 2021 | 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 Oct 16 11:03:21 2021 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon Oct 18 07:49:01 2021 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon Oct 18 07:49:01 2021 | 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 Oct 20 10:44:08 2021 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu Oct 21 19:49:02 2021 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu Oct 21 19:49:02 2021 | 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 Oct 25 07:49:03 2021 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon Oct 25 07:49:03 2021 | 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 Oct 27 16:44:15 2021 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed Oct 27 16:44:36 2021 | 6 | CM-STATUS message sent. Event Type Code: 3; Chan ID: N/A; DSID: 688056; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri Oct 29 11:25:32 2021 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat Oct 30 00:16:52 2021 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat Oct 30 00:16:52 2021 | 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 Oct 30 14:48:34 2021 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon Nov 1 22:33:17 2021 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon Nov 1 22:33:17 2021 | 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 Nov 3 11:32:17 2021 | 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 Nov 7 03:57:05 2021 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun Nov 7 03:57:05 2021 | 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 Nov 7 15:27:34 2021 | 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 Nov 9 15:33:04 2021 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed Nov 10 01:30:21 2021 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed Nov 10 01:30:21 2021 | 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; |
Fri Nov 12 02:49:22 2021 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat Nov 13 13:30:22 2021 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat Nov 13 13:30:22 2021 | 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 Nov 17 01:30:22 2021 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed Nov 17 01:30:22 2021 | 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 Nov 17 09:11:39 2021 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
19-11-2021 14:51 - edited 19-11-2021 14:51
@plynch66 wrote:Hi John,
the PC has about 3 feet of CAT5 cable connecting it to the Hub.
Paul
Two things - do you mean Cat5 cable - that departed on the Ark. Or is it Cat5e? If Cat5 change it now - even if it is Cat5e it might have gone faulty - I would use Cat6a.
Second Dell updates notoriously install things like "SmartByte" which partitions connection speeds. Disable that and see what happens