Increasing occurrence of Broadband connection drop-outs

[#1]

Cheers for that Bill, glad it's better for now at least. 

Enjoy your holidays and let us know how things look with that when you get back. 

[#2]

Back from holiday, and the broadband speed (and connection reliability) seems as bad as ever.  I'll attach a picture of latest speed test result (11.46 Mb/s down, 2.01 up).

I think the earlier, decent, results need to be regarded as the anomaly, and BT check the line and connectivity, and advise on when proper fibre connection is planned.

[#3]

@billswan That appears to  be showing a definite problem. Which Hub/router do you have, and has it been switched off whilst you were away?

[#4]

Here's what it says

Plusnet Hub One | Software version 4.7.5.1.83.8.289.1.3 | Last updated 07/12/21

It wasn't switched off whilst I was away (but the PC was)

[#5]

Thanks for that. I asked for your Hub version as it tells me what I can expect if I ask you to post up your event log, which will be interesting if you can do that.

Can you also connect your router to the test  socket (behind the faceplate of your master socket) via a filter, and report the results of a speed test from: https://www.speedtest.net/ , please?

[#6]

My router is already connected direct (via filter) to the master BT socket, and my PC is connected via Ethernet to it.

Here's the (addresses redacted) Event log P/O

Also attached is a new speed test - which seems to confirm my diagnosis that it's an intermittent problem.

[#7]

Thanks. The Event Log I was actually after was the one accessed from the page in the screen shot below, especially the WAN category -accessible from the 'category' drop-down. Please don't obscure any IPs, though.

[#8]

It seems to go on forever, and makes no sense to me.

Copy of "first page" attached.  Any help?

It seems to be running OK at the moment, but the problem is intermittent.

[#9]

@willcutforth  / @ClaudiaG23  / @adamwalker  - the latest Error log (in the previous  post) seems to indicate there is still a problem. I know PN seem reluctant to post them them these days, but a Radius Log would be useful?

[#10]

@billswan 

Your attached WAN log has caused a stir, I note the top entry (last) time and date is 23:12:57  01 Oct, is the Hub One showing the correct time and date or is it wrong? At the time of posting my Hub One the top entry for the event log category ALL shows

07:42:16, 11 Nov. (63964.110000) Admin login successful by 192.168.1.64 on HTTP

If it does not check category NTP, hopefully you'll see daily events such as

13:58:47, 10 Nov. (155.460000) NTP synchronization success!
13:58:43, 10 Nov. (151.370000) NTP synchronization start

If incorrect a Hub restart should resolve the issue, do not switch off use the top button or GUI

The Helpdesk page would be help to see DSL uptime

[#11]

The hub one WAS showing the correct date, but I've rebooted it anyway.

All OK at the moment.  I guess I'll just wait 'til it goes winky-wanky-woo again?

In the meantime, thank you for the help.

[#12]

I'm thinking that the screen capture of the logfile is showing the event log after a (cold) reboot of the router before it gets a time from its configured time server and is showing a startup default time.

I have seen very similar in the Hub2. You just have to get logged into the router asap after a reboot.

The hubs don't have the capabilities to retain/store a "time-of-day". PC's have a little battery which keeps that data 'alive' Networking gear generally doesn't.

[#13]

Unfortunately you have made an incorrect assumption.

For the Hub One each event log entry is prefixed with time, date and system up time hh:mm:ss  dd mmm. (system uptime in seconds)

23:12:47 01 Oct (1565806, 710000) which equates to 18.12277 days.

You are correct the time needed to resync on cold/warm boot the NTP log confirms this.

HTH

[#14]

Obviously I've never encountered the Hub 1

[#15]

Interesting update

I noticed an OpenReach engineer in the lane outside our house a week ago and chatted to him.   He told me that they were looking at installing fibre, but that there was a known 'blockage' in the existing copper run!  He explained the topography.  It's a little complicated, as the cables come from the local "box" under a public, then a private road to a telegraph pole, from which it is distributed to houses (including mine).  The 'blockage' is believed to be at the foot of the telegraph pole, and just outside the gates of the big house which the private road leads to.  OpenReach have told the owner of the big house that they plan to hand-dig at the telegraph pole during the next two weeks (he won't let them dig up his road, nor use mechanical equipment!).

As an eternal optimist I hope they find and fix the problem, and that fibre will swiftly follow.  It does feel like this is what the true problem has been all along, but let's see.

I am surprised that Plusnet were apparently not aware of this engineering problem and planned works.