Intermittent drop outs and high packet loss

[tigger2014]

Ive had on going issues for months, A number of things have been done by networks to resolve the issue but it appears to be ongoing.

I  think levels look ok to me?

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

1	163000000	2.2	38	256 qam	4
2	139000000	3.2	38	256 qam	1
3	147000000	3.2	38	256 qam	2
4	155000000	2.5	38	256 qam	3
5	171000000	2	38	256 qam	5
6	179000000	1.7	38	256 qam	6
7	187000000	1.7	38	256 qam	7
8	195000000	1.4	40	256 qam	8
9	203000000	1	38	256 qam	9
10	211000000	0.9	38	256 qam	10
11	219000000	0.7	40	256 qam	11
12	227000000	0.5	38	256 qam	12
13	235000000	0.2	38	256 qam	13
14	243000000	-0.5	38	256 qam	14
15	251000000	-1	38	256 qam	15
16	259000000	-0.7	38	256 qam	16
17	267000000	0	38	256 qam	17
18	275000000	0.5	40	256 qam	18
19	283000000	0.7	40	256 qam	19
20	291000000	0.5	40	256 qam	20
21	299000000	0.5	40	256 qam	21
22	307000000	0.5	40	256 qam	22
23	315000000	0.2	40	256 qam	23
24	323000000	0.2	40	256 qam	24

Downstream bonded channels

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

1	Locked	38.9	360	0
2	Locked	38.9	466	0
3	Locked	38.9	416	0
4	Locked	38.6	382	0
5	Locked	38.9	325	0
6	Locked	38.9	246	0
7	Locked	38.9	220	0
8	Locked	40.9	216	0
9	Locked	38.6	193	0
10	Locked	38.6	162	0
11	Locked	40.3	162	0
12	Locked	38.9	134	0
13	Locked	38.6	118	0
14	Locked	38.6	110	0
15	Locked	38.9	108	0
16	Locked	38.9	96	0
17	Locked	38.6	89	0
18	Locked	40.3	65	0
19	Locked	40.9	63	0
20	Locked	40.3	48	0
21	Locked	40.3	70	0
22	Locked	40.3	60	0
23	Locked	40.9	79	0
24	Locked	40.3	62	0

Upstream bonded channels

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

1	46200000	39.5	5120	64 qam	3
2	39400000	38.5	5120	64 qam	4
3	53700000	41	5120	64 qam	2
4	60300000	41.5	5120	64 qam	1

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1	ATDMA	0	0	1	0
2	ATDMA	0	0	2	0
3	ATDMA	0	0	8	0
4	ATDMA	0	0	10	0

[tigger2014]

Network Log

Time Priority Description

04/06/2022 09:32:12	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/06/2022 09:32:12	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/06/2022 09:28:51	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/06/2022 09:28:51	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/06/2022 09:28:31	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/06/2022 09:28:31	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/06/2022 09:28:12	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/06/2022 09:28:11	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/06/2022 09:27:32	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/06/2022 09:27:31	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/06/2022 09:26:52	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/06/2022 09:26:51	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/06/2022 09:26:12	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/06/2022 09:26:12	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/06/2022 09:21:32	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/06/2022 09:21:32	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/06/2022 09:20:52	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/06/2022 09:20:52	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/06/2022 04:28:0	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/06/2022 04:28:0	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

Local Packet loss graph

BQMs

1st June

2nd June

3rd June

4th June

SamKnows

Live graph 

BQM Live 

[tigger2014]

Ive also just seen the status page a planned maintenance work, Can anyone shed anymore light on this, Is it related to the issues im facing?

[Alex_RM]

Hi tigger2014,

This would certainly explain the issues you're experiencing with the service.

Please let us know how the connection is after the fix date/ time has passed.

Alex_Rm

[tigger2014]

And as per every other issue, Its still a poor service.

No issues showing up on the status page but that's not unusual for me having issues.

Local packet loss

5th

6th ( a good day)

7th

8th

9th

10th

Samknows

[tigger2014]

Downstream bonded channels

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

