Hi there, We are having persistent issues with high latency and high jitter which are affecting our home networkThe network logs show T3 time-out. I restarted the Hub 3.0 since the last once at 9am. We've had this issue previously and it was fixed when an engineer visited the box in the street. We have on-curb parking in our street and unfortunately for us the network box is INSIDE a parking space and it has been hit and knocked over several times. Please advise if the Network Status stats and logs look good and if we can get an engineer to look at the box in the street. Network Log TimePriorityDescription26/08/2025 11:58:28noticeLAN login Success; [REMOVED]26/08/2025 09:09:14Warning!TCS Partial Service;[REMOVED]26/08/2025 09:09:14Warning!Initializing Channel Timeout Expires - Time the CM can perform initial ranging on all upstream channels in the TCS has expired;[REMOVED]25/08/2025 15:01:40criticalNo Ranging Response received - T3 time-out;[REMOVED]25/08/2025 06:30:8noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;[REMOVED]25/08/2025 06:30:8ErrorDHCP RENEW WARNING - Field invalid in response v4 option;[REMOVED]22/08/2025 03:57:17criticalNo Ranging Response received - T3 time-out;[REMOVED]21/08/2025 18:30:8noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;[REMOVED]21/08/2025 18:30:8ErrorDHCP RENEW WARNING - Field invalid in response v4 option;[REMOVED]18/08/2025 12:08:22criticalNo Ranging Response received - T3 time-out;[REMOVED]18/08/2025 06:30:7noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;[REMOVED]18/08/2025 06:30:7ErrorDHCP RENEW WARNING - Field invalid in response v4 option;[REMOVED]15/08/2025 03:43:43criticalNo Ranging Response received - T3 time-out;[REMOVED]14/08/2025 18:30:7noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;[REMOVED]14/08/2025 18:30:7ErrorDHCP RENEW WARNING - Field invalid in response v4 option;[REMOVED]11/08/2025 11:14:20criticalNo Ranging Response received - T3 time-out;[REMOVED]11/08/2025 06:30:2noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;[REMOVED]11/08/2025 06:30:2ErrorDHCP RENEW WARNING - Field invalid in response v4 option;[REMOVED]10/08/2025 01:59:11criticalNo Ranging Response received - T3 time-out;[REMOVED]07/08/2025 18:30:2noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;[REMOVED] [MOD EDIT: MAC addresses removed]

Hi yorkieboy123 Thanks for coming back to us. We're glad to hear the area fault is resolved but sorry to hear you're still having issues. According to our diagnostics, the Hub is in Modem Mode. Can you pop it in Router Mode for us please to run full checks? Best wishes.

Just to keep a record of the state of things.Here's today's BQM graph 9am (on router mode as requested)The hub 3 now periodically stops responding to WAN ping and the only thing I can do to reinstate the BQM is restart the hub 3 IF I notice the BQM is down.Interestingly, I read online that switching off IP flooding protection might improve my latency but having turned this off at 2.30pm 8th Sep, you can see above it made no difference. I'm switching this back on now.A Virgin engineer is coming to my flat tomorrow to investigate. We've had someone come before about a year ago, they replaced all the hardware including the hub3 for a different hub 3 but this didn't improve things that much. I truly believe the issue is that the Cabinet is literally inside a parking space outside my house (as we have on curb parking) and people keep crashing into the cabinet and even knocking it over. It must be damaged surely.

OK an update. Firstly DO NOT CLOSE my complaint C-2208252379.The engineer came today and replaced all the cabling and removed a splitter that wasn't required and then upgraded me from a Superhub3 to a Superhub5.I'm still having issues. I am aware VM will tell me to wait 24h for the signal to "settle" - It will have been 24h at 10.30am tomorrow. I've already had a 30min period of full signal drop from 20.30-21.00 the evening (see BQM below). The new hub hasn't resolved my issues. The network logs suggest the issue is upstream, although apparently the channels all look OK on my router log page (see below). It's not a hardware issue with the gear at my house as it was all replaced this morning. I don't want to get stuck in an infinite loop of having the hub replaced or pods offered like I've seen happen on many other threads on the community forum. I'd like to request the area field manager reviews this case. I checked "issues in my area" page and it offered for me to book another appointment so another engineer is coming at 12-4pm on Friday 12th Sep 2025 but really what is the engineer going to do? Replace everything again? How many times will I need to go though this cycle before I can get a stable signal?I'm out of contract at this point I'm starting to wonder why I'm bothering, other than the sick curiosity of cracking the solution and potentially helping out some of my neighbours.Please have a look at the BQM and logs. The hub 5 came online at 10.30am today and the drop out was at 20:30

