Regular ping spikes every hour

[whuboy]

Hi all,

I have been experiencing regular ping spikes to over 1000ms at seemingly regular intervals, occurring about 45mins past the hour, every hour, as can be seen on the BQM below:

https://www.thinkbroadband.com/broadband/monitoring/quality/share/18a1986e7ef6e040ce7de5d0efbf916faee83d81

When playing games and on video calls I rarely disconnect, but the connection is unusable for a few minutes.

Due to the regularity I thought it might be related to a service such as OneDrive, doing regular synchronisations but after disabling I haven't seen any improvement. 

I would appreciate any suggestions as to what the issue could be

[whuboy]

3.0 Downstream channels

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

8	194750000	11.300003	38.983261	QAM256	8
1	138750000	11.300003	38.605377	QAM256	1
2	146750000	10.900002	38.605377	QAM256	2
3	154750000	10.900002	38.983261	QAM256	3
4	162750000	11.000000	38.983261	QAM256	4
5	170750000	11.000000	38.983261	QAM256	5
6	178750000	11.000000	38.983261	QAM256	6
7	186750000	11.099998	38.605377	QAM256	7
9	202750000	11.199997	38.605377	QAM256	9
10	210750000	11.199997	38.605377	QAM256	10
11	218750000	11.199997	38.983261	QAM256	11
12	226750000	11.099998	38.983261	QAM256	12
13	234750000	11.199997	38.983261	QAM256	13
14	242750000	11.300003	38.983261	QAM256	14
15	250750000	11.099998	38.605377	QAM256	15
16	258750000	11.599998	38.983261	QAM256	16
17	266750000	11.900002	38.983261	QAM256	17
18	274750000	12.300003	38.983261	QAM256	18
19	282750000	12.099998	38.983261	QAM256	19
20	290750000	11.900002	38.983261	QAM256	20
21	298750000	12.000000	38.983261	QAM256	21
22	306750000	12.099998	38.983261	QAM256	22
23	314750000	12.500000	38.605377	QAM256	23
24	322750000	12.400002	38.983261	QAM256	24
25	330750000	12.400002	38.983261	QAM256	25
26	338750000	12.500000	38.983261	QAM256	26
27	346750000	12.500000	38.983261	QAM256	27
28	354750000	12.199997	38.983261	QAM256	28
29	362750000	12.199997	38.983261	QAM256	29
30	370750000	12.099998	38.983261	QAM256	30
31	378750000	12.099998	38.983261	QAM256	31

[whuboy]

3.0 Downstream channels

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

8	Locked	38.983261	0	0
1	Locked	38.605377	0	0
2	Locked	38.605377	0	0
3	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
9	Locked	38.605377	0	0
10	Locked	38.605377	0	0
11	Locked	38.983261	0	0
12	Locked	38.983261	0	0
13	Locked	38.983261	0	0
14	Locked	38.983261	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	0	0
20	Locked	38.983261	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	0	0
26	Locked	38.983261	0	0
27	Locked	38.983261	0	0
28	Locked	38.983261	0	0
29	Locked	38.983261	0	0
30	Locked	38.983261	0	0
31	Locked	38.983261	0	0

[whuboy]

3.0 Downstream channels

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

8	194750000	11.4	39	QAM256	8
1	138750000	11.5	38.6	QAM256	1
2	146750000	11.1	38.6	QAM256	2
3	154750000	11	38.6	QAM256	3
4	162750000	11.1	38.6	QAM256	4
5	170750000	11.1	39	QAM256	5
6	178750000	11.2	38.6	QAM256	6
7	186750000	11.2	39	QAM256	7
9	202750000	11.4	38.6	QAM256	9
10	210750000	11.3	39	QAM256	10
11	218750000	11.4	39	QAM256	11
12	226750000	11.3	38.6	QAM256	12
13	234750000	11.4	38.6	QAM256	13
14	242750000	11.4	39	QAM256	14
15	250750000	11.3	39	QAM256	15
16	258750000	11.7	39	QAM256	16
17	266750000	12.1	39	QAM256	17
18	274750000	12.5	38.6	QAM256	18
19	282750000	12.3	39	QAM256	19
20	290750000	12.1	39	QAM256	20
21	298750000	12.1	39	QAM256	21
22	306750000	12.3	39	QAM256	22
23	314750000	12.7	40.4	QAM256	23
24	322750000	12.5	38.6	QAM256	24
25	330750000	12.5	39	QAM256	25
26	338750000	12.6	39	QAM256	26
27	346750000	12.6	40.4	QAM256	27
28	354750000	12.4	40.4	QAM256	28
29	362750000	12.3	39	QAM256	29
30	370750000	12.3	39	QAM256	30
31	378750000	12.2	39	QAM256	31

[whuboy]

3.1 Downstream channels

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

33

94

4K

1840

QAM4096

424

3.1 Downstream channels

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

33

Locked

42

11.8

1427887574

14529

3.0 Upstream channels

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

1	25800000	38.8	5120 KSym/sec	32QAM	4
2	46200000	38.5	5120 KSym/sec	64QAM	1
3	39400000	38.8	5120 KSym/sec	64QAM	2
4	32600000	39	5120 KSym/sec	64QAM	3

3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

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

[whuboy]

Network Log

Time Priority Description

Wed 03/08/2022 06:38:45	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 06/08/2022 04:37:40	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 07/08/2022 03:24:19	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 09/08/2022 16:37:40	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 14/08/2022 01:25:27	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 16/08/2022 16:37:40	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 22/08/2022 20:07:40	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 23/08/2022 16:37:40	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 25/08/2022 11:08:01	3	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 25/08/2022 11:08:05	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 25/08/2022 11:08:07	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 25/08/2022 11:08:10	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;
Thu 25/08/2022 11:08:10	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 25/08/2022 11:08:12	6	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 25/08/2022 11:08:16	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 25/08/2022 11:08:24	6	CM-STATUS message sent. Event Type Code: 5; Chan ID: 23; 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;
Sat 27/08/2022 04:37:40	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 27/08/2022 15:05:48	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 30/08/2022 16:37:40	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 02/09/2022 17:35:35	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/09/2022 04:37:40	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 04/09/2022 04:44:30	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 06/09/2022 16:37:40	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 08/09/2022 03:32:51	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 10/09/2022 04:37:40	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 12/09/2022 14:03:50	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 12/09/2022 15:54:42	5	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 13/09/2022 21:37:24	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 14/09/2022 22:16:20	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 17/09/2022 06:27:59	5	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

[Natalie_L]

Hi whuboy, 

Welcome to the Community and thank you for posting. 

I am very sorry to hear you are experiencing issues with your connection, we will do all we can to help. 

Can you please confirm which Hub you have with us and when it was last rebooted? 

Can you also please check that the cables leading to and from the Hub are secure with no damage? 

If the issue is still occurring today, can you also please run a quick check for any known issues here? 

Thank you, 

[legacy1]

Its caused by VM doing DoS speed tests to the hub you can either ask to have this pointless test off EVERY hour or use hub in modem mode.

And looking at your live BQM packet loss is not good

[whuboy]

Thank you for your reply Legacy, to turn this off do I need to contact VM or can I disable this in settings?

[David_Bn]

Good Morning @whuboy, thanks for your post, can you please advise us how the connection has been performing since your most recent post?

Do you still have a BQM running and is it still showing the ping spikes? 

Kindest regards,

David_Bn