1	267000000	-0.2	38	256 qam	17
2	139000000	2.9	38	256 qam	1
3	147000000	2.7	38	256 qam	2
4	155000000	2.2	38	256 qam	3
5	163000000	1.7	38	256 qam	4
6	171000000	1.5	38	256 qam	5
7	179000000	1.2	38	256 qam	6
8	187000000	1.2	38	256 qam	7
9	195000000	0.9	38	256 qam	8
10	203000000	0.5	38	256 qam	9
11	211000000	0.5	38	256 qam	10
12	219000000	0.4	38	256 qam	11
13	227000000	0	38	256 qam	12
14	235000000	-0.2	38	256 qam	13
15	243000000	-1	38	256 qam	14
16	251000000	-1.5	38	256 qam	15
17	259000000	-1	38	256 qam	16
18	275000000	0	40	256 qam	18
19	283000000	0.2	40	256 qam	19
20	291000000	0	38	256 qam	20
21	299000000	0	40	256 qam	21
22	307000000	0	40	256 qam	22
23	315000000	-0.2	40	256 qam	23
24	323000000	-0.4	40	256 qam	24

Downstream bonded channels

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

1	Locked	38.9	15	0
2	Locked	38.9	26	0
3	Locked	38.9	31	0
4	Locked	38.6	20	0
5	Locked	38.6	26	0
6	Locked	38.9	27	0
7	Locked	38.9	15	0
8	Locked	38.9	10	0
9	Locked	38.9	16	0
10	Locked	38.6	15	0
11	Locked	38.9	11	0
12	Locked	38.9	13	0
13	Locked	38.9	19	0
14	Locked	38.6	23	0
15	Locked	38.9	16	0
16	Locked	38.6	20	0
17	Locked	38.6	25	0
18	Locked	40.3	13	0
19	Locked	40.9	9	0
20	Locked	38.9	10	0
21	Locked	40.3	28	0
22	Locked	40.3	25	0
23	Locked	40.3	31	0
24	Locked	40.3	32	0

Upstream bonded channels

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

1	25800000	37.8	5120	64 qam	6
2	32600000	38.3	5120	64 qam	5
3	39400000	38.8	5120	64 qam	4
4	46200000	40	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	8	0
3	ATDMA	0	0	6	0
4	ATDMA	0	0	7	0

[tigger2014]

Network Log

Time Priority Description

10/06/2022 08:12:11	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/06/2022 08:12:11	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/06/2022 08:11:51	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/06/2022 08:11:51	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/06/2022 00:32:35	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/06/2022 00:32:35	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/06/2022 00:32:15	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/06/2022 00:32:14	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/06/2022 00:31:15	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/06/2022 00:31:14	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/06/2022 00:30:55	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/06/2022 00:30:54	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/06/2022 00:29:55	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/06/2022 00:29:55	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/06/2022 00:29:35	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/06/2022 00:29:35	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/06/2022 00:28:55	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/06/2022 00:28:55	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/06/2022 00:28:35	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/06/2022 00:28:35	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

[David_Bn]

Good Afternoon @tiggr2014, thanks for coming back to the thread.

I've looked into the local area and can see the outage is currently ongoing and is due to run until 09:00, 13/06/22.

Do please come back to us beyond this time frame, if the service issues are still ongoing, and we'll be happy to look into this, or advise you if the outage is still ongoing.

Kindest regards,

David_Bn 

[tigger2014]

Hello,

Still got issues, is the fault still open? has a new fault been opened?

Is there any sign of this ever actually getting fixed?

[Paulina_Z]

Hi @tigger2014,

Thank you for coming back to us about your ongoing intermittent broadband connection. 

I have been able to take a look at our systems and I can see that there is still an active local SNR (Signal to Noise Ratio) outage in your area. I do apologise about this. The Fault Number is F009882895 and the current estimated fix time is showing as 21/06/22 at 9am.

I do apologise that this issue is still impacting you. You can read more about our Automatic Compensation Scheme on our website if needed.

Please keep us updated on how you're getting on past the 21st.

Thank you.