Lag issues which have only recently started happening!

[TiPs1]

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

26/01/2024

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

28/01/2024

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

3.0 Downstream channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

1	427000000	-1.8	40	QAM 256	37
2	211000000	1.8	41	QAM 256	10
3	219000000	1.6	41	QAM 256	11
4	227000000	1.5	41	QAM 256	12
5	235000000	1.3	41	QAM 256	13
6	243000000	0.7	41	QAM 256	14
7	251000000	0.1	40	QAM 256	15
8	259000000	0.2	40	QAM 256	16
9	267000000	0.6	41	QAM 256	17
10	275000000	0.4	40	QAM 256	18
11	283000000	0.4	41	QAM 256	19
12	291000000	0.4	41	QAM 256	20
13	299000000	0.4	41	QAM 256	21
14	307000000	0.3	41	QAM 256	22
15	315000000	0.2	40	QAM 256	23
16	323000000	0.1	40	QAM 256	24
17	331000000	0.2	40	QAM 256	25
18	339000000	0.2	40	QAM 256	26
19	347000000	0.2	41	QAM 256	27
20	355000000	0.3	41	QAM 256	28
21	363000000	0.3	41	QAM 256	29
22	371000000	-1	41	QAM 256	30
23	379000000	-1.8	40	QAM 256	31
24	387000000	-2	40	QAM 256	32
25	395000000	-2	40	QAM 256	33
26	403000000	-1.9	40	QAM 256	34
27	411000000	-2.1	40	QAM 256	35
28	419000000	-2	40	QAM 256	36
29	435000000	-2	40	QAM 256	38
30	443000000	-1.9	40	QAM 256	39
31	451000000	-1.6	40	QAM 256	40

3.0 Downstream channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors

1	Locked	40	0	0
2	Locked	41	0	0
3	Locked	41	0	0
4	Locked	41	0	0
5	Locked	41	0	0
6	Locked	41	0	0
7	Locked	40	0	0
8	Locked	40	0	0
9	Locked	41	0	0
10	Locked	40	0	0
11	Locked	41	0	0
12	Locked	41	0	0
13	Locked	41	0	0
14	Locked	41	0	0
15	Locked	40	0	0
16	Locked	40	0	0
17	Locked	40	0	0
18	Locked	40	0	0
19	Locked	41	1	0
20	Locked	41	0	0
21	Locked	41	1	0
22	Locked	41	0	0
23	Locked	40	2	0
24	Locked	40	1	0
25	Locked	40	0	0
26	Locked	40	0	0
27	Locked	40	1	0
28	Locked	40	1	0
29	Locked	40	4	0
30	Locked	40	3	0
31	Locked	40	0	0

3.1 Downstream channels

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

159

94

4K

1840

QAM 4096

1108

3.1 Downstream channels

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

159

Locked

40

-3.7

3120497685

7152

3.0 Upstream channels

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

0	49600000	51.5	5120	QAM 64	1
1	43100000	50.8	5120	QAM 64	2
2	36600000	50.5	5120	QAM 64	3
3	30100000	50	5120	QAM 64	4
4	23600000	49	5120	QAM 64	5

3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

0	ATDMA	0	0	0	0
1	ATDMA	0	0	0	0
2	ATDMA	0	0	0	0
3	ATDMA	0	0	0	0
4	ATDMA	0	0	0	0

3.1 Upstream channels

Channel Channel Width (MHz) Power (dBmV) FFT Type Modulation

6

10

46.0

2K

QAM 256

3.1 Upstream channels

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

6

OFDMA

200

74000000

10

0

[TiPs1]

Network Log

Time Priority Description

