cancel
Showing results for 
Search instead for 
Did you mean: 

Lag issues which have only recently started happening!

TiPs1
Tuning in

Hi, Over the last 1-2 weeks I have noticed I have started getting a lag on my hard wired connection on Xbox on the likes of Call of Duty and kids having issues on Fortnite. I have since ran a BQM for the last few days and noticed I am getting random spikes in latency which roughly matches the time we have issues while gaming and getting lag spikes.

I am not sure if its a network issue or what. I have checked the cable in my house which is only like 1m long as the entry point is right next to the router and the cable is tight. I have even changed ethernet cables just as a precaution but still no change.

Please see below my BQMs for the past few days and my router stats, hopefully its a simple fix (I have rebooted the router etc which hasn't helped. I even disconnected the VM cable and reconnected but nope.

I have also noticed in the Hub 5 log over the last day I have a few entries saying: DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value

Hub 5 with 1gig connection.

25/01/2024

TiPs1_0-1706528173372.png

26/01/2024

TiPs1_1-1706528213102.png

27/01/2024 (Red will be when I disconnected everything and made sure all cables were secure)

TiPs1_4-1706528350072.png

28/01/2024

TiPs1_3-1706528296070.png

29/01/2024 (until 11:40am)

 

TiPs1_6-1706528414401.png

 

3.0 Downstream channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1427000000-1.840QAM 25637
22110000001.841QAM 25610
32190000001.641QAM 25611
42270000001.541QAM 25612
52350000001.341QAM 25613
62430000000.741QAM 25614
72510000000.140QAM 25615
82590000000.240QAM 25616
92670000000.641QAM 25617
102750000000.440QAM 25618
112830000000.441QAM 25619
122910000000.441QAM 25620
132990000000.441QAM 25621
143070000000.341QAM 25622
153150000000.240QAM 25623
163230000000.140QAM 25624
173310000000.240QAM 25625
183390000000.240QAM 25626
193470000000.241QAM 25627
203550000000.341QAM 25628
213630000000.341QAM 25629
22371000000-141QAM 25630
23379000000-1.840QAM 25631
24387000000-240QAM 25632
25395000000-240QAM 25633
26403000000-1.940QAM 25634
27411000000-2.140QAM 25635
28419000000-240QAM 25636
29435000000-240QAM 25638
30443000000-1.940QAM 25639
31451000000-1.640QAM 25640

3.0 Downstream channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1Locked4000
2Locked4100
3Locked4100
4Locked4100
5Locked4100
6Locked4100
7Locked4000
8Locked4000
9Locked4100
10Locked4000
11Locked4100
12Locked4100
13Locked4100
14Locked4100
15Locked4000
16Locked4000
17Locked4000
18Locked4000
19Locked4110
20Locked4100
21Locked4110
22Locked4100
23Locked4020
24Locked4010
25Locked4000
26Locked4000
27Locked4010
28Locked4010
29Locked4040
30Locked4030
31Locked4000

3.1 Downstream channels

Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)
159944K1840QAM 40961108

3.1 Downstream channels

Channel ID Locked Status RxMER Data (dB) PLC Power (dBmV) Corrected errors (Active Profile) Uncorrectable errors (Active Profile)
159Locked40-3.731204976857152

 

 

3.0 Upstream channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
04960000051.55120QAM 641
14310000050.85120QAM 642
23660000050.55120QAM 643
330100000505120QAM 644
423600000495120QAM 645

3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
0ATDMA0000
1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA0000

3.1 Upstream channels

Channel Channel Width (MHz) Power (dBmV) FFT Type Modulation
61046.02KQAM 256

3.1 Upstream channels

Channel Channel Type Number of Active Subcarriers First Active Subcarrier (Hz) T3 Timeouts T4 Timeouts
6OFDMA20074000000100
22 REPLIES 22

TiPs1
Tuning in

Stopped the BQM monitor to see if it made a difference. Yet again peak time at evenings just can't play online games without lag spikes.

I have noticed on my logs I have been getting a lot of T3 errors .... 

3.0 Downstream channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1235000000141QAM 25613
21390000002.240QAM 2561
31470000002.140QAM 2562
4155000000240QAM 2563
51630000001.640QAM 2564
61710000001.440QAM 2565
71790000001.140QAM 2566
81870000001.240QAM 2567
91950000001.441QAM 2568
102030000001.341QAM 2569
112110000001.441QAM 25610
122190000001.241QAM 25611
132270000001.241QAM 25612
142430000000.441QAM 25614
152510000000.241QAM 25615
162590000000.141QAM 25616
172670000000.240QAM 25617
182750000000.141QAM 25618
19283000000041QAM 25619
20291000000041QAM 25620
21299000000041QAM 25621
223070000000.140QAM 25622
233150000000.240QAM 25623
243230000000.440QAM 25624
253310000000.640QAM 25625
263390000000.540QAM 25626
273470000000.541QAM 25627
283550000000.641QAM 25628
293630000000.641QAM 25629
30371000000-1.340QAM 25630
31379000000-2.240QAM 25631
32387000000-2.440QAM 25632

