Virgin Media Community

[BaronVonStrudel]

Hi guys

My Broadband connection keeps dropping out.  This seems related to the upload.  As whenever i test the upload at speediest it gives me terrible speeds of less than 10 mbits, then the connection completely drops out during the test.  This has been happening for the last couple of days.  My network log on my router has been logging critical errors as the connection drops out 

03-01-2022 13:04:38	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-01-2022 06:14:04	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-01-2022 06:13:56	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-01-2022 06:13:52	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;

I cant game or even chat on discord without the connection eventually dropping out on me every 10 minutes or so.

Any help would be appreciated.  

Thanks

[Adduxi]

Please post the power level stats from the Hub. Just copy and paste into several posts 

[BaronVonStrudel]

Downstream bonded channels

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

1	155000000	6.5	39	QAM 256	3
2	139000000	6.6	39	QAM 256	1
3	147000000	6.5	39	QAM 256	2
4	163000000	6.6	39	QAM 256	4
5	171000000	6.5	39	QAM 256	5
6	179000000	6.5	39	QAM 256	6
7	187000000	6.6	39	QAM 256	7
8	195000000	6.9	39	QAM 256	8
9	203000000	6.8	39	QAM 256	9
10	211000000	7.1	39	QAM 256	10
11	219000000	7.3	39	QAM 256	11
12	227000000	7.4	40	QAM 256	12
13	235000000	7.3	39	QAM 256	13
14	243000000	7.1	40	QAM 256	14
15	251000000	7.3	40	QAM 256	15
16	259000000	7.3	40	QAM 256	16
17	267000000	7.1	40	QAM 256	17
18	275000000	7.2	40	QAM 256	18
19	283000000	7.4	40	QAM 256	19
20	291000000	7.4	40	QAM 256	20
21	299000000	7.1	40	QAM 256	21
22	307000000	7.2	40	QAM 256	22
23	315000000	7.3	40	QAM 256	23
24	323000000	7.1	40	QAM 256	24
25	331000000	6.8	40	QAM 256	25
26	339000000	6.9	39	QAM 256	26
27	347000000	7.1	40	QAM 256	27
28	355000000	6.8	41	QAM 256	28
29	363000000	6.6	41	QAM 256	29
30	371000000	6.7	41	QAM 256	30
31	379000000	6.9	41	QAM 256	31

Downstream bonded channels

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

1	Locked	39	16782	119412
2	Locked	39	317422	294502
3	Locked	39	6166	1991
4	Locked	39	186286	725439
5	Locked	39	10352	1250
6	Locked	39	109002	649012
7	Locked	39	0	152788
8	Locked	39	0	27
9	Locked	39	0	2
10	Locked	39	0	11
11	Locked	39	0	42
12	Locked	40	0	188
13	Locked	39	0	355
14	Locked	40	0	672
15	Locked	40	0	411
16	Locked	40	0	217
17	Locked	40	0	58
18	Locked	40	0	9
19	Locked	40	0	2
20	Locked	40	0	0
21	Locked	40	0	0
22	Locked	40	0	0
23	Locked	40	0	0
24	Locked	40	0	0
25	Locked	40	0	0
26	Locked	39	0	0
27	Locked	40	0	0
28	Locked	41	0	0
29	Locked	41	0	0
30	Locked	41	0	0
31	Locked	41	0	0

[BaronVonStrudel]

Upstream bonded channels

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

1	60300000	44.5	5120	QPSK	1
2	53700000	44.3	5120	QPSK	2
3	39400000	44	5120	QPSK	4

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1	ATDMA	0	13	0	0
2	ATDMA	0	13	0	0
3	ATDMA	0	13	0	0

[BaronVonStrudel]

Here's a list of network errors just from the last 20 minutes.  The connection is even more unstable now.  Basically unusable 

Network Log

Time Priority Description

03-01-2022 16:37:30	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-01-2022 16:37:22	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-01-2022 16:37:17	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;
03-01-2022 16:37:15	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-01-2022 16:37:14	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;
03-01-2022 16:37:06	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-01-2022 16:37:06	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;
03-01-2022 16:37:05	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-01-2022 16:37:04	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;
03-01-2022 16:33:13	critical	16 consecutive T3 timeouts while trying to range on upstream channel 4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-01-2022 16:33:13	critical	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-01-2022 16:33:13	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-01-2022 16:32:06	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-01-2022 16:24:06	critical	16 consecutive T3 timeouts while trying to range on upstream channel 4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-01-2022 16:24:06	critical	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-01-2022 16:20:54	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-01-2022 16:20:34	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-01-2022 16:20:34	critical	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-01-2022 16:20:34	critical	16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-01-2022 16:20:33	critical	16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-01-2022 16:20:33	critical	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-01-2022 16:19:18	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-01-2022 16:19:16	critical	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-01-2022 16:19:16	critical	16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-01-2022 16:17:17	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-01-2022 16:17:17	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-01-2022 16:16:54	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;
03-01-2022 16:13:56	critical	16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-01-2022 16:13:56	critical	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-01-2022 16:13:32	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-01-2022 16:13:27	critical	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-01-2022 16:13:27	critical	16 consecutive T3 timeouts while trying to range on upstream channel 4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

[legacy1]

your upstream Modulation is low.

[Zach_R]

Hi @BaronVonStrudel,

Thank you for your posts. We're here to help.

I'm really sorry to hear you're having some issues with your connection lately. Can you please set up and share with us a live BQM so that we can take a closer look at what's going on with your connection?

Thanks,
 

[BaronVonStrudel]

I currently can't post anything as my connection doesn't remain stable enough . I'm posting this from my mobile phone.  Do I need a thinkbroadband account to post a live bqm graph?  

[BaronVonStrudel]

It settled down long enough for me to sign up and post

https://www.thinkbroadband.com/broadband/monitoring/quality/share/0199012695d6ccb421fd15ac11dc128e9b78e364

[BaronVonStrudel]

Hey Zach, sorry i meant to mention . That last night the connection became stable and full speed for a little while.  The upload modulation changed from QPSK to QAM64, if i remember correctly.  The connection became stable and full speed.  When i got up this morning it was worse than ever and the upload modulation had switched back to QPSK.   I dont know if its at all related but i know the connection only becomes unstable when im uploading. For example a speed test will usually halt on the upload test cycle.  Giving either an error or the router will crap out completely and lose connectivity giving me network log errors.  I also meant to mention that im on a wired connection to the new HUB 5.

Thanks