Status ____________________________________________Item Status CommentsAcquired Downstream Channel (Hz), 331000000, LockedRanged Upstream Channel (Hz), 36599988, LockedProvisioning State, OnlineDownstream ____________________________________________Downstream bonded channels _____________________________Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID1 331000000 3.7 40 256 qam 252 139000000 4.9 40 256 qam 13 147000000 4.8 40 256 qam 24 155000000 4.9 40 256 qam 35 163000000 4.8 40 256 qam 46 171000000 4.6 40 256 qam 57 179000000 4.3 40 256 qam 68 187000000 4.4 40 256 qam 79 195000000 4.3 40 256 qam 810 203000000 4.1 40 256 qam 911 227000000 4.3 40 256 qam 1212 235000000 4.1 40 256 qam 1313 259000000 3.9 40 256 qam 1614 267000000 4 40 256 qam 1715 291000000 3.7 40 256 qam 2016 299000000 4.4 40 256 qam 2117 323000000 3.5 40 256 qam 2418 355000000 3.4 40 256 qam 2819 363000000 3.2 40 256 qam 2920 379000000 3.7 40 256 qam 3121 387000000 3.4 40 256 qam 3222 395000000 2.9 40 256 qam 3323 403000000 2.5 40 256 qam 3424 411000000 2.7 40 256 qam 35Downstream bonded channels _____________________________Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors1 Locked 40.9 8 02 Locked 40.9 13 03 Locked 40.3 83 04 Locked 40.3 7 05 Locked 40.9 18 06 Locked 40.3 20 07 Locked 40.3 30 08 Locked 40.9 8 09 Locked 40.9 19 010 Locked 40.9 7 011 Locked 40.3 8 012 Locked 40.9 8 013 Locked 40.3 9 014 Locked 40.3 14 015 Locked 40.3 5 016 Locked 40.9 1 017 Locked 40.9 9 018 Locked 40.9 11 019 Locked 40.3 1 020 Locked 40.3 13 021 Locked 40.9 6 022 Locked 40.9 16 323 Locked 40.9 6 024 Locked 40.3 16 0Upstream ____________________________________________Upstream bonded channels ______________________________Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID1 36599988 47 5120 64 qam 32 23600019 47 5120 64 qam 53 30099993 47 5120 64 qam 44 43100024 47 5120 64 qam 25 49600039 47 5120 64 qam 1Upstream bonded channels _____________________________Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts1 ATDMA 0 0 0 02 ATDMA 0 0 0 03 ATDMA 0 0 0 04 ATDMA 0 0 0 05 ATDMA 0 0 0 0 General Configuration _____________________________Network access, AllowedMaximum Number of CPEs, 1Baseline Privacy, EnabledDOCSIS Mode, Docsis30Config file, gvca69834ncxv9873254k;fg8Primary Downstream Service Flow, SFID 822Max Traffic Rate 287500061Max Traffic Burst 42600Min Traffic Rate 0 Primary Upstream Service FlowSFID 821Max Traffic Rate 27500061Max Traffic Burst 42600Min Traffic Rate 0Max Concatenated Burst 42600Scheduling Type BestEffort

Also, just to add we recently had the hub 3.0 replaced (within the past year) due to this same issue

No Ranging Response received - T3 time-out | Virgin Media Community

Time	Priority	Description
26/08/2025 11:58:28	notice	LAN login Success; [REMOVED]
26/08/2025 09:09:14	Warning!	TCS Partial Service;[REMOVED]
26/08/2025 09:09:14	Warning!	Initializing Channel Timeout Expires - Time the CM can perform initial ranging on all upstream channels in the TCS has expired;[REMOVED]
25/08/2025 15:01:40	critical	No Ranging Response received - T3 time-out;[REMOVED]
25/08/2025 06:30:8	notice	DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;[REMOVED]
25/08/2025 06:30:8	Error	DHCP RENEW WARNING - Field invalid in response v4 option;[REMOVED]
22/08/2025 03:57:17	critical	No Ranging Response received - T3 time-out;[REMOVED]
21/08/2025 18:30:8	notice	DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;[REMOVED]
21/08/2025 18:30:8	Error	DHCP RENEW WARNING - Field invalid in response v4 option;[REMOVED]
18/08/2025 12:08:22	critical	No Ranging Response received - T3 time-out;[REMOVED]
18/08/2025 06:30:7	notice	DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;[REMOVED]
18/08/2025 06:30:7	Error	DHCP RENEW WARNING - Field invalid in response v4 option;[REMOVED]
15/08/2025 03:43:43	critical	No Ranging Response received - T3 time-out;[REMOVED]
14/08/2025 18:30:7	notice	DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;[REMOVED]
14/08/2025 18:30:7	Error	DHCP RENEW WARNING - Field invalid in response v4 option;[REMOVED]
11/08/2025 11:14:20	critical	No Ranging Response received - T3 time-out;[REMOVED]
11/08/2025 06:30:2	notice	DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;[REMOVED]
11/08/2025 06:30:2	Error	DHCP RENEW WARNING - Field invalid in response v4 option;[REMOVED]
10/08/2025 01:59:11	critical	No Ranging Response received - T3 time-out;[REMOVED]
07/08/2025 18:30:2	notice	DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;[REMOVED]

