on 12-09-2022 20:05
Hi all
looking for help on my Hub 4..
had 1gb internet for around 8 months been fantastic… but get 1gb usually sits around 600:700mbps.. which is still brilliant. I have a DECO system which has also been great for home working and gaming … giving me them values above on my speeds tests.
but now all of a sudden last week or so am getting 110 to 180 max? Tried mutiple resets of the system still the same … tried calling for help at virgin said they would send new coding to the device to help , hasnt helped . Also said give it a week but i know thats not going to help at all.
anyone able to give any advise or help ? I think my hub maybe busted or something ?
on 13-09-2022 15:25
on 13-09-2022 15:32
Yes the DECO m5 and yes the virgin is on modem mode and DECO doing the router job
Ill try that cable change and see how i get on but i did reset the full network and took the deco off the network and virgin media router back to router mode . And the speed was the same as the deco
on 13-09-2022 15:40
on 13-09-2022 16:02
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
25 | 331000000 | 3.700001 | 38.983261 | QAM256 | 25 |
6 | 179000000 | 4.000000 | 38.605377 | QAM256 | 6 |
7 | 187000000 | 4.300003 | 38.605377 | QAM256 | 7 |
8 | 195000000 | 4.199997 | 38.605377 | QAM256 | 8 |
9 | 203000000 | 3.900002 | 38.605377 | QAM256 | 9 |
10 | 211000000 | 4.099998 | 38.605377 | QAM256 | 10 |
11 | 219000000 | 4.300003 | 37.355988 | QAM256 | 11 |
12 | 227000000 | 3.799999 | 36.386890 | QAM256 | 12 |
13 | 235000000 | 3.900002 | 38.605377 | QAM256 | 13 |
14 | 243000000 | 4.300003 | 38.983261 | QAM256 | 14 |
15 | 251000000 | 3.599998 | 37.636276 | QAM256 | 15 |
16 | 259000000 | 3.200001 | 37.636276 | QAM256 | 16 |
17 | 267000000 | 3.700001 | 38.605377 | QAM256 | 17 |
18 | 275000000 | 4.000000 | 38.605377 | QAM256 | 18 |
19 | 283000000 | 3.799999 | 38.605377 | QAM256 | 19 |
20 | 291000000 | 4.099998 | 38.605377 | QAM256 | 20 |
21 | 299000000 | 3.700001 | 38.605377 | QAM256 | 21 |
22 | 307000000 | 3.299999 | 38.605377 | QAM256 | 22 |
23 | 315000000 | 3.700001 | 38.605377 | QAM256 | 23 |
24 | 323000000 | 4.099998 | 38.605377 | QAM256 | 24 |
26 | 339000000 | 3.500000 | 38.605377 | QAM256 | 26 |
27 | 347000000 | 3.400002 | 38.605377 | QAM256 | 27 |
28 | 355000000 | 3.000000 | 38.605377 | QAM256 | 28 |
29 | 363000000 | 3.099998 | 38.605377 | QAM256 | 29 |
30 | 371000000 | 3.500000 | 38.605377 | QAM256 | 30 |
31 | 379000000 | 3.599998 | 37.636276 | QAM256 | 31 |
32 | 387000000 | 3.799999 | 38.605377 | QAM256 | 32 |
33 | 395000000 | 4.300003 | 38.605377 | QAM256 | 33 |
34 | 403000000 | 4.000000 | 37.636276 | QAM256 | 34 |
35 | 411000000 | 4.000000 | 38.605377 | QAM256 | 35 |
36 | 419000000 | 4.400002 | 38.605377 | QAM256 | 36 |
Channel Lock Status RxMER (dB) Pre RS Errors Post RS Errors
25 | Locked | 38.983261 | 0 | 0 |
6 | Locked | 38.605377 | 2590 | 1 |
7 | Locked | 38.605377 | 835 | 0 |
8 | Locked | 38.605377 | 0 | 0 |
9 | Locked | 38.605377 | 0 | 0 |
10 | Locked | 38.605377 | 0 | 0 |
11 | Locked | 37.355988 | 0 | 0 |
12 | Locked | 36.386890 | 0 | 0 |
13 | Locked | 38.605377 | 0 | 0 |
14 | Locked | 38.983261 | 0 | 0 |
15 | Locked | 37.636276 | 0 | 0 |
16 | Locked | 37.636276 | 0 | 0 |
17 | Locked | 38.605377 | 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.605377 | 0 | 0 |
23 | Locked | 38.605377 | 0 | 0 |
24 | Locked | 38.605377 | 0 | 0 |
26 | Locked | 38.605377 | 0 | 0 |
27 | Locked | 38.605377 | 0 | 0 |
28 | Locked | 38.605377 | 0 | 0 |
29 | Locked | 38.605377 | 0 | 0 |
30 | Locked | 38.605377 | 0 | 0 |
31 | Locked | 37.636276 | 0 | 0 |
32 | Locked | 38.605377 | 0 | 0 |
33 | Locked | 38.605377 | 0 | 0 |
34 | Locked | 37.636276 | 0 | 0 |
35 | Locked | 38.605377 | 0 | 0 |
36 | Locked | 38.605377 | 0 | 0 |
on 13-09-2022 16:03
1 | 43100000 | 45.520599 | 5120 KSym/sec | 64QAM | 2 |
2 | 49600000 | 45.770599 | 5120 KSym/sec | 64QAM | 1 |
3 | 36600000 | 45.270599 | 5120 KSym/sec | 64QAM | 3 |
4 | 23600000 | 45.270599 | 5120 KSym/sec | 32QAM | 9 |
5 | 30100000 | 45.770599 | 5120 KSym/sec | 64QAM | 4 |
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 |
5 | US_TYPE_STDMA | 0 | 0 | 0 | 0 |
13 | 10.4 | 41.0 | 2K | QAM8 |
13 | OFDMA | 208 | 53.4 | 0 | 0 |
on 13-09-2022 16:04
Time Priority Description
Fri Sep 9 10:31:02 2022 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri Sep 9 10:34:17 2022 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri Sep 9 23:07:33 2022 | 6 | US profile assignment change. US Chan ID: 13; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri Sep 9 23:07:35 2022 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri Sep 9 23:08:04 2022 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri Sep 9 23:08:48 2022 | 3 | Ranging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri Sep 9 23:08:48 2022 | 3 | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri Sep 9 23:08:48 2022 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri Sep 9 23:09:03 2022 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri Sep 9 23:49:48 2022 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri Sep 9 23:50:02 2022 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat Sep 10 00:11:22 2022 | 6 | US profile assignment change. US Chan ID: 13; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat Sep 10 00:11:39 2022 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat Sep 10 00:16:25 2022 | 6 | US profile assignment change. US Chan ID: 13; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat Sep 10 00:56:51 2022 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat Sep 10 03:19:56 2022 | 6 | US profile assignment change. US Chan ID: 13; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat Sep 10 03:27:30 2022 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat Sep 10 03:41:30 2022 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat Sep 10 03:41:58 2022 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 8; 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; |
Sat Sep 10 03:42:56 2022 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat Sep 10 03:43:25 2022 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 8; 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; |
Sat Sep 10 04:42:28 2022 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat Sep 10 04:42:40 2022 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 8; 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; |
Sat Sep 10 05:38:16 2022 | 6 | US profile assignment change. US Chan ID: 13; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat Sep 10 05:38:23 2022 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat Sep 10 05:43:19 2022 | 6 | US profile assignment change. US Chan ID: 13; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat Sep 10 05:44:51 2022 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 8; 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; |
Sat Sep 10 10:27:52 2022 | 6 | US profile assignment change. US Chan ID: 13; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat Sep 10 12:41:01 2022 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat Sep 10 12:41:03 2022 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat Sep 10 12:41:18 2022 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat Sep 10 14:02:23 2022 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat Sep 10 14:02:47 2022 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat Sep 10 14:40:07 2022 | 6 | US profile assignment change. US Chan ID: 13; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat Sep 10 14:40:14 2022 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat Sep 10 14:45:10 2022 | 6 | US profile assignment change. US Chan ID: 13; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat Sep 10 14:45:49 2022 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat Sep 10 14:54:36 2022 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
on 15-09-2022 16:12
Hi Gazza23102021, thanks for the message and welcome to the forums.
I am sorry to hear that you are having issues with the speed and this is not the experience which we want you to have with us. How is the service since posting? Can you send us the BQM so that this can be investigated?
Chris
on 15-09-2022 16:18
Exactly the same … i know i get 1100 to my house and when it goes through my hub i am getting 50 / 100 when i was getting 600/700 pretty easily and for over a year, it’s definitely the hub causing the issue but when i call virgin they are just monitoring it ?
what is bqm?
on 17-09-2022 17:55
Hey there @Gazza23102021, thanks for reaching out to us.
I'm sorry to see the issues with the speed.
May I ask if you are using SamKnows speed test?
BQM is a broadband quality monitor graph which allows us to see any spikes, packet loss or latency issues with the connection, which may indicate that there's an SNR (Signal to Noise Ratio) fault or a high utilisation fault.
For more information regarding BQM, please check here where you can sign up and run your own checks which will help us to advise regarding your connection. 🙂
Let us know how it goes.
Kind regards.