ERROR_NO_CARRIER Faults

[#1]

I am experiencing outages around 3-4 times/week lasting around 60 seconds each due to ERROR_NO_CARRIER faults. The logs look like the below (see attached). The issue resolves itself, but its incredibly frustrating when working as video calls drop, VPNs have to reset, etc. Any suggestions on resolution steps for this issue?:

11:35:57, 22 Aug. DSL Link Up: Down Rate=79999kbps, Up Rate=16995kbps; SNR Margin Down=12.4dB, Up=11.5dB
11:35:56, 22 Aug. WAN Sensing Auto sensing Complete, interface selected
11:35:56, 22 Aug. WAN Sensing Auto sensing Running
11:35:56, 22 Aug. Success - secondary DNS servers
11:35:56, 22 Aug. Success - primary DNS servers
11:35:56, 22 Aug. WAN connection WAN2_INTERNET_PTM connected
11:35:49, 22 Aug. WAN Auto-sensing detected port DSL WAN
11:32:16, 22 Aug. WAN Sensing Auto sensing Complete, interface selected
11:32:15, 22 Aug. WAN Sensing Auto sensing Running
11:32:15, 22 Aug. WAN connection WAN2_INTERNET_PTM disconnected.[ERROR_NO_CARRIER]
11:32:14, 22 Aug. DSL Link Down: duration was 10416 seconds
08:38:46, 22 Aug. DSL Link Up: Down Rate=79999kbps, Up Rate=16995kbps; SNR Margin Down=12.3dB, Up=11.7dB

[#2]

@wsomm4864 Report the fault via: https://www.plus.net/help/report-a-problem/

If the bot says there is 'no fault', come back and let us know, because there is one.

[#3]

@wsomm4864 

Actually the DSL link down messages is the cause of that error.

11:32:14, 22 Aug. DSL Link Down: duration was 10416 second

Error No Carrier is a symptom

As advised raise a fault.

[#4]

There is a fault, @Dan_the_Van , which is why I advised raising the report. Whether the 'error no carrier is symptom or not is, IMO, irrelevant.

[#5]

@jab1 

I was adding some background to the issue, also to follow the advice given by you.

No criticism of you 🙄

[#6]

Fair enough, @Dan_the_Van