Connection keeps dropping

[#1]

So, according to that, the DSL had been up for four days? The other disconnections are on your internal network, which neither OR or PN have any control over.

[#2]

Not what I call a stable connection

17:42:21, 12 Oct. DSL Link Down: duration was 338725 seconds
19:34:44, 08 Oct. DSL Link Down: duration was 793792 seconds
15:03:26, 29 Sep. DSL Link Down: duration was 61591 seconds
21:55:27, 28 Sep. DSL Link Down: duration was 194383 seconds
15:54:17, 26 Sep. DSL Link Down: duration was 245981 seconds
19:31:37, 23 Sep. DSL Link Down: duration was 25 seconds
19:22:46, 23 Sep. DSL Link Down: duration was 4886 seconds
17:59:52, 23 Sep. DSL Link Down: duration was 139673 seconds
03:10:02, 22 Sep. DSL Link Down: duration was 98306 seconds
23:50:08, 20 Sep. DSL Link Down: duration was 2066 seconds
23:14:16, 20 Sep. DSL Link Down: duration was 171683 seconds
23:31:26, 18 Sep. DSL Link Down: duration was 201409 seconds
15:33:10, 16 Sep. DSL Link Down: duration was 67389 seconds
20:48:33, 15 Sep. DSL Link Down: duration was 1157 seconds
20:27:47, 15 Sep. DSL Link Down: duration was 90932 seconds
16:17:47, 09 Sep. DSL Link Down: duration was 821144 seconds
04:10:19, 31 Aug. DSL Link Down: duration was 92474 seconds
02:27:36, 30 Aug. DSL Link Down: duration was 123904 seconds
05:07:08, 28 Aug. DSL Link Down: duration was 149849 seconds
20:32:28, 25 Aug. DSL Link Down: duration was 13316 seconds

[#3]

@Dan_the_Van Thanks for the 'extraction', and I totally agree. There is something going off with the external connection.

[#4]

I do believe its the installation of the mastersocket extension causing it, but its been put under the carpet and floor boards, so the mastersocket would need to be replaced I am assuming if it is that

[#5]

Went down again at 1 am this morning, they told me not to call because ill be on a monitoring period and they'd call me

[#6]

@ghamilton123 Just reading back, and the comment about a 'DIY' move of the master socket makes me think that could be a contributory factor, but I'm not a telecoms engineer.

[#7]

@ghamilton123 wrote:

I do believe its the installation of the master socket extension causing it, but its been put under the carpet and floor boards, so the master socket would need to be replaced I am assuming if it is that

I will admit to being confused by this post, are you talking about an extension from the master socket or is the master socket (NTE - Network Terminating Equipment) where the copper phone line is terminated in your property) buried under the carpet and floorboards?

Not sure Openreach would be happy if someone had moved the master socket under the floor, but wouldn't care if it was an extension as they are only responsible for the connection up to the master socket.

Where faults of this nature occur it is recommended to connect the Hub to the test socket found behind the faceplate of the master socket. An in-line ADSL filter may be needed.

[#8]

Had my family member out and he cant seem to find where the connection actually comes into the flat, knocked the "extension" part out of it, but he believes the connection comes in from a flat a few doors down and comes into the property from under the floor, due to there being no holes apart coming into the property apart from a old sky dish, I am also using the test socket on the mastersocket. 

[#9]

that factors been knocked out, as we cant actually tell where the master socket comes in from

[#10]

Woke up to this:

Dear Mr , Openreach has advised that they have resolved the issue with the broadband If you have any further issues please get back in touch. Please do not hesitate to get back in touch online at Contact Us or by phone on 0330 123 9123 if we can be of further assistance. Kind regards,  [Email notification sent to: me@***.dev]

[#11]

Just got off the phone, plusnet nor openreach cant see any faults on the line, plusnet are now sending out a new router, its been down 2x in 24hrs, been told to test with the new router when it arrives and call back

[#12]

Interesting, @ghamilton123 , although I am sceptical that a new Hub will correct your DSL drops.

[#13]

Yes im sceptical of it too, if it was a hardware issue i'd assume that the router itself would power off but no, its been the DSL connection:

System uptime:

31 Days 19 Hrs 0 Mins

Network uptime:

0 Days 12 Hrs 21 Mins

[#14]

It isn't the Hub then - definitely a OR network issue, but it seems the BT Consumer/Plusnet way is to blame the hardware/customers environment until they are forced to act.

What does you Error Log look like?

[#15]

Same as before:

01:48:05, 16 Oct. DSL Link Up: Down Rate=79999kbps, Up Rate=20000kbps; SNR Margin Down=13.1dB, Up=8.9dB
01:48:03, 16 Oct. PPP: Sending PADI
01:47:58, 16 Oct. PPP: Starting PPP daemon
01:47:57, 16 Oct. WAN Auto-sensing detected port DSL WAN
01:47:06, 16 Oct. ARP [del] br0 192.168.1.146 5e:a9:10:94:82:bd
01:46:16, 16 Oct. DHCP device Disconnected: 192.168.1.146, 5e:a9:10:94:82:bd, unknown
01:46:16, 16 Oct. LAN [DEL] ARP 192.168.1.146 with 5e:a9:10:94:82:bd from br0
01:46:09, 16 Oct. admin timeout from 192.168.1.146
01:46:02, 16 Oct. SIP WAN DOWN
01:46:02, 16 Oct. WAN Sensing Auto sensing Complete, interface selected
01:46:01, 16 Oct. WAN Sensing Auto sensing Running
01:46:01, 16 Oct. WAN connection WAN2_INTERNET_PTM disconnected.[ERROR_NO_CARRIER]
01:46:00, 16 Oct. PPP: Stopped PPP daemon(0,1,5)
01:46:00, 16 Oct. PPP LCP Send Termination Request (User request)
01:46:00, 16 Oct. PPP: IPCP down
01:46:00, 16 Oct. PPP: LCP down
01:46:00, 16 Oct. DSL Link Down: duration was 87411 seconds
01:32:23, 16 Oct. NTP synchronization success
01:32:23, 16 Oct. NTP Server: ntp.plus.net
01:32:10, 16 Oct. NTP synchronization start