on 13-10-2022 14:50
Hi,
It's been 4~ weeks now that upload speeds in NW2 have been dreadful. I have already raised a complaint, I was given twice different date as to when the issue should be resolved, nothing has been done so far.
This is clearly an issue on the VM network as I had no issue with my M500 for years and everything started only few weeks ago. Download speeds are pretty much fine (500 Mbps~ throughout the day), upload however is plain garbage. While I was getting 35Mbps~ 24/7 before, now I'm getting anywhere between 1Mbps~5Mbps during day/peak time. Everything starts to become fine at night between 1am~6am showing that this isn't an issue with my setup.
I already went through all the usual BS about "checking my installation" but this isn't it. I'm not using WiFi, I've tried to reset my hub already, tried to connect directly through my hub in both in modem and router mode, doesn't change a thing.
Typical gap between peak and offpeak:
on 13-10-2022 16:21
on 13-10-2022 16:34
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 330750000 | 0 | 38 | 256 qam | 25 |
2 | 234750000 | 1 | 38 | 256 qam | 13 |
3 | 242750000 | 0.5 | 38 | 256 qam | 14 |
4 | 250750000 | 0.2 | 38 | 256 qam | 15 |
5 | 258750000 | 0 | 38 | 256 qam | 16 |
6 | 266750000 | 0 | 38 | 256 qam | 17 |
7 | 274750000 | -0.2 | 38 | 256 qam | 18 |
8 | 282750000 | -0.5 | 37 | 256 qam | 19 |
9 | 290750000 | -1.2 | 37 | 256 qam | 20 |
10 | 298750000 | -1.2 | 37 | 256 qam | 21 |
11 | 306750000 | -0.2 | 38 | 256 qam | 22 |
12 | 314750000 | 0 | 38 | 256 qam | 23 |
13 | 322750000 | 0.2 | 38 | 256 qam | 24 |
14 | 338750000 | 0 | 38 | 256 qam | 26 |
15 | 346750000 | 0 | 38 | 256 qam | 27 |
16 | 354750000 | 0 | 38 | 256 qam | 28 |
17 | 362750000 | -0.2 | 38 | 256 qam | 29 |
18 | 370750000 | 0.2 | 38 | 256 qam | 30 |
19 | 378750000 | 0.7 | 38 | 256 qam | 31 |
20 | 386750000 | 0.7 | 38 | 256 qam | 32 |
21 | 394750000 | 1 | 38 | 256 qam | 33 |
22 | 402750000 | 1 | 38 | 256 qam | 34 |
23 | 410750000 | 1 | 38 | 256 qam | 35 |
24 | 418750000 | 1 | 38 | 256 qam | 36 |
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 38.9 | 201 | 83 |
2 | Locked | 38.6 | 108 | 31 |
3 | Locked | 38.9 | 95 | 33 |
4 | Locked | 38.6 | 88 | 39 |
5 | Locked | 38.9 | 99 | 40 |
6 | Locked | 38.6 | 118 | 38 |
7 | Locked | 38.6 | 123 | 52 |
8 | Locked | 37.3 | 206 | 85 |
9 | Locked | 37.6 | 310 | 69 |
10 | Locked | 37.3 | 708 | 61 |
11 | Locked | 38.6 | 250 | 169 |
12 | Locked | 38.9 | 133 | 98 |
13 | Locked | 38.6 | 165 | 103 |
14 | Locked | 38.9 | 222 | 83 |
15 | Locked | 38.9 | 259 | 86 |
16 | Locked | 38.9 | 212 | 77 |
17 | Locked | 38.6 | 222 | 69 |
18 | Locked | 38.9 | 152 | 93 |
19 | Locked | 38.9 | 106 | 108 |
20 | Locked | 38.9 | 92 | 106 |
21 | Locked | 38.9 | 76 | 104 |
22 | Locked | 38.9 | 76 | 104 |
23 | Locked | 38.9 | 53 | 51 |
24 | Locked | 38.9 | 42 | 94 |
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 36600000 | 51 | 5120 | 64 qam | 11 |
2 | 23600000 | 51 | 5120 | 64 qam | 13 |
3 | 30100000 | 51 | 5120 | 64 qam | 12 |
4 | 43100000 | 51 | 5120 | 64 qam | 10 |
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 | ATDMA | 0 | 0 | 4 | 0 |
2 | ATDMA | 0 | 0 | 10 | 0 |
3 | ATDMA | 0 | 0 | 7 | 0 |
4 | ATDMA | 0 | 0 | 3 | 0 |
on 13-10-2022 16:35
Time Priority Description
13/10/2022 15:28:50 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/10/2022 13:02:37 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/10/2022 13:02:36 | critical | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/10/2022 13:01:10 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/10/2022 13:01:10 | critical | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/10/2022 13:00:57 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/10/2022 11:27:34 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
09/10/2022 17:40:26 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
09/10/2022 05:56:29 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt053-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
09/10/2022 05:56:29 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
06/10/2022 20:50:40 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
06/10/2022 03:50:0 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt053-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
06/10/2022 03:50:0 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
01/10/2022 23:23:24 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
01/10/2022 19:03:0 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt053-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
01/10/2022 19:03:0 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
01/10/2022 18:27:6 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
01/10/2022 12:28:13 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
01/10/2022 00:58:36 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
29/09/2022 08:08:57 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
on 13-10-2022 16:39
Here's a BQM already running from the past few days:
on 14-10-2022 14:12
on 14-10-2022 14:29
I checked the wiring again and that's not it. I tried to exclude every parameter that could affect the quality of the line, so just plugging a laptop to the virgin media Hub with nothing but a single Ethernet cable is still producing the same results.
Even after a full pin reset I'm still getting the same issue. I fail to see how someone coming to my place would help considering that speed are fine during the night and terrible during daytime/evening.
It's literally something happening in my area.
on 15-10-2022 03:49
Another day, another terrible BQM.
on 17-10-2022 15:48
Hey Antipika, thank you for reaching out and I am sorry you are having some connection issues.
Also thank you for sending over all your information.
I would like to look into and get to to the bottom of it, I am going to send you a PM.
Please can you look out for the purple envelope. Thanks
Matt - Forum Team
New around here?
on 18-10-2022 01:58
Hello! I just replied to your DM, thanks again for getting back to me and looking into this.