Continuing latency spikes

[s_curtis]

Following on from my previous post, the problem still remains even after an engineer visit. It did appear to be improved for a day or so and before returning to a lesser extent than before. However in the last few weeks it has become increasingly problematic. 

While doing some further research and testing, I remembered a discussion on reddit that about Puma chipset in the SH3/4 and an issue handling UDP packets. 

I added an openVPN connection using TCP to my pfSense box and routed my gaming PC's traffic through this interface. For several days I experienced no disconnects while playing so thought I'd found a workaround (albeit not ideal) but then the problem returned with a vengeance. 

Towards the end of July I received an email to say that VM were going to be 'carrying out essential works to improve our network', a week later and this still unfortunately has clearly not improved anything for me. Whilst playing last night for I lost connection to the game 5 times within an hour  which is totally unacceptable.

Checking my BQM monitor for the past month shows large latency spikes throughout the day and especially in the evenings.

I also noticed yesterday while doing some work in my garden that when the engineer last visited and re-terminated the connections he failed to replace the cover where the cables are presented, therefore leaving them exposed to the elements.

I've been a customer with VM and all it's predecessors right the way back to Cable Corporation and a dialup modem. I don't particuarly want to leave since I have TV, phone and broadband but unless this problem is resolved ASAP I am seriously considering given notice when my contract ends in November, especially as Community Fibre is now available in my street.

https://www.thinkbroadband.com/broadband/monitoring/quality/share/b3c76e4d4c4faf84b11faea90f1ce09e6a... 

[s_curtis]

3.0 Downstream channels

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

3	155000000	0.9	39	QAM256	3
1	139000000	1	39	QAM256	1
2	147000000	1.1	39	QAM256	2
4	163000000	0.6	39	QAM256	4
5	171000000	0.1	39	QAM256	5
6	179000000	-0.1	39	QAM256	6
7	187000000	-0.2	38.6	QAM256	7
8	195000000	-0.4	39	QAM256	8
9	203000000	-0.3	38.6	QAM256	9
10	211000000	-0.5	39	QAM256	10
11	219000000	-0.7	39	QAM256	11
12	227000000	-0.7	38.6	QAM256	12
13	235000000	-0.8	39	QAM256	13
14	243000000	-0.6	38.6	QAM256	14
15	251000000	-0.7	38.6	QAM256	15
16	259000000	-0.6	39	QAM256	16
17	267000000	-0.5	39	QAM256	17
18	275000000	-0.4	39	QAM256	18
19	283000000	-0.1	39	QAM256	19
20	291000000	-0.2	38.6	QAM256	20
21	299000000	-0.4	39	QAM256	21
22	307000000	-0.9	39	QAM256	22
23	315000000	-1.2	38.6	QAM256	23
24	323000000	-1.6	39	QAM256	24
25	331000000	-1.6	39	QAM256	25
26	339000000	-1.4	38.6	QAM256	26
27	347000000	-1.4	39	QAM256	27
28	355000000	-1.3	38.6	QAM256	28
29	363000000	-1.4	39	QAM256	29
30	371000000	-1.5	39	QAM256	30
31	379000000	-1.6	38.6	QAM256	31

3.0 Downstream channels

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

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

3.1 Downstream channels

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

33

96

4K

1880

QAM4096

392

3.1 Downstream channels

Channel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)

33

Locked

40

-2.4

9488650

0

[s_curtis]

3.0 Upstream channels

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

1	46200000	44	5120 KSym/sec	64QAM	3
2	39400000	43.8	5120 KSym/sec	64QAM	4
3	60300000	45	5120 KSym/sec	64QAM	1
4	53700000	44.5	5120 KSym/sec	64QAM	2

3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1	US_TYPE_STDMA	0	0	0	0
2	US_TYPE_STDMA	0	0	0	0
3	US_TYPE_STDMA	0	0	0	0
4	US_TYPE_STDMA	0	0	0	0

 

Network Log

Time Priority Description

Thu 01/01/1970 00:01:20	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 11/08/2022 22:14:24	5	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 14/08/2022 02:08:11	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 14/08/2022 11:36:12	5	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 14/08/2022 11:36:23	5	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 16/08/2022 10:43:38	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 16/08/2022 23:33:45	3	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 16/08/2022 23:33:48	6	CM-STATUS message sent. Event Type Code: 2; Chan ID: 3; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 16/08/2022 23:33:50	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 16/08/2022 23:36:19	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 16/08/2022 23:36:24	6	CM-STATUS message sent. Event Type Code: 4; Chan ID: 2; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 16/08/2022 23:36:25	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 16/08/2022 23:36:34	6	CM-STATUS message sent. Event Type Code: 23; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 16/08/2022 23:36:35	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 16/08/2022 23:41:26	3	Ranging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 16/08/2022 23:41:26	3	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 16/08/2022 23:41:30	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 16/08/2022 23:42:29	3	Ranging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 16/08/2022 23:42:29	3	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 16/08/2022 23:42:44	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 16/08/2022 23:43:08	3	Ranging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 16/08/2022 23:43:08	3	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 16/08/2022 23:43:35	3	Ranging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 16/08/2022 23:43:36	3	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 16/08/2022 23:44:03	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 16/08/2022 23:44:31	5	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 18/08/2022 20:36:25	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 19/08/2022 11:17:48	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 01/01/1970 00:01:18	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 25/08/2022 15:23:16	5	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 27/08/2022 19:20:27	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 30/08/2022 11:14:36	6	CM-STATUS message sent. Event Type Code: 5; Chan ID: 4; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 30/08/2022 11:14:37	3	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 30/08/2022 11:14:40	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 30/08/2022 11:15:06	3	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 30/08/2022 11:15:07	6	CM-STATUS message sent. Event Type Code: 5; Chan ID: 24; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 30/08/2022 11:15:10	3	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 30/08/2022 11:15:11	6	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 30/08/2022 11:15:13	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 30/08/2022 11:15:14	6	CM-STATUS message sent. Event Type Code: 4; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

[legacy1]

You don't have the worst BQM their might not be much that can be done short from VM adding more upstream.

I take it your connection was idle when just gaming? As a test you could setup QoS/BWM on pfSense with 9280Kb up and 92160Kb download to see if spike go down for the BQM.

[Travis_M]

Hi @s_curtis

Thank you for the reply

I am going to drop you a private message now to collect some more information and investigate further, please keep an eye on your inbox.

Regards

[Travis_M]

Hi @s_curtis

Good morning and thanks for your reply when confirming those details via Private Message. 

Please keep us updated with how your connection is today after the reboot and we can look further into this if needs be.

Regards