on 23-02-2023 06:07
Hello,
Lately, I've been dealing with high ping spikes to the point were it's unbearable ever since the installation two weeks ago. The download and upload speeds are fine but it's latency is abnormally high and fluctuates through the day.
I've rebooted the router many times and also checked if my area was having issues but no improvements at all.
Answered! Go to Answer
on 25-02-2023 14:37
Hi @Anonymous
Thanks for posting and welcome to the community.
Sorry to hear of the broadband issues. From a system check ran, you have got an SNR issue (signal to noise ratio). F010337396 is the fault number for your records. The estimated fix dte and time is the 27th February at 3pm.
Please monitor the connection after this time and report back if any issues, we'll be happy to help.
Best wishes,
Need a helpful hand to show you how to make a payment? Check out our guide - How to pay my Virgin Media bill
on 23-02-2023 06:24
Cable Modem Status
Item | Status | Comments |
Acquired Downstream Channel(Hz) | 138000000 | Locked |
Ranged Upstream Channel(Hz) | 0 | Failed |
Provisioning State | Online | Operational |
Downstream bonded channels
1 | 138000000 | 6.3 | 40 | QAM 256 | 1 |
2 | 146000000 | 6.2 | 40 | QAM 256 | 2 |
3 | 154000000 | 6.1 | 40 | QAM 256 | 3 |
4 | 162000000 | 6.1 | 40 | QAM 256 | 4 |
5 | 170000000 | 5.8 | 40 | QAM 256 | 5 |
6 | 178000000 | 5.8 | 40 | QAM 256 | 6 |
7 | 186000000 | 6.2 | 40 | QAM 256 | 7 |
8 | 194000000 | 6.3 | 40 | QAM 256 | 8 |
9 | 202000000 | 6.2 | 39 | QAM 256 | 9 |
10 | 210000000 | 6.6 | 39 | QAM 256 | 10 |
11 | 218000000 | 6.6 | 40 | QAM 256 | 11 |
12 | 226000000 | 6.3 | 40 | QAM 256 | 12 |
13 | 234000000 | 6.3 | 40 | QAM 256 | 13 |
14 | 242000000 | 6.4 | 40 | QAM 256 | 14 |
15 | 250000000 | 6.3 | 40 | QAM 256 | 15 |
16 | 258000000 | 6.1 | 39 | QAM 256 | 16 |
17 | 266000000 | 6 | 39 | QAM 256 | 17 |
18 | 274000000 | 6.1 | 39 | QAM 256 | 18 |
19 | 282000000 | 6.2 | 40 | QAM 256 | 19 |
20 | 290000000 | 6 | 40 | QAM 256 | 20 |
21 | 298000000 | 5.8 | 39 | QAM 256 | 21 |
22 | 306000000 | 6 | 39 | QAM 256 | 22 |
23 | 314000000 | 5.9 | 39 | QAM 256 | 23 |
24 | 322000000 | 4.8 | 39 | QAM 256 | 24 |
25 | 330000000 | 6 | 39 | QAM 256 | 25 |
26 | 338000000 | 6.3 | 39 | QAM 256 | 26 |
27 | 346000000 | 6 | 40 | QAM 256 | 27 |
28 | 354000000 | 6.4 | 40 | QAM 256 | 28 |
29 | 362000000 | 6.8 | 40 | QAM 256 | 29 |
30 | 370000000 | 6.6 | 40 | QAM 256 | 30 |
31 | 378000000 | 6.2 | 40 | QAM 256 | 31 |
1 | Locked | 40 | 0 | 0 |
2 | Locked | 40 | 0 | 0 |
3 | Locked | 40 | 0 | 0 |
4 | Locked | 40 | 0 | 0 |
5 | Locked | 40 | 0 | 0 |
6 | Locked | 40 | 0 | 0 |
7 | Locked | 40 | 0 | 0 |
8 | Locked | 40 | 0 | 0 |
9 | Locked | 39 | 0 | 0 |
10 | Locked | 39 | 0 | 0 |
11 | Locked | 40 | 0 | 0 |
12 | Locked | 40 | 0 | 0 |
13 | Locked | 40 | 0 | 0 |
14 | Locked | 40 | 0 | 0 |
15 | Locked | 40 | 0 | 0 |
16 | Locked | 39 | 0 | 0 |
17 | Locked | 39 | 0 | 0 |
18 | Locked | 39 | 0 | 0 |
19 | Locked | 40 | 0 | 0 |
20 | Locked | 40 | 0 | 0 |
21 | Locked | 39 | 0 | 0 |
22 | Locked | 39 | 0 | 0 |
23 | Locked | 39 | 20 | 0 |
24 | Locked | 39 | 2 | 0 |
25 | Locked | 39 | 2 | 0 |
26 | Locked | 39 | 2 | 0 |
27 | Locked | 40 | 0 | 0 |
28 | Locked | 40 | 0 | 0 |
29 | Locked | 40 | 0 | 0 |
30 | Locked | 40 | 1 | 0 |
31 | Locked | 39 | 1 | 0 |
Upstream bonded channels
Not Available |
Not Available |
General Configuration
Allowed |
1 |
Enabled |
3.1 |
dsfd;kfoA,.iyewrkldJKDHSU |
Primary Downstream Service Flow
16547 |
1200000450 bps |
42600bytes |
0 bps |
Primary Upstream Service Flow
16681 |
55000270 bps |
42600bytes |
0 bps |
16320bytes |
Best Effort |
22-02-2023 22:40:13 | warning | DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
22-02-2023 22:40:13 | notice | US profile assignment change. US Chan ID: 14; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
22-02-2023 21:37:08 | notice | US profile assignment change. US Chan ID: 14; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
22-02-2023 21:37:08 | warning | DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
22-02-2023 20:29:10 | notice | US profile assignment change. US Chan ID: 14; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
22-02-2023 20:29:10 | warning | DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
22-02-2023 20:19:02 | warning | DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
22-02-2023 20:19:02 | notice | US profile assignment change. US Chan ID: 14; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
22-02-2023 18:48:22 | warning | DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
22-02-2023 18:48:22 | notice | US profile assignment change. US Chan ID: 14; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
22-02-2023 18:28:12 | notice | US profile assignment change. US Chan ID: 14; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
22-02-2023 18:28:12 | warning | DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
22-02-2023 17:47:43 | notice | US profile assignment change. US Chan ID: 14; Previous Profile: 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
22-02-2023 17:47:43 | warning | DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
22-02-2023 17:47:40 | warning | REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
22-02-2023 17:47:40 | notice | REGISTRATION COMPLETE - Waiting for Operational status |
22-02-2023 17:47:35 | notice | DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
22-02-2023 17:47:15 | warning | DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
22-02-2023 17:47:13 | notice | Honoring MDD; IP provisioning mode = IPv4 |
22-02-2023 17:47:03 | critical | 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; |
22-02-2023 08:51:01 | warning | DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
22-02-2023 08:51:01 | notice | US profile assignment change. US Chan ID: 14; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
22-02-2023 08:40:53 | warning | DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
22-02-2023 08:40:53 | notice | US profile assignment change. US Chan ID: 14; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
21-02-2023 22:25:33 | warning | DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
21-02-2023 22:25:33 | notice | US profile assignment change. US Chan ID: 14; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
21-02-2023 22:15:25 | notice | US profile assignment change. US Chan ID: 14; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
21-02-2023 22:15:25 | warning | DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
21-02-2023 20:44:42 | warning | DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
21-02-2023 20:44:42 | notice | US profile assignment change. US Chan ID: 14; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
21-02-2023 19:54:16 | notice | US profile assignment change. US Chan ID: 14; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
21-02-2023 19:54:16 | warning | DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
on 25-02-2023 14:37
Hi @Anonymous
Thanks for posting and welcome to the community.
Sorry to hear of the broadband issues. From a system check ran, you have got an SNR issue (signal to noise ratio). F010337396 is the fault number for your records. The estimated fix dte and time is the 27th February at 3pm.
Please monitor the connection after this time and report back if any issues, we'll be happy to help.
Best wishes,
Need a helpful hand to show you how to make a payment? Check out our guide - How to pay my Virgin Media bill
on 28-02-2023 07:17
Hello,
Went to go check the connection as of right now and there is no improvement whatsoever. The problem hasn't been fixed yet.
https://www.thinkbroadband.com/broadband/monitoring/quality/share/f5fc9b614d81b0426625607c90ea40bd36edb554-28-02-2023
on 28-02-2023 16:37
on 09-03-2023 00:05
Can't open that BQM but if it's the same as the previous one there's probably still noise there.
Can confirm by looking at the logs to see if the upstream profile is repeatedly changing rapidly - that's the system trying to compensate for the noise.
on 10-03-2023 20:55
@Anonymous wrote:Hello,
Went to go check the connection as of right now and there is no improvement whatsoever. The problem hasn't been fixed yet.
https://www.thinkbroadband.com/broadband/monitoring/quality/share/f5fc9b614d81b0426625607c90ea40bd36edb554-28-02-2023
Oh if this ain't a perfect example for my two solutions. So you've had an engineers out, they 'fixed' it but it still poopy connection huh? Welcome to the world of VM. Your two options now are:
1) Accept this is as 'good as it gets' and get used to it
2) Leave and move to FTTP.