Gig1 uncorrectable errors on 3.1 channel

[Jamied281]

Morning all,

I hope your all well. I’m having issues with my Gig1 service. I get occasional buffering whilst on video calls, YouTube etc. As you can see from my Hub4 stats, I’m getting uncorrectable errors on the 3.1 down channel.

My set up is as follows:

Hub 4 in Modem mode, Asus AX88u providing Wi-Fi. 

I’ve reset everything, checked cables, nothing seems obviously out.

Thanks in advance, James.  

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

1	362250000	2.799999	37.355988	QAM256	1
2	370250000	2.400002	36.609653	QAM256	2
3	378250000	1.599998	36.609653	QAM256	3
4	386250000	2.200001	37.355988	QAM256	4
5	394250000	2.500000	37.355988	QAM256	5
6	402250000	1.700001	37.355988	QAM256	6
7	410250000	1.799999	37.355988	QAM256	7
8	418250000	2.400002	37.636276	QAM256	8
9	426250000	2.299999	37.355988	QAM256	9
10	434250000	2.500000	37.355988	QAM256	10
11	442250000	3.299999	37.355988	QAM256	11
12	450250000	3.700001	37.636276	QAM256	12
13	458250000	1.799999	37.636276	QAM256	13
14	466250000	2.400002	37.636276	QAM256	14
15	474250000	2.599998	37.636276	QAM256	15
16	482250000	1.700001	37.355988	QAM256	16
17	490250000	1.099998	37.355988	QAM256	17
18	498250000	2.299999	37.355988	QAM256	18
19	506250000	2.099998	37.636276	QAM256	19
20	514250000	1.299999	37.636276	QAM256	20
21	522250000	1.599998	37.636276	QAM256	21
22	530250000	2.599998	37.355988	QAM256	22
23	538250000	1.599998	37.355988	QAM256	23
24	546250000	1.000000	37.636276	QAM256	24
25	554250000	1.599998	37.355988	QAM256	25
26	562250000	1.900002	37.636276	QAM256	26
27	570250000	1.099998	37.636276	QAM256	27
28	578250000	1.299999	37.355988	QAM256	28
29	586250000	1.700001	37.636276	QAM256	29
30	594250000	1.200001	37.355988	QAM256	30
31	602250000	0.500000	37.636276	QAM256	31

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

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

3.1 Downstream channels

Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)

48

96

4K

1880

QAM4096

759

3.1 Downstream channels

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

48

Locked

39

0.4

370975663

3

[gitty]

The current numbers don't look scary. Check the log when you get uncorrectables. The interesting part is which modulation profiles are getting hit. If it is only the 4096-QAM profile, you may never notice anything, even it the number gets big.

[Jamied281]

Gitty,

thanks for the reply. I do switch to the log once buffering occurs, however the uncorrectables only raise by 1 or 2, if they even raise.

Cheers

James

[Adduxi]

3 uncorrectable errors is nothing to worry about.  When it climbs to 1000's then worry.  

You need to setup a BQM to monitor and record the state of your circuit.   Once running for 24 hours, please post a link to the shared graph and we can comment.

[Serena_C]

Hi @Jamied281

Welcome back to our Community Help Forum 🙂

Thank you for making this post regarding the issues you are experiencing with your Gig1 service, I'm sorry to hear you are experiencing buffering on calls and when watching YouTube. That is not ideal 😞

I have taken a look at our systems and there are currently no issues showing with your connection. Please set up a Broadband Quality Monitor here and share the graph results in this thread so we can see the issues when they occur.

Many thanks,

Serena