Random WAN disconnects started 18th October and nearly daily since

[#1]

As of the 18th October I have been getting frequent WAN drops, anything from every other day to multiple times a day. Any idea of possible causes? Tried the text fault reporting, but of course by the time that runs the connection is back up.

The history of the drops from the router logs are:

12:58:31 01 Nov. DSL Link Down: duration was 4009 seconds

11:51:17 01 Nov. DSL Link Down: duration was 68472 seconds

16:49:39 31 Oct. DSL Link Down: duration was 276189 seconds

13:06:05 28 Oct. DSL Link Down: duration was 4167 seconds

11:56:13 28 Oct. DSL Link Down: duration was 66092 seconds

17:34:15 27 Oct. DSL Link Down: duration was 9705 seconds

14:52:05 27 Oct. DSL Link Down: duration was 15310 seconds

10:36:30 27 Oct. DSL Link Down: duration was 113160 seconds

03:10:05 26 Oct. DSL Link Down: duration was 66006 seconds

08:49:34 25 Oct. DSL Link Down: duration was 42811 seconds

20:55:38 24 Oct. DSL Link Down: duration was 35060 seconds

11:10:53 24 Oct. DSL Link Down: duration was 158890 seconds

15:02:18 22 Oct. DSL Link Down: duration was 4639 seconds

13:44:34 22 Oct. DSL Link Down: duration was 4466 seconds

12:29:43 22 Oct. DSL Link Down: duration was 79916 seconds

14:17:19 21 Oct. DSL Link Down: duration was 145 seconds

14:14:29 21 Oct. DSL Link Down: duration was 21 seconds

14:13:43 21 Oct. DSL Link Down: duration was 67853 seconds

19:22:25 20 Oct. DSL Link Down: duration was 58611 seconds

03:05:09 20 Oct. DSL Link Down: duration was 182016 seconds

00:25:38 18 Oct. DSL Link Down: duration was 2499774 seconds

02:02:19 19 Sep. DSL Link Down: duration was 1298563 seconds

01:19:10 04 Sep. DSL Link Down: duration was 5342822 seconds

04:10:06 05 May. DSL Link Down: duration was 526014 seconds

As you can see it has become more frequent since the 18th October. There have been no changes in the infrastructure or configuration during this period.

A more detailed WAN log for today is:

12:59:35 01 Nov. WAN Sensing Auto sensing Complete

12:59:34 01 Nov. WAN Sensing Auto sensing Running

12:59:34 01 Nov. Success - secondary DNS servers

12:59:34 01 Nov. Success - primary DNS servers

12:59:34 01 Nov. WAN connection WAN2_INTERNET_PTM connected

12:59:05 01 Nov. DSL Link Up: Down Rate=77314kbps

12:58:57 01 Nov. WAN Auto-sensing detected port DSL WAN

12:58:33 01 Nov. WAN Sensing Auto sensing Complete

12:58:33 01 Nov. WAN Sensing Auto sensing Running

12:58:33 01 Nov. WAN connection WAN2_INTERNET_PTM disconnected.[ERROR_NO_CARRIER]

12:58:31 01 Nov. DSL Link Down: duration was 4009 seconds

11:52:10 01 Nov. WAN Sensing Auto sensing Complete

11:52:10 01 Nov. WAN Sensing Auto sensing Running

11:52:10 01 Nov. Success - secondary DNS servers

11:52:10 01 Nov. Success - primary DNS servers

11:52:10 01 Nov. WAN connection WAN2_INTERNET_PTM connected

11:51:50 01 Nov. DSL Link Up: Down Rate=77073kbps

11:51:42 01 Nov. WAN Auto-sensing detected port DSL WAN

11:51:19 01 Nov. WAN Sensing Auto sensing Complete

11:51:18 01 Nov. WAN Sensing Auto sensing Running

11:51:18 01 Nov. WAN connection WAN2_INTERNET_PTM disconnected.[ERROR_NO_CARRIER]

11:51:17 01 Nov. DSL Link Down: duration was 68472 seconds

[#2 · Accepted solution]

@400ixl 

First thing to check: Is your phoneline clear? Dial 17070 (preferably from a corded phone), select option 2. Once your phone number is confirmed, there should be silence on the line except for the regular 'Quiet Line Test' message - any other noise, report a PHONE problem via: https://www.plus.net/help/report-a-problem/phone/

If the phone test passes, report a broadband problem via: https://www.plus.net/help/report-a-problem/broadband/

Let us know the result - if the tests come back as clear but you still have a problem, we need to investigate further.

The above assumes you still have 'normal' landline connection - if you have a SOGEA (internet only) one, just use the second link to report a network issue.

[#3]

Thanks jab1

Line test seemed clear.

I had tried the SMS test when it happened the other day but that came back as no problem. Tried it again today and it has come back with a fault and an engineer is being deployed tomorrow to look at it.

Thanks for your response, lets see where the engineer gets to tomorrow.