3.0 Downstream channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1Locked4120
2Locked40100
3Locked402722
4Locked402934
5Locked403748
6Locked402754
7Locked403753
8Locked403529
9Locked414547
10Locked412449
11Locked413954
12Locked414176
13Locked413649
14Locked413863
15Locked413751
16Locked413333
17Locked402838
18Locked413555
19Locked412231
20Locked412113
21Locked412224
22Locked401526
23Locked401429
24Locked403329
25Locked402435
26Locked402633
27Locked412826
28Locked412860
29Locked413326
30Locked402237
31Locked403538
32Locked402825

3.1 Downstream channels

Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)
159944K1840QAM 40961108

3.1 Downstream channels

Channel ID Locked Status RxMER Data (dB) PLC Power (dBmV) Corrected errors (Active Profile) Uncorrectable errors (Active Profile)
159Locked40-4.0306061801213004

 

3.0 Upstream channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
04960000051.85120QAM 641
14310000050.55120QAM 642
23660000050.85120QAM 643
330100000505120QAM 644
42360000048.85120QAM 645

3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
0ATDMA01520
1ATDMA01500
2ATDMA01500
3ATDMA015530
4ATDMA01550

3.1 Upstream channels

Channel Channel Width (MHz) Power (dBmV) FFT Type Modulation
61046.22KQAM 256

3.1 Upstream channels

Channel Channel Type Number of Active Subcarriers First Active Subcarrier (Hz) T3 Timeouts T4 Timeouts
6OFDMA20074000000440

 

Network Log

Time Priority Description
06-02-2024 03:12:53noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
06-02-2024 03:12: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;
06-02-2024 02:42:17warningDBC-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;
06-02-2024 02:42:17noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
06-02-2024 02:41:53noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
06-02-2024 02:41: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;
06-02-2024 02:41:32criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
06-02-2024 02:41:31criticalRanging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
06-02-2024 02:41:31critical16 consecutive T3 timeouts while trying to range on upstream channel 8;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
06-02-2024 02:41:02criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
06-02-2024 02:31:20critical16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
06-02-2024 02:31:20criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
06-02-2024 02:17:21criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
06-02-2024 02:15:56noticeCM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 4 5 6 7 8 9 10 11 12 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS
06-02-2024 02:15:25criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
06-02-2024 02:15:23warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
06-02-2024 02:10:51criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
06-02-2024 02:09:22noticeCM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 4 5 6 7 8 9 10 11 12 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS
06-02-2024 02:08:54criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
06-02-2024 02:08:52warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
06-02-2024 02:08:51criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
06-02-2024 00:41:55warningDBC-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;
06-02-2024 00:41:37criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
06-02-2024 00:41:37criticalRanging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
06-02-2024 00:41:37critical16 consecutive T3 timeouts while trying to range on upstream channel 8;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
06-02-2024 00:40:55criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-02-2024 20:30:47warningDBC-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;
03-02-2024 11:18:30errorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
02-02-2024 12:20:31noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
02-02-2024 12:20:31warningDBC-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;
02-02-2024 11:18:15noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
02-02-2024 11:18:15warningDBC-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;

TiPs1
Tuning in

I have been hit with this twice in the past 7-10 days. Previous time it asked me to factory reset my router which made no difference. 

TiPs1_0-1707211905454.png

TiPs1_1-1707211963123.png

 

Hi TiPs1

Thanks for your post and for including all of your screenshots, that's really helpful.

Whilst your BQM graph looks very stable, it looks like your upstream power levels are out of the normal parameters, which will explain why the issue is most visible when gaming online. 

There's no known outages that are causing this, so we'll need to book in an engineer visit for you.

I've dropped you a PM so I can help further.

Beth

Mate, you are not alone.  I have had these issues since December 2023.  they have been out to my house twice once in January and today.  they first replaced the "booster box" as this apparently interfers with superhub 5 signal.  they also updates the point the signal comes into the building (I live in a block of flats).  Still lagging like crazy.  today they replaced the router.  I'm still lagging like crazy. 

 