29 Replies

yorkieboy123

On our wavelength

5 days ago

Time	Priority	Description
10-09-2025 21:20:59	notice	GUI Login Status - Login Success from LAN interface
10-09-2025 21:02:18	warning	DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=[MAC-1];CMTS-MAC=[MAC-2];CM-QOS=1.1;CM-VER=3.1;
10-09-2025 21:02:18	notice	US profile assignment change. US Chan ID: 6; Previous Profile: 13; New Profile: 11 13.;CM-MAC=[MAC-1];CMTS-MAC=[MAC-2];CM-QOS=1.1;CM-VER=3.1;
10-09-2025 21:02:13	notice	REGISTRATION COMPLETE - Waiting for Operational status
10-09-2025 21:02:07	warning	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=[MAC-1];CMTS-MAC=[MAC-2];CM-QOS=1.1;CM-VER=3.1;
10-09-2025 21:02:07	warning	Dynamic Range Window violation
10-09-2025 21:02:07	warning	Dynamic Range Window violation
10-09-2025 21:02:07	warning	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=[MAC-1];CMTS-MAC=[MAC-2];CM-QOS=1.1;CM-VER=3.1;
10-09-2025 21:02:07	warning	RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=[MAC-1];CMTS-MAC=[MAC-2];CM-QOS=1.1;CM-VER=3.1;
10-09-2025 21:02:07	warning	Dynamic Range Window violation
10-09-2025 21:02:07	warning	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=[MAC-1];CMTS-MAC=[MAC-2];CM-QOS=1.1;CM-VER=3.1;
10-09-2025 21:02:07	warning	Dynamic Range Window violation
10-09-2025 21:02:06	warning	REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=[MAC-1];CMTS-MAC=[MAC-2];CM-QOS=1.1;CM-VER=3.1;
10-09-2025 21:02:00	notice	DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=[MAC-1];CMTS-MAC=[MAC-2];CM-QOS=1.1;CM-VER=3.1;
10-09-2025 21:01:59	notice	TLV-11 - unrecognized OID;CM-MAC=[MAC-1];CMTS-MAC=[MAC-2];CM-QOS=1.1;CM-VER=3.1;
10-09-2025 21:01:52	warning	DHCP WARNING - Non-critical field invalid in response ;CM-MAC=[MAC-1];CMTS-MAC=[MAC-2];CM-QOS=1.1;CM-VER=3.1;
10-09-2025 21:01:50	notice	Honoring MDD; IP provisioning mode = IPv4
10-09-2025 21:01:39	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[MAC-1];CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
10-09-2025 21:01:34	critical	DHCP FAILED - Discover sent, no offer received;CM-MAC=[MAC-1];CMTS-MAC=[MAC-2];CM-QOS=1.1;CM-VER=3.1;
10-09-2025 21:01:33	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[MAC-1];CMTS-MAC=[MAC-2];CM-QOS=1.1;CM-VER=3.1;
10-09-2025 20:58:27	critical	DHCP FAILED - Discover sent, no offer received;CM-MAC=[MAC-1];CMTS-MAC=[MAC-2];CM-QOS=1.1;CM-VER=3.1;
10-09-2025 20:58:24	notice	Honoring MDD; IP provisioning mode = IPv4
10-09-2025 20:58:04	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[MAC-1];CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
10-09-2025 20:57:59	warning	ToD request sent - No Response received;CM-MAC=[MAC-1];CMTS-MAC=[MAC-2];CM-QOS=1.1;CM-VER=3.1;
10-09-2025 20:57:54	notice	DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=[MAC-1];CMTS-MAC=[MAC-2];CM-QOS=1.1;CM-VER=3.1;
10-09-2025 20:57:52	notice	TLV-11 - unrecognized OID;CM-MAC=[MAC-1];CMTS-MAC=[MAC-2];CM-QOS=1.1;CM-VER=3.1;
10-09-2025 20:57:46	warning	DHCP WARNING - Non-critical field invalid in response ;CM-MAC=[MAC-1];CMTS-MAC=[MAC-2];CM-QOS=1.1;CM-VER=3.1;
10-09-2025 20:57:43	notice	Honoring MDD; IP provisioning mode = IPv4
10-09-2025 20:52:49	notice	GUI Login Status - Login Success from LAN interface
10-09-2025 20:52:30	notice	GUI Login Status - Login Fail from LAN interface
10-09-2025 20:52:17	notice	GUI Login Status - Login Success from LAN interface
10-09-2025 20:51:21	notice	GUI Login Status - Login Success from LAN interface
10-09-2025 20:50:59	notice	GUI Login Status - Login Fail from LAN interface
10-09-2025 20:49:57	notice	GUI Login Status - Login Success from LAN interface
10-09-2025 20:32:24	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[MAC-1];CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
10-09-2025 20:32:20	warning	ToD request sent - No Response received;CM-MAC=[MAC-1];CMTS-MAC=[MAC-2];CM-QOS=1.1;CM-VER=3.1;
10-09-2025 20:32:18	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[MAC-1];CMTS-MAC=[MAC-2];CM-QOS=1.1;CM-VER=3.1;
10-09-2025 20:31:59	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[MAC-1];CMTS-MAC=[MAC-2];CM-QOS=1.1;CM-VER=3.1;
10-09-2025 20:31:58	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[MAC-1];CMTS-MAC=[MAC-2];CM-QOS=1.1;CM-VER=3.1;
10-09-2025 20:31:39	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[MAC-1];CMTS-MAC=[MAC-2];CM-QOS=1.1;CM-VER=3.1;
10-09-2025 20:31:39	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[MAC-1];CMTS-MAC=[MAC-2];CM-QOS=1.1;CM-VER=3.1;
10-09-2025 20:31:19	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[MAC-1];CMTS-MAC=[MAC-2];CM-QOS=1.1;CM-VER=3.1;
10-09-2025 20:31:19	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[MAC-1];CMTS-MAC=[MAC-2];CM-QOS=1.1;CM-VER=3.1;
10-09-2025 20:30:59	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[MAC-1];CMTS-MAC=[MAC-2];CM-QOS=1.1;CM-VER=3.1;
10-09-2025 20:30:59	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[MAC-1];CMTS-MAC=[MAC-2];CM-QOS=1.1;CM-VER=3.1;
10-09-2025 20:30:39	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[MAC-1];CMTS-MAC=[MAC-2];CM-QOS=1.1;CM-VER=3.1;
10-09-2025 20:30:39	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[MAC-1];CMTS-MAC=[MAC-2];CM-QOS=1.1;CM-VER=3.1;
10-09-2025 20:29:46	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[MAC-1];CMTS-MAC=[MAC-2];CM-QOS=1.1;CM-VER=3.1;
10-09-2025 20:29:45	warning	MDD message timeout;CM-MAC=[MAC-1];CMTS-MAC=[MAC-2];CM-QOS=1.1;CM-VER=3.1;
10-09-2025 20:29:40	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[MAC-1];CMTS-MAC=[MAC-2];CM-QOS=1.1;CM-VER=3.1;
10-09-2025 20:29:39	warning	MDD message timeout;CM-MAC=[MAC-1];CMTS-MAC=[MAC-2];CM-QOS=1.1;CM-VER=3.1;
10-09-2025 20:29:38	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[MAC-1];CMTS-MAC=[MAC-2];CM-QOS=1.1;CM-VER=3.1;
10-09-2025 11:00:58	error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=[MAC-1];CMTS-MAC=[MAC-2];CM-QOS=1.1;CM-VER=3.1;
10-09-2025 10:31:25	notice	US profile assignment change. US Chan ID: 6; Previous Profile: 13; New Profile: 11 13.;CM-MAC=[MAC-1];CMTS-MAC=[MAC-2];CM-QOS=1.1;CM-VER=3.1;
10-09-2025 10:31:25	warning	DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=[MAC-1];CMTS-MAC=[MAC-2];CM-QOS=1.1;CM-VER=3.1;
10-09-2025 10:31:20	notice	REGISTRATION COMPLETE - Waiting for Operational status
10-09-2025 10:31:15	warning	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=[MAC-1];CMTS-MAC=[MAC-2];CM-QOS=1.1;CM-VER=3.1;
10-09-2025 10:31:15	warning	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=[MAC-1];CMTS-MAC=[MAC-2];CM-QOS=1.1;CM-VER=3.1;
10-09-2025 10:31:15	warning	Dynamic Range Window violation
10-09-2025 10:31:15	warning	Dynamic Range Window violation
10-09-2025 10:31:15	warning	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=[MAC-1];CMTS-MAC=[MAC-2];CM-QOS=1.1;CM-VER=3.1;
10-09-2025 10:31:15	warning	Dynamic Range Window violation
10-09-2025 10:31:15	warning	Dynamic Range Window violation
10-09-2025 10:31:14	warning	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=[MAC-1];CMTS-MAC=[MAC-2];CM-QOS=1.1;CM-VER=3.1;
10-09-2025 10:31:13	warning	RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=[MAC-1];CMTS-MAC=[MAC-2];CM-QOS=1.1;CM-VER=3.1;
10-09-2025 10:31:13	warning	Dynamic Range Window violation

