cancel
Showing results for 
Search instead for 
Did you mean: 

High Latency Spikes

Anonymous
Not applicable

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.

https://www.thinkbroadband.com/broadband/monitoring/quality/share/5cda89426d5ea694319d33bb69551ec993...

 

1 ACCEPTED SOLUTION

Accepted Solutions

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,

John_GS
Forum Team


Need a helpful hand to show you how to make a payment? Check out our guide - How to pay my Virgin Media bill

See where this Helpful Answer was posted

6 REPLIES 6

Anonymous
Not applicable

Cable Modem Status

ItemStatusComments
Acquired Downstream Channel(Hz)138000000Locked
Ranged Upstream Channel(Hz)0Failed
Provisioning StateOnlineOperational

 

 

Downstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
11380000006.340QAM 2561
21460000006.240QAM 2562
31540000006.140QAM 2563
41620000006.140QAM 2564
51700000005.840QAM 2565
61780000005.840QAM 2566
71860000006.240QAM 2567
81940000006.340QAM 2568
92020000006.239QAM 2569
102100000006.639QAM 25610
112180000006.640QAM 25611
122260000006.340QAM 25612
132340000006.340QAM 25613
142420000006.440QAM 25614
152500000006.340QAM 25615
162580000006.139QAM 25616
17266000000639QAM 25617
182740000006.139QAM 25618
192820000006.240QAM 25619
20290000000640QAM 25620
212980000005.839QAM 25621
22306000000639QAM 25622
233140000005.939QAM 25623
243220000004.839QAM 25624
25330000000639QAM 25625
263380000006.339QAM 25626
27346000000640QAM 25627
283540000006.440QAM 25628
293620000006.840QAM 25629
303700000006.640QAM 25630
313780000006.240QAM 25631
 Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1Locked4000
2Locked4000
3Locked4000
4Locked4000
5Locked4000
6Locked4000
7Locked4000
8Locked4000
9Locked3900
10Locked3900
11Locked4000
12Locked4000
13Locked4000
14Locked4000
15Locked4000
16Locked3900
17Locked3900
18Locked3900
19Locked4000
20Locked4000
21Locked3900
22Locked3900
23Locked39200
24Locked3920
25Locked3920
26Locked3920
27Locked4000
28Locked4000
29Locked4000
30Locked4010
31Locked3910

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
Not Available

 

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
Not Available

 

General Configuration

Network accessMaximum Number of CPEsBaseline PrivacyDOCSIS ModeConfig file
Allowed
1
Enabled
3.1
dsfd;kfoA,.iyewrkldJKDHSU

 

Primary Downstream Service Flow

SFIDMax Traffic RateMax Traffic BurstMin Traffic Rate
16547
1200000450 bps
42600bytes
0 bps

 

Primary Upstream Service Flow

SFIDMax Traffic RateMax Traffic BurstMin Traffic RateMax Concatenated BurstScheduling Type
16681
55000270 bps
42600bytes
0 bps
16320bytes
Best Effort

 

Time Priority Description
22-02-2023 22:40:13warningDBC-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:13noticeUS 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:08noticeUS 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:08warningDBC-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:10noticeUS 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:10warningDBC-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:02warningDBC-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:02noticeUS 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:22warningDBC-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:22noticeUS 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:12noticeUS 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:12warningDBC-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:43noticeUS 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:43warningDBC-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:40warningREG-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:40noticeREGISTRATION COMPLETE - Waiting for Operational status
22-02-2023 17:47:35noticeDS 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:15warningDHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
22-02-2023 17:47:13noticeHonoring MDD; IP provisioning mode = IPv4
22-02-2023 17:47:03criticalReceived 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:01warningDBC-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:01noticeUS 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:53warningDBC-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:53noticeUS 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:33warningDBC-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:33noticeUS 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:25noticeUS 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:25warningDBC-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:42warningDBC-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:42noticeUS 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:16noticeUS 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:16warningDBC-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;

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,

John_GS
Forum Team


Need a helpful hand to show you how to make a payment? Check out our guide - How to pay my Virgin Media bill

Anonymous
Not applicable

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

 

Test over night in modem mode with just a PC setup a new BQM and allow inbound ICMP on firewall.
---------------------------------------------------------------

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. 


@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.