If I take mu equipment to my neighbours who is also VM I have no issues at all.  I am paying for a 512GB download because I game, stream about mental health and my ptsd treatment is done via NHS video call.  there is always lag and stuttering all day everyday.  I used cat7 cables and have switched out to my cat5e and cat6e cables which were all working perfectly prior to my upgrading to cat 7.  again these cables and my xbox, laptop and px all work without issue in my neighbor flat.  the issues is 100% to do with the cables ran from the entrance to the block of flats to my router. 

 

VM run diagnostics.  no issue in my postcode area.  no issue with bill payment.  no issue with equipment.  we are having problems reaching your router.  hard reset the router.  the issue is just as bad if not worse than before.  I will have to allow them until midafternoon tomorrow for the 24 hours the new equipment needs to settle.  its nonsense.  absolutely nonsense.  it is not only affecting my use of services.  it has a direct impact on my mental health and is interfering with my mental health treatment. It's absolutely disgusting.

Tech visted me 2 days ago. replaced a few of my cables and replaced the hub and removed a metal thing that was attached to the cable which he said wasn't needed. Can't fault the tech who visited guy was brilliant and wanted to rule out a faulty hub due to errors on the hub not clearing and said to give it a few days to see how the power levels go. Going to monitor it until the weekend I think and see if it settles but so far I think its got worse especially gaming last night. Rubberbanding effect online just unplayable and yet again happened around 7:30pm-8pm and continued until I turned it off around 9pm.

 

3.0 Upstream channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
04960000051.55120QAM 641
14310000050.35120QAM 642
23660000049.55120QAM 643
330100000495120QAM 644
423600000495120QAM 645

3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
0ATDMA0000
1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA0000

3.1 Upstream channels

Channel Channel Width (MHz) Power (dBmV) FFT Type Modulation
61045.72KQAM 256

3.1 Upstream channels

Channel Channel Type Number of Active Subcarriers First Active Subcarrier (Hz) T3 Timeouts T4 Timeouts
6OFDMA2007400000020

 

Network Log

Time Priority Description
08-02-2024 19:37:28criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-02-2024 05:51:20noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-02-2024 05:51:20warningDBC-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;
08-02-2024 04:45:20noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-02-2024 04:45:20warningDBC-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;
07-02-2024 19:56:54noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
07-02-2024 19:56:54warningDBC-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;
07-02-2024 19:26:20warningDBC-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;
07-02-2024 19:26:20noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
07-02-2024 19:25:56warningDBC-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;
07-02-2024 19:25:56noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
07-02-2024 17:37:42noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
07-02-2024 17:37: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;
07-02-2024 17:37:38noticeREGISTRATION COMPLETE - Waiting for Operational status
07-02-2024 17:37:32warningDynamic Range Window violation
07-02-2024 17:37:32warningRNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
07-02-2024 17:37:32warningREG-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;
07-02-2024 17:37:32warningRNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
07-02-2024 17:37:32warningDynamic Range Window violation
07-02-2024 17:37:32warningRNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
07-02-2024 17:37:32warningDynamic Range Window violation
07-02-2024 17:37:32warningRNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
07-02-2024 17:37:32warningDynamic Range Window violation
07-02-2024 17:37:27noticeDS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 4.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
07-02-2024 17:37:19warningDHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
07-02-2024 17:37:17noticeHonoring MDD; IP provisioning mode = IPv4
07-02-2024 17:37:01criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
07-02-2024 17:37:00criticalCable Modem Reboot because of - Reboot Timezone Change
07-02-2024 17:34:05criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
07-02-2024 17:33:59criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
07-02-2024 17:33:54criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
07-02-2024 17:33:53criticalCable Modem Reboot because of - pin-reset

TiPs1
Tuning in

Started a new BQM monitor once I detected I was having the issues still.

TiPs1_0-1707471783325.png

 

legacy1
Alessandro Volta

BQM to hub shows nothing much might be as good as it gets for you so get your own router with 1Gb ports to test BQM past the hub in modem mode

---------------------------------------------------------------

Considering the fact the hub worked perfectly fine a couple of weeks ago, I won't be buying my own router to get the connection back to how it was lol. It has already been confirmed by forum staff and also the tech who visited that the upstream power levels are too high. 

legacy1
Alessandro Volta

If upstream power levels was the problem don't you think your BQM would look worse? 

---------------------------------------------------------------

I don't have a clue which is why I am here asking for help to get the connection back to how it was a few weeks ago. Clearly something has happened within the network. Tech did confirm the hub had stored errors which never cleared so replaced the hub just incase that was to blame and hoped to see the power levels drop within 24hours which they haven't. 

Upstream power levels currently

3.0 Upstream channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
04960000051.55120QAM 641
14310000050.35120QAM 642
23660000049.55120QAM 643
330100000495120QAM 644
423600000495120QAM 645

BQM for the last 24hours.

TiPs1_0-1707517275398.png