Internet grinds to a halt during the day - large number RS errors

[lakeland]

I have a hub 3 and in the past few months, the internet frequently grinds to a halt during the day. I've looked at the logs, and there are high Pre and Post RS errors. I have switched off the router to clear the errors, checked and changed the cable, and changed the channel from auto, but the errors have resurfaced. The network log also lists errors, any ideas?

Logs below:

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

1	267000000	2.9	38	256 qam	17
2	275000000	3	38	256 qam	18
3	283000000	3.2	38	256 qam	19
4	291000000	3.5	38	256 qam	20
5	299000000	3.7	38	256 qam	21
6	307000000	3.7	38	256 qam	22
7	315000000	3.7	38	256 qam	23
8	323000000	3.7	38	256 qam	24
9	331000000	3.7	38	256 qam	25
10	339000000	3.7	38	256 qam	26
11	347000000	3.7	38	256 qam	27
12	355000000	3.5	38	256 qam	28
13	363000000	3.7	38	256 qam	29
14	371000000	3.4	38	256 qam	30
15	379000000	3.2	38	256 qam	31
16	387000000	2.7	38	256 qam	32
17	395000000	2.5	38	256 qam	33
18	403000000	2.2	38	256 qam	34
19	411000000	2.4	38	256 qam	35
20	419000000	2	38	256 qam	36
21	523000000	1.7	38	256 qam	37
22	531000000	1.7	38	256 qam	38
23	539000000	1.4	38	256 qam	39
24	547000000	1.7	38	256 qam	40

Downstream bonded channels

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

1	Locked	38.6	6103	29372
2	Locked	38.6	5882	28746
3	Locked	38.9	6887	26860
4	Locked	38.6	10108	22585
5	Locked	38.9	12039	19624
6	Locked	38.9	17120	13776
7	Locked	38.6	19928	10383
8	Locked	38.9	21590	9071
9	Locked	38.6	21831	8239
10	Locked	38.9	21947	7394
11	Locked	38.6	20830	7828
12	Locked	38.6	19614	8410
13	Locked	38.6	17856	8503
14	Locked	38.9	17994	8577
15	Locked	38.6	17651	7446
16	Locked	38.9	16744	7319
17	Locked	38.9	15496	7436
18	Locked	38.9	13588	9366
19	Locked	38.6	13500	296325
20	Locked	38.9	12102	7787
21	Locked	38.6	3513	9541
22	Locked	38.9	1670	9757
23	Locked	38.6	1966	9767
24	Locked	38.6	1344	9701

Time Priority Description

15/07/2024 11:41:8	notice	LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/07/2024 04:05:19	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/07/2024 20:41:12	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/07/2024 04:04:59	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/07/2024 15:49:20	Warning!	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/07/2024 15:49:16	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/07/2024 15:49:16	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/07/2024 15:49:15	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/07/2024 15:49:15	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/07/2024 12:09:57	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/07/2024 11:10:38	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/07/2024 04:49:36	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/07/2024 04:38:26	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/07/2024 12:09:57	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:45	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/07/2024 04:04:11	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/07/2024 17:55:10	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/07/2024 12:10:19	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/07/2024 12:05:25	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/07/2024 12:09:57	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

[lakeland]

BQM link: 

https://www.thinkbroadband.com/broadband/monitoring/quality/share/562aea8a06bb611c341bbf7974b52ddfa73893d3

[Adduxi]

Reboot the Hub and monitor the PostRS errors, they should remain at zero on an ideal circuit.  If they build up quickly there is a fault on the line.  This will need a technician to fix. 

In the meantime, check all the connections are at least "finger tight" and not loose, as loose connections can cause noise ingress.

[lakeland]

Reset once again. Also noticed the box on the outside of the house was slightly open as the cable tie had snapped. A huge spider had made a lovely nest in there so brushed it all out and tightened the connections. The main cable coming in was kinked, so unkinked that. No Post RS errors but pre-RS are present but in small numbers:

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

1	Locked	38.6	42	0
2	Locked	38.9	10	0
3	Locked	38.9	11	0
4	Locked	38.9	11	0
5	Locked	38.9	24	0
6	Locked	38.9	29	0
7	Locked	38.9	24	0
8	Locked	38.6	23	0
9	Locked	38.9	26	0
10	Locked	38.9	25	0
11	Locked	38.9	18	0
12	Locked	38.6	26	0
13	Locked	38.9	20	0
14	Locked	38.6	14	0
15	Locked	38.9	13	0
16	Locked	38.9	37	0
17	Locked	38.6	67	0
18	Locked	38.9	75	0
19	Locked	38.9	48	0
20	Locked	38.9	39	0
21	Locked	38.9	38	0
22	Locked	38.9	45	0
23	Locked	38.9	50	0
24	Locked	38.9	60	0

[Adduxi]

PreRS errors are nothing to worry about as they are corrected.  It's the PostRS errors you need to worry about.

[Beth_G]

Hi lakeland

Thanks for your post, welcome to the Community Forums.

Sorry to hear you've been experiencing a few issues with your broadband performance recently. I've had a look on this end and whilst I can see there's been a few disconnections over the past week, the connection looks quite stable. No known outages or anything affecting your connection. How've things been over the weekend after resetting?

[lakeland]

Thanks for the replies everyone. I've left it for several days now and since cleaning up the box on the outside of the house, no more post RS errors and the internet hasn't dropped. Thanks for checking at your end Beth.

[Vikki_M]

Hi lakeland

Thanks for your reply, we're really happy to hear things have improved :).

If you have any further questions, please pop back to us and we'd be happy to help.