23-08-2021 15:09 - edited 23-08-2021 15:12
Hi
Im wondering if someone could have a look at my numbers, my BB is normally exceptional but we have begun to notice slowdowns, teams meetings disxonnecting and multiple kicks from online games
Wondered would someone offer some insight
on 23-08-2021 15:10
3.0 Downstream channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
40 | 451000000 | 2.3 | 40.4 | QAM256 | 40 |
10 | 211000000 | 4.6 | 40.4 | QAM256 | 10 |
11 | 219000000 | 4.8 | 40.9 | QAM256 | 11 |
12 | 227000000 | 4.7 | 40.4 | QAM256 | 12 |
13 | 235000000 | 4.5 | 40.4 | QAM256 | 13 |
14 | 243000000 | 4.8 | 40.4 | QAM256 | 14 |
15 | 251000000 | 4.9 | 40.4 | QAM256 | 15 |
16 | 259000000 | 4.9 | 40.9 | QAM256 | 16 |
17 | 267000000 | 4.4 | 40.4 | QAM256 | 17 |
18 | 275000000 | 3.3 | 40.4 | QAM256 | 18 |
19 | 283000000 | 3.5 | 40.4 | QAM256 | 19 |
20 | 291000000 | 3.6 | 40.4 | QAM256 | 20 |
21 | 299000000 | 4.6 | 40.4 | QAM256 | 21 |
22 | 307000000 | 4.6 | 40.4 | QAM256 | 22 |
23 | 315000000 | 4.4 | 40.4 | QAM256 | 23 |
24 | 323000000 | 4.6 | 40.9 | QAM256 | 24 |
25 | 331000000 | 4.1 | 40.9 | QAM256 | 25 |
26 | 339000000 | 4.1 | 40.9 | QAM256 | 26 |
27 | 347000000 | 3.9 | 40.9 | QAM256 | 27 |
28 | 355000000 | 4 | 40.9 | QAM256 | 28 |
29 | 363000000 | 3.4 | 40.4 | QAM256 | 29 |
30 | 371000000 | 3.4 | 40.4 | QAM256 | 30 |
31 | 379000000 | 3.6 | 40.4 | QAM256 | 31 |
32 | 387000000 | 2.9 | 40.4 | QAM256 | 32 |
33 | 395000000 | 3.8 | 40.9 | QAM256 | 33 |
34 | 403000000 | 3 | 40.4 | QAM256 | 34 |
35 | 411000000 | 2.2 | 40.4 | QAM256 | 35 |
36 | 419000000 | 1.9 | 40.4 | QAM256 | 36 |
37 | 427000000 | 2.2 | 40.4 | QAM256 | 37 |
38 | 435000000 | 2.1 | 40.9 | QAM256 | 38 |
39 | 443000000 | 2 | 40.4 | QAM256 | 39 |
3.0 Downstream channels
Channel Lock Status RxMER (dB) Pre RS Errors Post RS Errors
40 | Locked | 40.366287 | 0 | 0 |
10 | Locked | 40.366287 | 0 | 0 |
11 | Locked | 40.946209 | 0 | 0 |
12 | Locked | 40.366287 | 0 | 0 |
13 | Locked | 40.366287 | 0 | 0 |
14 | Locked | 40.366287 | 0 | 0 |
15 | Locked | 40.366287 | 0 | 0 |
16 | Locked | 40.946209 | 0 | 0 |
17 | Locked | 40.366287 | 0 | 0 |
18 | Locked | 40.366287 | 0 | 0 |
19 | Locked | 40.366287 | 0 | 0 |
20 | Locked | 40.366287 | 0 | 0 |
21 | Locked | 40.366287 | 0 | 0 |
22 | Locked | 40.366287 | 0 | 0 |
23 | Locked | 40.366287 | 0 | 0 |
24 | Locked | 40.946209 | 0 | 0 |
25 | Locked | 40.946209 | 0 | 0 |
26 | Locked | 40.946209 | 0 | 0 |
27 | Locked | 40.946209 | 0 | 0 |
28 | Locked | 40.946209 | 0 | 0 |
29 | Locked | 40.366287 | 0 | 0 |
30 | Locked | 40.366287 | 0 | 0 |
31 | Locked | 40.366287 | 0 | 0 |
32 | Locked | 40.366287 | 0 | 0 |
33 | Locked | 40.946209 | 0 | 0 |
34 | Locked | 40.366287 | 0 | 0 |
35 | Locked | 40.366287 | 0 | 0 |
36 | Locked | 40.366287 | 0 | 0 |
37 | Locked | 40.366287 | 0 | 0 |
38 | Locked | 40.946209 | 0 | 0 |
39 | Locked | 40.366287 | 0 | 0 |
41 | 96 | 4K | 1880 | QAM4096 | 759 |
41 | Locked | 40 | -4.3 | 1194946938 | 9 |
on 23-08-2021 15:11
3.0 Upstream channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 46200000 | 48 | 5120 KSym/sec | 64QAM | 3 |
2 | 39400000 | 47.8 | 5120 KSym/sec | 64QAM | 7 |
3 | 60300000 | 49.5 | 5120 KSym/sec | 64QAM | 1 |
4 | 53700000 | 49 | 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 | 1 | 0 |
2 | US_TYPE_STDMA | 0 | 0 | 0 | 0 |
3 | US_TYPE_STDMA | 0 | 0 | 2 | 0 |
4 | US_TYPE_STDMA | 0 | 0 | 0 | 0 |
on 23-08-2021 15:12
Network Log
Time Priority Description
Fri 06/08/2021 11:09:15 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 06/08/2021 11:09:15 | 6 | CM-STATUS message sent. Event Type Code: 4; Chan ID: 41; 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; |
Fri 06/08/2021 11:09:19 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 06/08/2021 11:10:32 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 06/08/2021 11:10:37 | 6 | CM-STATUS message sent. Event Type Code: 4; Chan ID: 10; 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; |
Fri 06/08/2021 11:10:38 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 06/08/2021 11:10:41 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 06/08/2021 11:10:44 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 06/08/2021 11:10:44 | 6 | CM-STATUS message sent. Event Type Code: 4; Chan ID: 10; 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; |
Fri 06/08/2021 11:10:45 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 06/08/2021 11:10:46 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 06/08/2021 11:10:48 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 06/08/2021 11:10:48 | 6 | CM-STATUS message sent. Event Type Code: 16; Chan ID: 41; 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 06/08/2021 11:10:49 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 06/08/2021 11:10:50 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 18; 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; |
Fri 06/08/2021 11:11:01 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 06/08/2021 11:11:04 | 6 | CM-STATUS message sent. Event Type Code: 23; Chan ID: 41; 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; |
Fri 06/08/2021 11:11:12 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 06/08/2021 11:11:25 | 3 | Ranging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 06/08/2021 11:11:25 | 3 | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 06/08/2021 11:11:36 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 06/08/2021 11:12:48 | 3 | Ranging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 06/08/2021 11:12:48 | 3 | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 06/08/2021 11:12:50 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 06/08/2021 11:14:26 | 3 | Ranging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 06/08/2021 11:14:26 | 3 | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 06/08/2021 11:14:37 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 06/08/2021 11:20:10 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 25; 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; |
Fri 06/08/2021 11:20:13 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 06/08/2021 11:21:25 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 06/08/2021 11:21:29 | 6 | CM-STATUS message sent. Event Type Code: 2; Chan ID: 30; 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; |
Fri 06/08/2021 11:21:30 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 06/08/2021 11:24:02 | 3 | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 06/08/2021 11:33:49 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 06/08/2021 11:34:14 | 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 06/08/2021 11:49:45 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 40; 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; |
Fri 06/08/2021 11:59:20 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri 06/08/2021 11:59:22 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
on 23-08-2021 16:00
on 23-08-2021 17:12
On the face if it, the raw figures don’t look too bad - but then again, I’m known for regarding the values as reported by the Hub 4 as being about as reliable as the Taliban’s report on how well they respect the rights of women! Worryingly there are a lot of errors being logged which all seemed to stop on 6th when the Hub evidently just gave up on logging them - who said the Hub 4 wasn’t a superbly engineered quality product?
So, basically who knows what’s going on?
@jbrennand’s suggestion on the Think broadband Quality monitor is certainly a good one, also, assuming that you have already power cycled the hub, I’d suggest factory resetting it to see if it can’t be persuaded to start logging something useful.
The lack of data makes a proper diagnosis difficult, but I suspect you have a cable connectivity issue and will need an engineer visit to fix, we’ll need some more recent info to be able to check though.
on 23-08-2021 20:31
im guessing yellow spikes are bad ?
on 23-08-2021 20:37
on 24-08-2021 21:33
on 27-08-2021 11:15
Thanks for your post and welcome to the Community Forums, binzie,
Sorry to hear that you have been having connection issues. How has things been since your post?
I have run a remote diagnostic and have not been able to identify any issues with your connection.
We can also provide online broadband help here: https://www.virginmedia.com/help/services-support/broadband
Let us know if you need any further help.
Cheers,
Corey C