14-03-2022 21:28 - edited 14-03-2022 21:36
For 6 months now I have had really bad latency whilst gaming I have tried going through to virgins "technical" team numerous times who only understand the top 5 wifi tips and tricks and the only test they can run is a broadband speed test. Not one person in the company can just watch over your network for a day. They constantly log complaints for me that just have "wifi issues" attached to it which I tell them constantly it has nothing to do with. The technicians come round and say there is nothing wrong in my house leave and never hear anything again. Going through people on the forums they just tell me that the network team in my area dont see any issues. I knew it wouldnt change anything but thought i would try it anyway, in the last few days I have tried going for the 1Gb/s broadband just as a test to see if anything changed and it hasn't. I am within my 14 days where I can leave so this is the last time i'm going to try find a fix otherwise im going to go to another company to get broadband. I dont really want to do this as obviously virgins speeds are much better than anything im able to get here. But with the high latency it makes games unplayable.
Attached is my BQM and router levels if anyone can help me. I've heard many times this is just a typical over utilisation problem but surely there is a fix.
https://www.thinkbroadband.com/broadband/monitoring/quality/share/631ab29cc1facdef6347d954f73e1b5dc4...
on 14-03-2022 21:33
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
8 | 194750000 | 5.1 | 39 | QAM256 | 8 |
1 | 138750000 | 6.9 | 38.6 | QAM256 | 1 |
2 | 146750000 | 6.5 | 38.6 | QAM256 | 2 |
3 | 154750000 | 6.5 | 39 | QAM256 | 3 |
4 | 162750000 | 6.2 | 39 | QAM256 | 4 |
5 | 170750000 | 5.6 | 38.6 | QAM256 | 5 |
6 | 178750000 | 5.3 | 39 | QAM256 | 6 |
7 | 186750000 | 5.3 | 39 | QAM256 | 7 |
9 | 202750000 | 4.9 | 39 | QAM256 | 9 |
10 | 210750000 | 4.5 | 39 | QAM256 | 10 |
11 | 218750000 | 4.3 | 37.4 | QAM256 | 11 |
12 | 226750000 | 3.5 | 37.6 | QAM256 | 12 |
13 | 234750000 | 3.5 | 38.6 | QAM256 | 13 |
14 | 242750000 | 4 | 38.6 | QAM256 | 14 |
15 | 250750000 | 4.2 | 38.6 | QAM256 | 15 |
16 | 258750000 | 4.4 | 38.6 | QAM256 | 16 |
17 | 266750000 | 4 | 38.6 | QAM256 | 17 |
18 | 274750000 | 3.8 | 38.6 | QAM256 | 18 |
19 | 282750000 | 4.1 | 38.6 | QAM256 | 19 |
20 | 290750000 | 4.6 | 39 | QAM256 | 20 |
21 | 298750000 | 5 | 39 | QAM256 | 21 |
22 | 306750000 | 4.6 | 38.6 | QAM256 | 22 |
23 | 314750000 | 4.6 | 38.6 | QAM256 | 23 |
24 | 322750000 | 4.1 | 38.6 | QAM256 | 24 |
25 | 330750000 | 2.9 | 38.6 | QAM256 | 25 |
26 | 338750000 | 2.5 | 38.6 | QAM256 | 26 |
27 | 346750000 | 2.5 | 39 | QAM256 | 27 |
28 | 354750000 | 2.4 | 38.6 | QAM256 | 28 |
29 | 362750000 | 2.6 | 38.6 | QAM256 | 29 |
30 | 370750000 | 2.6 | 39 | QAM256 | 30 |
31 | 378750000 | 2.7 | 38.6 | QAM256 | 31 |
Channel Lock Status RxMER (dB) Pre RS Errors Post RS Errors
8 | Locked | 38.983261 | 0 | 0 |
1 | Locked | 38.605377 | 0 | 0 |
2 | Locked | 38.605377 | 0 | 0 |
3 | Locked | 38.983261 | 0 | 0 |
4 | Locked | 38.983261 | 0 | 0 |
5 | Locked | 38.605377 | 0 | 0 |
6 | Locked | 38.983261 | 0 | 0 |
7 | Locked | 38.983261 | 0 | 0 |
9 | Locked | 38.983261 | 0 | 0 |
10 | Locked | 38.983261 | 0 | 0 |
11 | Locked | 37.355988 | 0 | 0 |
12 | Locked | 37.636276 | 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.605377 | 0 | 0 |
18 | Locked | 38.605377 | 0 | 0 |
19 | Locked | 38.605377 | 0 | 0 |
20 | Locked | 38.983261 | 0 | 0 |
21 | Locked | 38.983261 | 0 | 0 |
22 | Locked | 38.605377 | 0 | 0 |
23 | Locked | 38.605377 | 0 | 0 |
24 | Locked | 38.605377 | 0 | 0 |
25 | Locked | 38.605377 | 0 | 0 |
26 | Locked | 38.605377 | 0 | 0 |
27 | Locked | 38.983261 | 0 | 0 |
28 | Locked | 38.605377 | 0 | 0 |
29 | Locked | 38.605377 | 0 | 0 |
30 | Locked | 38.983261 | 0 | 0 |
31 | Locked | 38.605377 | 0 | 0 |
159 | 96 | 4K | 1880 | QAM4096 | 759 |
159 | Locked | 40 | 2.1 | 1438664577 | 1497 |
1 | 60300000 | 45.5 | 5120 KSym/sec | 64QAM | 9 |
2 | 39400000 | 44.8 | 5120 KSym/sec | 64QAM | 12 |
3 | 46200000 | 44.3 | 5120 KSym/sec | 64QAM | 11 |
4 | 53700000 | 44.8 | 5120 KSym/sec | 64QAM | 10 |
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 14-03-2022 21:33
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; |
Sat 12/03/2022 12:17:04 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat 12/03/2022 12:17:04 | 3 | Registration RSP rejected unspecified reason;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat 12/03/2022 12:17:05 | 4 | T6 Timeout and retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat 12/03/2022 12:17:05 | 3 | REG RSP not received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat 12/03/2022 12:17:27 | 4 | Missing Mandatory MDD TLV on primary DS Channel;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat 12/03/2022 12:22:00 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat 12/03/2022 12:22:04 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat 12/03/2022 12:22:09 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat 12/03/2022 12:23:31 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat 12/03/2022 12:23:56 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat 12/03/2022 12:24:07 | 6 | SW Download INIT - Via Config file SUBsgvca69834ncxv9873254k |
Sat 12/03/2022 12:25:44 | 6 | SW download Successful - Via Config file |
Sat 12/03/2022 12:28:17 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat 12/03/2022 12:58:04 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat 12/03/2022 12:58:04 | 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 12/03/2022 13:52:28 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat 12/03/2022 13:52:28 | 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 12/03/2022 14:39:51 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat 12/03/2022 19:34:50 | 6 | CM-STATUS message sent. Event Type Code: 5; 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; |
Sat 12/03/2022 23:52:35 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat 12/03/2022 23:52:39 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat 12/03/2022 23:52:46 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat 12/03/2022 23:52:48 | 6 | CM-STATUS message sent. Event Type Code: 4; Chan ID: 6; 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 12/03/2022 23:52:49 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat 12/03/2022 23:53:07 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat 12/03/2022 23:55:46 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat 12/03/2022 23:59:04 | 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 13/03/2022 10:01:27 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 13/03/2022 10:53:09 | 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 13/03/2022 19:00:08 | 6 | CM-STATUS message sent. Event Type Code: 23; Chan ID: 159; 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; |
Sun 13/03/2022 19:05:12 | 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 13/03/2022 19:19:06 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
on 15-03-2022 07:20
This thread may explain, you may not like the options open to you, I'm afraid.