orange light and orange b intermittently

[#1]

i keep getting an orange light and orange b on my hub. it started about a month ago and is now happening 30+ times a day. it stops and starts at any time of day and night (whether anyone is online or not) and lasts between a couple of minutes to about 20. I've tried all the router help suggestions from plusnet but nothing works. any idea what's causing it and how to fix it? thanks

[#2]

A warm welcome to the community!

I assume your router is a Hub One.

The orange light with the “b” is signalling that there is a potential issue between the router and the DSLAM in the BT OR cabinet, or that the Hub One is malfunctioning. We need more information.

I suggest that you log into your router and got to:

 >Troubleshooting > Helpdesk, and copy and paste the following data

5. DSL uptime:
6. Data rate:
7. Maximum data rate:
8. Noise margin:
9. Line attenuation:
10. Signal attenuation:
11. Modulation:

> Troubleshooting > Event Log: Category = Boot

Copy and paste the latest four logged entries.

[#3]

Hi thank you,

5. DSL uptime:	0 days, 01:17:54
6. Data rate:	16229 / 39976
7. Maximum data rate:	34492 / 85854
8. Noise margin:	12.0 / 17.7
9. Line attenuation:	15.1 / 14.9
10. Signal attenuation:	15.2 / 14.9
23. Modulation:	G.993.2 Annex B

16:12:18, 02 Apr.	IN: BLOCK [16] Remote administration (ICMP type 8 code 0 128.9.63.139-​>146.199.153.171 on ppp3)
16:12:11, 02 Apr.	ath10: STA 6c:40:08:a1:fa:88 IEEE 802.11: WiFi registration failed
16:11:57, 02 Apr.	OUT: BLOCK [7] ICMP replay (ICMP type 3 code 1 192.168.1.64-​>17.253.37.210 on ppp3)
16:11:13, 02 Apr.	OUT: BLOCK [7] ICMP replay (ICMP type 3 code 1 192.168.1.64-​>17.248.144.175 on ppp3)

 hopes these are the right ones, 

[#4]

@pglm77

The data from >Troubleshooting > Helpdesk tells us that you have an excellent line, plenty of signal to nose margin, so it is unlikely that the DLSLAM’s DLM is causing the modem/router to attempt renegotiate the speed due to the presence of RFI, REIN or crosstalk affecting the line; orange indicators. 

The data from Troubleshooting > Event Log: Category = Boot, looks odd to me. Have you presented the log for Troubleshooting > Event Log: Category = WiFi?  My interpretation of it is that a device 192.168.1.64 is attempting and failing to connect to the router using WiFi.

Could you please look at Troubleshooting > Event Log: Category = Boot again?

From your opening message I assume that you have confirmed that the issue persists even when you connect the Hub One directly to the “Test Socket” which is accessed by removing the front off the BT Openreach Master socket?

Are you able to connect you device using wired Ethernet to a LAN port on the Hub One?