Virgin Media Community

[LochyMacleod]

Every few minutes my connection will completely drop for 10-30 seconds making 99% of online games unplayable. 

So not only games but discord and i cant even load a webpage when it does it. 

Its been doing this for the past 24 hours at least..

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

Th red bars on the BQM is me resetting the hub. 

[LochyMacleod]

Refresh data

3.0 Downstream channels

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

25	331000000	5.3	37.4	QAM256	25
1	139000000	4.8	35.8	QAM256	1
2	147000000	4.8	35.8	QAM256	2
3	155000000	5	36.4	QAM256	3
4	163000000	5.1	36.4	QAM256	4
5	171000000	4.7	36.6	QAM256	5
6	179000000	4.5	36.6	QAM256	6
7	187000000	4.5	36.6	QAM256	7
8	195000000	4.7	36.6	QAM256	8
9	203000000	4.8	36.6	QAM256	9
10	211000000	5	36.6	QAM256	10
11	219000000	5.1	36.6	QAM256	11
12	227000000	5.4	37.4	QAM256	12
13	235000000	5.7	36.6	QAM256	13
14	243000000	5.9	37.6	QAM256	14
15	251000000	5.7	36.6	QAM256	15
16	259000000	5.8	37.4	QAM256	16
17	267000000	5.4	37.4	QAM256	17
18	275000000	5.5	37.4	QAM256	18
19	283000000	6	37.4	QAM256	19
20	291000000	6.3	37.4	QAM256	20
21	299000000	6.6	37.6	QAM256	21
22	307000000	6	37.6	QAM256	22
23	315000000	5.5	37.4	QAM256	23
24	323000000	5.1	37.4	QAM256	24
26	339000000	5.7	37.6	QAM256	26
27	347000000	4.6	36.6	QAM256	27
28	355000000	4.6	37.4	QAM256	28
29	363000000	4.6	37.4	QAM256	29
30	371000000	4.7	37.4	QAM256	30
31	379000000	4.7	37.6	QAM256	31

3.0 Downstream channels

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

25	Locked	37.355988	0	0
1	Locked	35.779911	3	0
2	Locked	35.779911	0	0
3	Locked	36.386890	1	0
4	Locked	36.386890	0	0
5	Locked	36.609653	0	0
6	Locked	36.609653	0	0
7	Locked	36.609653	0	0
8	Locked	36.609653	0	0
9	Locked	36.609653	0	0
10	Locked	36.609653	0	0
11	Locked	36.609653	0	0
12	Locked	37.355988	0	0
13	Locked	36.609653	0	0
14	Locked	37.636276	0	0
15	Locked	36.609653	0	0
16	Locked	37.355988	0	0
17	Locked	37.355988	0	0
18	Locked	37.355988	0	0
19	Locked	37.355988	0	0
20	Locked	37.355988	0	0
21	Locked	37.636276	0	0
22	Locked	37.636276	0	0
23	Locked	37.355988	0	0
24	Locked	37.355988	0	0
26	Locked	37.636276	0	0
27	Locked	36.609653	0	0
28	Locked	37.355988	0	0
29	Locked	37.355988	0	0
30	Locked	37.355988	0	0
31	Locked	37.636276	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

424

3.1 Downstream channels

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

33

Locked

38

3.2

36322316

0

 

[LochyMacleod]

3.0 Upstream channels

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

1	32600000	41	5120 KSym/sec	64QAM	5
2	39400000	40.8	5120 KSym/sec	64QAM	4
3	46200000	40.5	5120 KSym/sec	64QAM	3
4	25800000	41.8	5120 KSym/sec	64QAM	6

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

General Configuration

Network access	true
Maximum Number of CPEs	1
Baseline Privacy	true
DOCSIS Mode	3.1
Config file	cmreg-vmdg640-bbt076+voc-b.cm

Primary Downstream Service Flow

SFID	4812
Max Traffic Rate	1230000450
Max Traffic Burst	42600
Min Traffic Rate	0

Primary Upstream Service Flow

SFID	4811
Max Traffic Rate	55000270
Max Traffic Burst	42600
Min Traffic Rate	0
Max Concatenated Burst	42600
Scheduling Type	bestEffort

[LochyMacleod]

Network Log

Time Priority Description

Wed 27/04/2022 23:19:06	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 28/04/2022 04:30:49	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 30/04/2022 04:41:11	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 01/05/2022 16:30:49	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 02/05/2022 20:37:42	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 05/05/2022 04:30:49	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 07/05/2022 06:31:26	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 08/05/2022 16:30:49	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 09/05/2022 21:02:29	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 12/05/2022 04:30:49	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 23/05/2022 04:38:17	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 26/05/2022 04:30:49	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 27/05/2022 00:17:38	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 29/05/2022 16:30:49	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 31/05/2022 00:33:13	3	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 31/05/2022 00:33:17	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 31/05/2022 00:35:33	3	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;
Tue 31/05/2022 00:36:22	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 31/05/2022 00:36:31	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 31/05/2022 00:36:31	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 31/05/2022 00:36:35	6	CM-STATUS message sent. Event Type Code: 4; Chan ID: 7; 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 31/05/2022 00:36:36	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 31/05/2022 00:36:37	6	CM-STATUS message sent. Event Type Code: 5; Chan ID: 5; 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 31/05/2022 00:36:39	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 31/05/2022 00:40:32	3	Ranging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 31/05/2022 00:40:32	3	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 31/05/2022 00:40:33	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 31/05/2022 00:41:09	3	Ranging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 31/05/2022 00:41:09	3	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 31/05/2022 00:41:09	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 31/05/2022 00:41:33	3	Ranging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 31/05/2022 00:41:33	3	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 31/05/2022 00:41:59	3	Ranging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 31/05/2022 00:41:59	3	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 31/05/2022 00:42:40	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 31/05/2022 00:43:58	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 31/05/2022 00:44:01	3	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 31/05/2022 21:41:03	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 02/06/2022 20:37:37	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 02/06/2022 23:04:29	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 06/06/2022 01:04:32	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 07/06/2022 01:32:57	3	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 07/06/2022 01:32:59	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 07/06/2022 01:35:53	3	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 07/06/2022 01:35:55	6	CM-STATUS message sent. Event Type Code: 5; Chan ID: 30; 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 07/06/2022 01:35:58	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 07/06/2022 01:35:58	6	CM-STATUS message sent. Event Type Code: 4; 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;
Thu 09/06/2022 13:04:33	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 10/06/2022 21:38:31	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 12/06/2022 16:26:06	5	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

[LochyMacleod]

 This is my sam knows but even with only 93mb i should be getting full drops in connection. Usually this is fixed with a hub reset though. Yesterday when i ws having these issues my sam knows was showing full speed. 

[LochyMacleod]

Also im on a fully wired connection. Direct from my hub to my PC.

It was also happening on both my sons Xbox Series X's and they are fully wired too.

[Carley_S]

Hi LochyMacleod

Welcome back to the community. 

Sorry to hear you're currently experiencing connection issues. Thank you for posting your hub log and BQM link. 

I can't see any issues on our side either that might be causing these connection and speed concerns. There are also no area concerns. Has this issue just started to occur? Have you made any changes at all to your equipment? What ethernet categories are you using? Does your WiFi devices also have similar speeds that never exceed 94mbps?

Please can you try a 60 second pin hole reset on the router. This will revert any customisations back to factory settings and full update the router with firmware/software updates. Please do not reboot the router whilst it is completing the pin hole request.