yorkieboy123

On our wavelength

5 days ago

Cable Modem Status
Item	Status	Type
Cable Modem Status	Online	DOCSIS 3.0
Primary downstream channel	Locked	SC-QAM
Channel Overview	Downstream	Upstream
DOCSIS 3.0 channels	32	5
DOCSIS 3.1 channels	1	1

3.0 Downstream channels

Channel	Frequency (Hz)	Power (dBmV)	SNR (dB)	Modulation	Channel ID
1	331000000	7.6	42	QAM 256	25
2	139000000	7.3	41	QAM 256	1
3	147000000	7	41	QAM 256	2
4	155000000	6.8	41	QAM 256	3
5	163000000	6.9	41	QAM 256	4
6	171000000	6.9	41	QAM 256	5
7	179000000	6.7	41	QAM 256	6
8	187000000	6.7	41	QAM 256	7
9	195000000	7	41	QAM 256	8
10	203000000	7.2	41	QAM 256	9
11	211000000	7.6	41	QAM 256	10
12	219000000	7.8	41	QAM 256	11
13	227000000	7.6	41	QAM 256	12
14	235000000	7.5	41	QAM 256	13
15	243000000	7.7	41	QAM 256	14
16	251000000	7.5	42	QAM 256	15
17	259000000	7.5	42	QAM 256	16
18	267000000	7.4	41	QAM 256	17
19	275000000	7.4	41	QAM 256	18
20	283000000	7.5	41	QAM 256	19
21	291000000	7.7	42	QAM 256	20
22	299000000	7.9	42	QAM 256	21
23	307000000	7.9	42	QAM 256	22
24	315000000	7.7	42	QAM 256	23
25	323000000	7.7	42	QAM 256	24
26	339000000	7.4	42	QAM 256	26
27	347000000	7.4	42	QAM 256	27
28	355000000	7.5	42	QAM 256	28
29	363000000	7.5	42	QAM 256	29
30	371000000	7.4	41	QAM 256	30
31	379000000	7.1	42	QAM 256	31
32	387000000	7	41	QAM 256	32

