on 18-08-2022 18:01
I recently upgraded to 1Gb internet which meant Hub3 to Hub4. Previously the internet was rock-solid, no drop-outs, but since moving to the hub4 it's been a nightmare. Hub is running in modem mode to the same Asus router as the hub3 was, and the drop-outs are happening with wired and wireless connections. Any ideas? Some days working from home is just impossible.
Answered! Go to Answer
on 24-08-2022 15:25
Downstream and upstream power levels are out of spec. Unless there is an area fault, you probably need a technician’s visit to rectify.
Check with Area faults on 0800 561 0061 If you have a VM landline 150 this goes down to post code level. You could also try the web page http://www.virginmedia.com/servicechecker although this only covers large outages.
VM will not dispatch any technicians while an area fault exists.
If no faults found:
Call Customer Services on 0345 454 1111/150 if you have a VM landline
on 18-08-2022 18:03
25 | 331000000 | -10.2 | 35.8 | QAM256 | 25 |
1 | 139000000 | -6.6 | 36.6 | QAM256 | 1 |
2 | 147000000 | -6.6 | 37.4 | QAM256 | 2 |
3 | 155000000 | -6.5 | 37.6 | QAM256 | 3 |
4 | 163000000 | -6.5 | 37.4 | QAM256 | 4 |
5 | 171000000 | -6.7 | 37.6 | QAM256 | 5 |
6 | 179000000 | -7.1 | 36.6 | QAM256 | 6 |
7 | 187000000 | -7.4 | 36.6 | QAM256 | 7 |
8 | 195000000 | -7.7 | 37.6 | QAM256 | 8 |
9 | 203000000 | -7.8 | 37.4 | QAM256 | 9 |
10 | 211000000 | -8 | 37.4 | QAM256 | 10 |
11 | 219000000 | -8.1 | 37.4 | QAM256 | 11 |
12 | 227000000 | -7.9 | 37.6 | QAM256 | 12 |
13 | 235000000 | -7.9 | 37.4 | QAM256 | 13 |
14 | 243000000 | -7.6 | 37.4 | QAM256 | 14 |
15 | 251000000 | -8 | 37.4 | QAM256 | 15 |
16 | 259000000 | -7.9 | 36.6 | QAM256 | 16 |
17 | 267000000 | -8.4 | 37.4 | QAM256 | 17 |
18 | 275000000 | -9.1 | 36.6 | QAM256 | 18 |
19 | 283000000 | -8.8 | 36.8 | QAM256 | 19 |
20 | 291000000 | -8.7 | 36.6 | QAM256 | 20 |
21 | 299000000 | -8.1 | 37.4 | QAM256 | 21 |
22 | 307000000 | -8.6 | 36.6 | QAM256 | 22 |
23 | 315000000 | -9.1 | 36.6 | QAM256 | 23 |
24 | 323000000 | -9.9 | 36.4 | QAM256 | 24 |
26 | 339000000 | -10.3 | 35.8 | QAM256 | 26 |
27 | 347000000 | -10.5 | 35.6 | QAM256 | 27 |
28 | 355000000 | -10.7 | 35.6 | QAM256 | 28 |
29 | 363000000 | -11 | 35.6 | QAM256 | 29 |
30 | 371000000 | -11.3 | 35.1 | QAM256 | 30 |
31 | 379000000 | -11.5 | 35.1 | QAM256 | 31 |
25 | Locked | 35.779911 | 1211 | 0 |
1 | Locked | 36.609653 | 62478 | 1354 |
2 | Locked | 37.355988 | 5027 | 1526 |
3 | Locked | 37.636276 | 2467 | 564 |
4 | Locked | 37.355988 | 46027 | 0 |
5 | Locked | 37.636276 | 20 | 0 |
6 | Locked | 36.609653 | 3285 | 0 |
7 | Locked | 36.609653 | 65 | 0 |
8 | Locked | 37.636276 | 1 | 0 |
9 | Locked | 37.355988 | 0 | 0 |
10 | Locked | 37.355988 | 15 | 0 |
11 | Locked | 37.355988 | 8 | 0 |
12 | Locked | 37.636276 | 15 | 0 |
13 | Locked | 37.355988 | 15 | 0 |
14 | Locked | 37.355988 | 8 | 0 |
15 | Locked | 37.355988 | 15 | 0 |
16 | Locked | 36.609653 | 3 | 0 |
17 | Locked | 37.355988 | 5 | 0 |
18 | Locked | 36.609653 | 0 | 0 |
19 | Locked | 36.844463 | 9 | 0 |
20 | Locked | 36.609653 | 8 | 0 |
21 | Locked | 37.355988 | 5 | 0 |
22 | Locked | 36.609653 | 22 | 0 |
23 | Locked | 36.609653 | 94 | 0 |
24 | Locked | 36.386890 | 408 | 0 |
26 | Locked | 35.779911 | 1154 | 0 |
27 | Locked | 35.595078 | 2302 | 0 |
28 | Locked | 35.595078 | 1768 | 0 |
29 | Locked | 35.595078 | 1912 | 0 |
30 | Locked | 35.083549 | 3039 | 0 |
31 | Locked | 35.083549 | 1700 | 0 |
33 | 96 | 4K | 1880 | QAM256 | 759 |
33 | Locked | 26 | -23.6 | 861359 | 0 |
on 18-08-2022 18:04
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 32600000 | 49.8 | 5120 KSym/sec | 64QAM | 5 |
2 | 53700000 | 51.8 | 5120 KSym/sec | 64QAM | 2 |
3 | 46200000 | 51 | 5120 KSym/sec | 64QAM | 3 |
4 | 39400000 | 50.3 | 5120 KSym/sec | 64QAM | 4 |
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-08-2022 18:04
Network access | true |
Maximum Number of CPEs | 1 |
Baseline Privacy | true |
DOCSIS Mode | 3.1 |
Config file | cmreg-vmdg640-bbt076-b.cm |
SFID | 142106 |
Max Traffic Rate | 1230000450 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
SFID | 142105 |
Max Traffic Rate | 55000270 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
Max Concatenated Burst | 42600 |
Scheduling Type | bestEffort |
on 18-08-2022 18:05
Time Priority Description
Wed 17/08/2022 03:01:27 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 17/08/2022 03:02:42 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 17/08/2022 03:02:45 | 6 | CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 17/08/2022 03:03:26 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 17/08/2022 03:03:29 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 17; 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 17/08/2022 03:03:39 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 17/08/2022 03:03:39 | 6 | CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 17/08/2022 03:03:49 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 17/08/2022 03:03:51 | 6 | CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 17/08/2022 03:04:17 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 17/08/2022 03:04:17 | 6 | CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 17/08/2022 03:05:29 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 17/08/2022 03:05:31 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 17/08/2022 10:25:20 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 17/08/2022 10:25:22 | 6 | CM-STATUS message sent. Event Type Code: 1; 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 17/08/2022 10:25:45 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 17/08/2022 10:25:45 | 6 | CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 17/08/2022 10:27:06 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 17/08/2022 10:27:11 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 17; 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 17/08/2022 15:27:17 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 17/08/2022 15:27:37 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 17; 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 17/08/2022 15:46:32 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 17/08/2022 15:46:38 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 17; 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 17/08/2022 15:48:46 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 17/08/2022 15:48:54 | 6 | CM-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 17/08/2022 15:48:58 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 17/08/2022 15:49:03 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 17; 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 17/08/2022 15:55:03 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 17/08/2022 15:55:10 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 17; 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 17/08/2022 15:55:11 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 17/08/2022 15:55:27 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 17; 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 01/01/1970 00:01:22 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 18/08/2022 00:35:02 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 18/08/2022 00:35:39 | 6 | CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 18/08/2022 02:30:40 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 18/08/2022 02:30:57 | 6 | CM-STATUS message sent. Event Type Code: 4; Chan ID: 2; 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 18/08/2022 02:35:33 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 18/08/2022 02:36:01 | 6 | CM-STATUS message sent. Event Type Code: 4; Chan ID: 2; 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 18/08/2022 02:43:25 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 18/08/2022 02:43:33 | 6 | CM-STATUS message sent. Event Type Code: 4; Chan ID: 3; 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 18/08/2022 02:46:58 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 18/08/2022 02:47:09 | 6 | CM-STATUS message sent. Event Type Code: 4; Chan ID: 3; 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; |
on 21-08-2022 15:08
Hi rickgillyon,
thanks for the message and welcome to the forums.
I am sorry to hear that you are having issues with the broadband connection and this is not the experience which we want you to have with us.
Can you put the router in router mode and run the BQM/ a speed test to give an accurate result as the router is currently being used as a Modem and we cannot run tests on 3rd party devices.
Chris
on 22-08-2022 13:24
Thanks for this. What are you asking here, for me to put it in router mode and leave it in router mode for BQM? That's not really acceptable, we have a lot of devices connected to the mesh system and they would all be disconnected. Add to that, on some days the connection is fine, other days awful, so I may have to disconnect for multiple days. Also, BQM is currently connected to the hub4, what do you think BQM is connecting to?
You say you can't run tests on third-party devices: the device connected to VM is a hub4, not a third-party device. Every other device at the property was running fine with the hub3. I'm puzzled what this will do apart from cause me hassle. I have already fully reset the hub4 and set up from scratch still the same issues.
Do the power levels etc. look okay?
on 24-08-2022 14:12
Hey rickgillyon thank you for reaching back out.
Unfortunately whilst the device is connected to a mesh system we won't be able to tell it as we should, we would need to test it with the Hub4 running A WIFI or cable connection only without any 3rd party equipment.
Just to confirm this BQM is for the connection running through the Hub4 and not the mesh system? Thanks
Matt - Forum Team
New around here?
on 24-08-2022 14:46
The BQM is for the hub4, as that's my internet connection. Hub4 connects to vm coax, in modem mode, and connected by cat6 ethernet to Asus router. Same as my Hub3 was. So the BQM is for my internet connection. The hub4 just runs a cable connection to a router, the mesh system is irrelevant.
on 24-08-2022 15:10
Looking at the forums
Seems a lot of people are suffering dropouts , and posting bqm plots to support
I'm wondering if virgin have a bigger problem they are not owning up to