28-01-2024 19:30:55	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;
28-01-2024 19:30:55	notice	US 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;
28-01-2024 18:21:34	notice	US 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;
28-01-2024 18:21:34	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;
28-01-2024 14:58:45	notice	US 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;
28-01-2024 14:58:45	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;
28-01-2024 13:50:07	notice	US 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;
28-01-2024 13:50:07	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;
28-01-2024 01:51:53	notice	US 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;
28-01-2024 01:51: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;
28-01-2024 01:21:20	notice	US 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;
28-01-2024 01:21:20	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;
28-01-2024 01:20:55	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;
28-01-2024 01:20:55	notice	US 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;
28-01-2024 01:20:31	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;
28-01-2024 01:20:04	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
28-01-2024 01:19:54	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-01-2024 13:34: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;
27-01-2024 13:34:02	notice	US 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;
27-01-2024 13:33:58	notice	REGISTRATION COMPLETE - Waiting for Operational status
27-01-2024 13:33:53	warning	Dynamic Range Window violation
27-01-2024 13:33:53	warning	RNG-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;
27-01-2024 13:33:53	warning	RNG-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;
27-01-2024 13:33:53	warning	Dynamic Range Window violation
27-01-2024 13:33:53	warning	Dynamic Range Window violation
27-01-2024 13:33:53	warning	RNG-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;
27-01-2024 13:33:52	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;
27-01-2024 13:33:46	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;
27-01-2024 13:33:39	warning	DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-01-2024 13:33:37	notice	Honoring MDD; IP provisioning mode = IPv4
27-01-2024 13:33:21	critical	Cable Modem Reboot because of - HW or Power-On Reset
27-01-2024 13:33:21	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

[TiPs1]

Just to add, I have also checked the service status phone number and online and no faults for broadband have been raised in my area.

I just find it strange that this has only happened within the last 1-2 weeks which is making me think something has been done in the area.

[TiPs1]

Went on the Virgin Media website last night to check again the service status and to check for any faults on my line. It prompted I had to factory reset my hub for some reason which I have done. After the reset the connection was even worse and to the point I just stopped playing online games as no matter what game I played I was getting spikes of lag. Looking at the graph it also shows spikes which I am guessing is what I was experiecing. Can someone from Virgin please take a look at my connection and my area as this has only started happening within the last 1-2 weeks! - Connection was perfect before then and nothing in my home has changed. Always have been hardwired.

Latest Graph for the last 24hrs

[TiPs1]

Disapointed someone from Virgin has still not messaged regarding this issue I am having. Its clear as day its mostly happening at peak times which is making me think its a Utilisation issue as its mostly always happening during peak times. See below my latest BQM results and also my latest router logs and power levels.

Tuesday 30/01/2024

Wednesday 31/01/2024

Thursday 01/02/2024  (upto 8am) (Some sort of outage during the night)

3.0 Downstream channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

1	235000000	1.1	41	QAM 256	13
2	139000000	2.3	40	QAM 256	1
3	147000000	2.2	40	QAM 256	2
4	155000000	2.1	40	QAM 256	3
5	163000000	1.7	40	QAM 256	4
6	171000000	1.5	40	QAM 256	5
7	179000000	1.3	40	QAM 256	6
8	187000000	1.4	40	QAM 256	7
9	195000000	1.5	41	QAM 256	8
10	203000000	1.4	41	QAM 256	9
11	211000000	1.5	41	QAM 256	10
12	219000000	1.3	41	QAM 256	11
13	227000000	1.3	41	QAM 256	12
14	243000000	0.5	41	QAM 256	14
15	251000000	0.1	40	QAM 256	15
16	259000000	0.1	40	QAM 256	16
17	267000000	0.3	41	QAM 256	17
18	275000000	0.1	41	QAM 256	18
19	283000000	0.1	41	QAM 256	19
20	291000000	0.1	41	QAM 256	20
21	299000000	0.1	41	QAM 256	21
22	307000000	0	40	QAM 256	22
23	315000000	0.1	40	QAM 256	23
24	323000000	0.3	40	QAM 256	24
25	331000000	0.5	40	QAM 256	25
26	339000000	0.4	40	QAM 256	26
27	347000000	0.4	41	QAM 256	27
28	355000000	0.5	41	QAM 256	28
29	363000000	0.5	41	QAM 256	29
30	371000000	-1.1	41	QAM 256	30
31	379000000	-2.1	40	QAM 256	31
32	387000000	-2.3	40	QAM 256	32

3.0 Downstream channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors

1	Locked	41	1	0
2	Locked	40	5	0
3	Locked	40	5	0
4	Locked	40	9	8
5	Locked	40	5	7
6	Locked	40	5	7
7	Locked	40	8	6
8	Locked	40	12	7
9	Locked	41	7	8
10	Locked	41	4	8
11	Locked	41	8	8
12	Locked	41	12	8
13	Locked	41	6	7
14	Locked	41	9	9
15	Locked	40	3	8
16	Locked	40	8	0
17	Locked	41	8	0
18	Locked	41	5	0
19	Locked	41	3	0
20	Locked	41	6	0
21	Locked	41	4	0
22	Locked	40	3	0
23	Locked	40	6	0
24	Locked	40	7	0
25	Locked	40	12	0
26	Locked	40	5	0
27	Locked	41	2	0
28	Locked	41	2	0
29	Locked	41	1	0
30	Locked	41	1	0
31	Locked	40	2	0
32	Locked	40	0	0

