High Post RS errors, no ranging response

[smllmn]

After persistent issues over the last 5 days with connecting to telegram and gmail (the former will hang on "connecting" for 15-30 seconds at a time before establishing a connection, the latter simply will not load the modern client), I've been digging into the hub data and I'm a little disconcerted by what I see.

Full logs are below, but I'm seeing quite a lot of post RS errors and a few upstream sync issues. I've also observed spikes of seriously high upload latency - spikes as high as multiple seconds with median latency in the low hundreds of milliseconds.

Downstream bonded channels

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

1	203000000	10.9	40	256 qam	9
2	139000000	11.9	40	256 qam	1
3	147000000	11.8	40	256 qam	2
4	155000000	11.5	40	256 qam	3
5	163000000	11.5	40	256 qam	4
6	171000000	11.4	40	256 qam	5
7	179000000	11.4	40	256 qam	6
8	187000000	11.1	40	256 qam	7
9	195000000	11	40	256 qam	8
10	211000000	10.8	40	256 qam	10
11	219000000	10.5	40	256 qam	11
12	227000000	10.4	40	256 qam	12
13	235000000	10.3	40	256 qam	13
14	243000000	9.9	40	256 qam	14
15	251000000	9.8	40	256 qam	15
16	259000000	9.5	40	256 qam	16
17	267000000	9.5	40	256 qam	17
18	275000000	9.5	40	256 qam	18
19	283000000	9.9	40	256 qam	19
20	291000000	9.9	40	256 qam	20
21	299000000	10.1	40	256 qam	21
22	307000000	10.1	40	256 qam	22
23	315000000	10	40	256 qam	23
24	323000000	10	40	256 qam	24

Downstream bonded channels

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

1	Locked	40.9	280	105
2	Locked	40.3	316	179
3	Locked	40.3	326	160
4	Locked	40.3	283	190
5	Locked	40.3	317	229
6	Locked	40.3	304	116
7	Locked	40.3	332	146
8	Locked	40.3	289	207
9	Locked	40.3	284	136
10	Locked	40.3	318	115
11	Locked	40.9	254	174
12	Locked	40.9	254	124
13	Locked	40.3	299	84
14	Locked	40.3	256	89
15	Locked	40.3	286	70
16	Locked	40.3	265	78
17	Locked	40.3	268	68
18	Locked	40.9	270	107
19	Locked	40.3	288	89
20	Locked	40.3	253	54
21	Locked	40.3	272	79
22	Locked	40.3	249	48
23	Locked	40.3	272	48
24	Locked	40.3	276	73

Upstream bonded channels

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

1	49600000	34.3	5120	64 qam	1
2	23599897	33.3	5120	64 qam	5
3	43100000	34	5120	64 qam	2
4	30100000	33.8	5120	64 qam	4
5	36600039	34	5120	64 qam	3

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1	ATDMA	0	0	1	0
2	ATDMA	0	0	0	0
3	ATDMA	0	0	1	0
4	ATDMA	0	0	0	0
5	ATDMA	0	0	0	0

Network Log

Time Priority Description

05/09/2022 04:00:19	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/09/2022 17:20:48	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/09/2022 13:04:59	Warning!	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/09/2022 13:04:55	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/09/2022 13:04:55	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/09/2022 13:04:55	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/09/2022 13:04:54	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/09/2022 00:21:35	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/09/2022 14:02:39	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/09/2022 09:08:30	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/09/2022 08:56:33	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.0;
02/09/2022 08:54:9	Warning!	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/09/2022 08:54:6	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/09/2022 08:54:5	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/09/2022 08:54:5	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/09/2022 08:54:5	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:41	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

(notices omitted for brevity)

Any ideas on what the issue might be, or if this is an upstream issue that needs referring to VM, would be greatly appreciated.

[Akua_A]

Hi @smllmn,

Welcome to our community forums and thank you for your first posts.

Sorry to hear you have been having issues with your service. We can understand the frustration caused and we want to best help. I have had a look into your service and I can see there may bee an issue with your power levels. For this reason, I am sending you a private message. Please look out for the purple envelope and provide a response when you can.

Thanks,