3.0 Downstream channels

Channel	Locked Status	RxMER (dB)	Pre RS Errors	Post RS Errors
1	Locked	42	2	0
2	Locked	41	3	0
3	Locked	41	3	0
4	Locked	41	1	0
5	Locked	41	2	0
6	Locked	41	3	0
7	Locked	41	2	0
8	Locked	41	3	0
9	Locked	41	0	0
10	Locked	41	2	0
11	Locked	41	2	0
12	Locked	41	2	0
13	Locked	41	0	0
14	Locked	41	3	0
15	Locked	41	1	0
16	Locked	42	0	0
17	Locked	42	0	0
18	Locked	41	0	0
19	Locked	41	0	0
20	Locked	41	2	0
21	Locked	42	0	0
22	Locked	42	0	0
23	Locked	42	2	0
24	Locked	42	1	0
25	Locked	42	0	0
26	Locked	42	0	0
27	Locked	42	0	0
28	Locked	42	0	0
29	Locked	42	1	0
30	Locked	41	0	0
31	Locked	42	0	0
32	Locked	41	2	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	42	6.7	651080447	0

3.0 Upstream channels

Channel	Frequency (Hz)	Power (dBmV)	Symbol Rate (ksps)	Modulation	Channel ID
0	49600000	46.3	5120	QAM 64	1
1	43100000	45.5	5120	QAM 64	2
2	36600000	44.8	5120	QAM 64	3
3	30100000	44.3	5120	QAM 64	4
4	23600000	44.8	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	40.5	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

yorkieboy123
On our wavelength
5 days ago
Here's what i saw during the 2030 outage
- Vikki_M
  Forum Team
  3 days ago
  Hi yorkieboy123,
  
  Thanks for the update, we're sorry to hear you're still having some issues.
  
  Have you had any further engineer visits since posting?
  
  If so, what was the outcome?
  
  Please pop back to us when you can.