3.1 Downstream channels

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

159

94

4K

1840

QAM 4096

1108

3.1 Downstream channels

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

159

Locked

40

-3.9

3464770279

4307

3.0 Upstream channels

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

0	49600000	51.3	5120	QAM 64	1
1	43100000	50.5	5120	QAM 64	2
2	36600000	50.3	5120	QAM 64	3
3	30100000	50	5120	QAM 64	4
4	23600000	48.8	5120	QAM 64	5

3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

0	ATDMA	0	15	2	0
1	ATDMA	0	15	0	0
2	ATDMA	0	15	0	0
3	ATDMA	0	15	0	0
4	ATDMA	0	15	5	0

3.1 Upstream channels

Channel Channel Width (MHz) Power (dBmV) FFT Type Modulation

6

10

46.0

2K

QAM 256

3.1 Upstream channels

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

6

OFDMA

200

74000000

0

0

Network Log

Time Priority Description

01-02-2024 01:55:25	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-02-2024 01:55:22	critical	No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-02-2024 01:55:00	warning	TCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-02-2024 01:55:00	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-02-2024 01:54:00	notice	US 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;
01-02-2024 01:54:00	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;
01-02-2024 01:53:56	critical	No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-02-2024 01:53:56	notice	REGISTRATION COMPLETE - Waiting for Operational status
01-02-2024 01:53:56	warning	TCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-02-2024 01:53:47	warning	Dynamic Range Window violation
01-02-2024 01:53:47	warning	RNG-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;
01-02-2024 01:53:46	warning	RNG-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;
01-02-2024 01:53:46	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;
01-02-2024 01:53:46	warning	RNG-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;
01-02-2024 01:53:46	warning	Dynamic Range Window violation
01-02-2024 01:53:46	warning	Dynamic Range Window violation
01-02-2024 01:53:46	warning	Dynamic Range Window violation
01-02-2024 01:53:46	warning	RNG-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;
01-02-2024 01:53:41	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;
01-02-2024 01:53:34	warning	DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-02-2024 01:53:31	notice	Honoring MDD; IP provisioning mode = IPv4
01-02-2024 01:50:46	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-02-2024 01:50:45	critical	SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-02-2024 01:32:50	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-02-2024 01:32:49	critical	SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-02-2024 01:32:26	critical	SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-02-2024 01:32:26	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-02-2024 01:24:15	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-02-2024 01:24:11	warning	ToD request sent - No Response received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-02-2024 01:24:10	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;
01-02-2024 01:23:50	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;
01-02-2024 01:23:50	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

[TiPs1]

Bufferbloat Test at 11:25am (01/02/2024)

BQM so far for today 01/02/2024 (11:30am)

[jpeg1]

Apart from the gap at 2am which was probably network switching, your BQM isn't bad. Those spikes probably coincide with something else on your own network. Do a couple of speedtests and you'll see spikes like those. 

[TiPs1]

The BQM is bad enough to affect my gaming online which I said previously has started with these lag spikes within the last 1-2 weeks. Peak times has become a joke and occassional rubber banding on games. Spikes are showing on the BQM when no one is using the broadband ... especially very late at night and early morning it spikes but everyone is asleep. Something has happened within the last 1-2 weeks in my area which is effecting my network now. No changes have been made in my house

[jpeg1]

I don't doubt that you are having gaming problems with lagging. I'm only saying that your BQM is not a particularly bad one, and better than many.

[legacy1]

You think how many packets of coordinated player positioning and firing of a gun happens in just one second that you go from 20mins-40 max ms to 100ms delay and normally more its a problem its the consistency of the connection that the server must depend on some jitter OK the odd spike thats not by much OK but when you push beyond that its a mess.

Like I know I'm doing everything possible to not cause a ping spike by doing BWM or QoS and being on the low speed to not be hit routers upstream from impacting the flow to me or from me but even now I spike high in BQM at times.