Watching FTTC Broadband!

[#1]

Following a simple and easily fixed (NTE 5c customer plate) noise issue yesterday I do hope what happened to my old ADSL2+ connection is not starting to happen to my heretofore stable FTTC connection. I have always worried about this...

I noticed there was an overnight carrier drop last night, around 2.15am, and this morning my download speed has dropped a bit to ~35Mbps, from around the normal ~37Mbps - on a 10/40 connection. Otherwise no sign of a problem and line is completely silent on landline test.

[#2]

Turned the router off last night, on again later this morning. Much the same 35Mbps Download (though variable).

Still no sign of anything wrong my end. This is looking to be one of those 'Event' things. There is the BB speed before the 'Event', then there is an 'Event' (nobody ever to know what it is), then there is the speed after the 'Event' - which is always lower than the before speed.

Let's just hope there are no more 'Events'. 🙄

Sigh!

[#3]

The plot thickens...

Extended listening on Quiet Line Test reveals an intermittent, very irregular, very brief 'Tick!' sound on the line. What can possibly be causing this? Clearly, something has happened, somewhere on the circuit. Any ideas?

TIA

[#4]

@pvmb 

Yes - report a phone fault.

Brian

[#5]

@pvmb 

There is the BB speed before the 'Event', then there is an 'Event' (nobody ever to know what it is), then there is the speed after the 'Event' - which is always lower than the before speed.

If its a Hub two export the event log, attach it to a post and we can take a look or copy/paste an example text if it is not

The DLM is know to perform a connection resync around 02:00 in an attempt to ensure you have a stable line, occasionally over a succession of nights.

[#6]

Does this help?

02:55:26, 10 Jul. DSL Link Up: Down Rate=39999kbps, Up Rate=10000kbps; SNR Margin Down=14.3dB, Up=16.7dB
02:55:24, 10 Jul. PPP: Sending PADI
02:55:18, 10 Jul. PPP: Starting PPP daemon
02:55:18, 10 Jul. WAN Auto-sensing detected port DSL WAN
02:54:49, 10 Jul. SIP WAN DOWN
02:54:49, 10 Jul. WAN Sensing Auto sensing Complete, interface selected
02:54:48, 10 Jul. WAN Sensing Auto sensing Running
02:54:48, 10 Jul. WAN connection WAN2_INTERNET_PTM disconnected.[ERROR_NO_CARRIER]
02:54:47, 10 Jul. PPP: Stopped PPP daemon(0,1,5)
02:54:47, 10 Jul. PPP LCP Send Termination Request (User request)
02:54:47, 10 Jul. PPP: IPCP down
02:54:47, 10 Jul. PPP: LCP down
02:54:47, 10 Jul. DSL Link Down: duration was 43587 seconds


13:02:39, 09 Jul. DSL Link Up: Down Rate=40000kbps, Up Rate=9999kbps; SNR Margin Down=15.3dB, Up=14.3dB
13:02:37, 09 Jul. PPP: Sending PADI
13:02:32, 09 Jul. PPP: Starting PPP daemon
13:02:31, 09 Jul. WAN Auto-sensing detected port DSL WAN
13:01:41, 09 Jul. SIP WAN DOWN
13:01:40, 09 Jul. WAN Sensing Auto sensing Complete, interface selected
13:01:40, 09 Jul. WAN Sensing Auto sensing Running
13:01:40, 09 Jul. WAN connection WAN2_INTERNET_PTM disconnected.[ERROR_NO_CARRIER]
13:01:39, 09 Jul. PPP: Stopped PPP daemon(0,1,5)
13:01:39, 09 Jul. PPP LCP Send Termination Request (User request)
13:01:38, 09 Jul. PPP: IPCP down
13:01:38, 09 Jul. PPP: LCP down
13:01:38, 09 Jul. DSL Link Down: duration was 13362 seconds


09:19:05, 09 Jul. DSL Link Up: Down Rate=40000kbps, Up Rate=9999kbps; SNR Margin Down=15.2dB, Up=14.3dB
09:19:02, 09 Jul. PPP: Sending PADI
09:18:57, 09 Jul. PPP: Starting PPP daemon
09:18:57, 09 Jul. WAN Auto-sensing detected port DSL WAN
09:18:07, 09 Jul. SIP WAN DOWN
09:18:06, 09 Jul. WAN Sensing Auto sensing Complete, interface selected
09:18:06, 09 Jul. WAN Sensing Auto sensing Running
09:18:05, 09 Jul. WAN connection WAN2_INTERNET_PTM disconnected.[ERROR_NO_CARRIER]
09:18:04, 09 Jul. PPP: Stopped PPP daemon(0,1,5)
09:18:04, 09 Jul. PPP LCP Send Termination Request (User request)
09:18:04, 09 Jul. PPP: IPCP down
09:18:04, 09 Jul. PPP: LCP down
09:18:04, 09 Jul. DSL Link Down: duration was 4055 seconds


08:10:37, 09 Jul. DSL Link Up: Down Rate=40000kbps, Up Rate=9999kbps; SNR Margin Down=15.1dB, Up=14.4dB
08:10:35, 09 Jul. PPP: Sending PADI
08:10:30, 09 Jul. PPP: Starting PPP daemon
08:10:29, 09 Jul. WAN Auto-sensing detected port DSL WAN
08:09:39, 09 Jul. SIP WAN DOWN
08:09:39, 09 Jul. WAN Sensing Auto sensing Complete, interface selected
08:09:38, 09 Jul. WAN Sensing Auto sensing Running
08:09:38, 09 Jul. WAN connection WAN2_INTERNET_PTM disconnected.[ERROR_NO_CARRIER]
08:09:37, 09 Jul. PPP: Stopped PPP daemon(0,1,5)
08:09:37, 09 Jul. PPP LCP Send Termination Request (User request)
08:09:37, 09 Jul. PPP: IPCP down
08:09:37, 09 Jul. PPP: LCP down
08:09:37, 09 Jul. DSL Link Down: duration was 21585 seconds


02:10:00, 09 Jul. DSL Link Up: Down Rate=40000kbps, Up Rate=9999kbps; SNR Margin Down=15.2dB, Up=14.3dB
02:09:57, 09 Jul. PPP: Sending PADI
02:09:52, 09 Jul. PPP: Starting PPP daemon
02:09:52, 09 Jul. WAN Auto-sensing detected port DSL WAN
02:09:01, 09 Jul. SIP WAN DOWN
02:09:01, 09 Jul. WAN Sensing Auto sensing Complete, interface selected
02:09:00, 09 Jul. WAN Sensing Auto sensing Running
02:09:00, 09 Jul. WAN connection WAN2_INTERNET_PTM disconnected.[ERROR_NO_CARRIER]
02:08:59, 09 Jul. PPP: Stopped PPP daemon(0,1,5)
02:08:59, 09 Jul. PPP LCP Send Termination Request (User request)
02:08:59, 09 Jul. PPP: IPCP down
02:08:59, 09 Jul. PPP: LCP down
02:08:59, 09 Jul. DSL Link Down: duration was 5184 seconds


00:42:43, 09 Jul. DSL Link Up: Down Rate=40000kbps, Up Rate=9999kbps; SNR Margin Down=15.2dB, Up=22.3dB
00:42:41, 09 Jul. PPP: Sending PADI
00:42:36, 09 Jul. PPP: Starting PPP daemon
00:42:35, 09 Jul. WAN Auto-sensing detected port DSL WAN
00:41:44, 09 Jul. SIP WAN DOWN
00:41:43, 09 Jul. WAN Sensing Auto sensing Complete, interface selected
00:41:43, 09 Jul. WAN Sensing Auto sensing Running
00:41:43, 09 Jul. WAN connection WAN2_INTERNET_PTM disconnected.[ERROR_NO_CARRIER]
00:41:42, 09 Jul. PPP: Stopped PPP daemon(0,1,5)
00:41:42, 09 Jul. PPP LCP Send Termination Request (User request)
00:41:42, 09 Jul. PPP: IPCP down
00:41:42, 09 Jul. PPP: LCP down
00:41:41, 09 Jul. DSL Link Down: duration was 54315 seconds

[#7]

@pvmb Just an observation, but I think you might have a problem - your D/S SNR margin looks very high.

[#8]

---

@bmc wrote:

@pvmb 

Yes - report a phone fault.

Brian

---

I could try that. But, as a phone fault, this is so slight you wouldn't even notice it on a phone call. I missed it on an ordinary check of the Quiet Line Test and only noticed it on a much extended listen. I have now given it the full 'works', so reckon the clicks are definitely coming from the Openreach network side.

[#9]

---

@jab1 wrote:

@pvmb Just an observation, but I think you might have a problem - your D/S SNR margin looks very high.

---

But doesn't this just go with the 10/40 link, where the line is actually shown as having a higher rated maximum download speed (~71Mbps)? It has always been this high (possibly even a bit higher) with my FTTC and I thought it gave plenty of headroom. I have always considered it normal.

[#10]

Quite possibly, @pvmb  - as I said, it was just a thought. I'll leave it to the experts.

[#11]

One curiosity, possibly irrelevant - The Hub 2 always used to report sync speeds as Down 40Mbps, Up 9.999Mbps. But now it is showing:

Downstream sync speed: 39.999 Mbps

Upstream sync speed: 10 Mbps

😕

[#12]

@pvmb 

A quick look at the event show a 'normal' event story following a DSL link down. It's knowing the cause can be hard to find.

When did Openreach visit you? Is the event "02:54:47, 10 Jul. DSL Link Down: duration was 43587 seconds " the last one you have had, exclude any switching off the Hub.

Regarding

DSL Link Up: Down Rate=39999kbps, Up Rate=10000kbps; SNR Margin Down=14.3dB, Up=16.7dB

compared with 

DSL Link Up: Down Rate=40000kbps, Up Rate=9999kbps; SNR Margin Down=15.3dB, Up=14.3dB

SNR is not necessarily a constant figure and can vary through the day. 

[#13]

@Dan_the_Van

Not sure what you mean by "When did Openreach visit you?". Last visit was more than 18 months ago when I was still on ADSL2+ and still frustratingly trying to get it back to something near my previous 'maximum speed'. I could never find anything actually physically wrong, neither could they and they thought I was just being 'fussy' - but over the years it had ratcheted down on a number of occasions following mysterious 'Events' with no known cause. Looking now at the reported max ADSL2+ speed at the cabinet for my premises, it is shown as about half what it used to be when I gave up on it and changed over to FTTC!

Yes, the "02:54:47, 10 Jul. DSL Link Down: duration was 43587 seconds" event was the last spontaneous drop, apart from my turning the router off for testing purposes.

[#14]

Interesting. Checked up on the cabinet services for my premises and noticed that now all sections relating to ADSL Products, SOADSL Products and ADSL Multicast have been removed. So now no figures are shown for ADSL 2+ 'Downstream Line Rate'. ADSL figures now only exist under Observed Speeds section, with entries under headings VSDL & ADSL:

Max Observed Downstream Speed

Max Observed Upstream Speed

Observed Date

The numbers under ADSL are for my old operating figures from 12 Sept 2022., 14.33/0.89Mbps.

[#15]

@pvmb 

I miss interpreted your first post, thinking Openreach replaced the Master Socket 5c faceplate.

If you have had noise introduced by a poor faceplate then a period of monitoring would be the next step.

The 5c does have a problem with the faceplate becoming poorly seated and introducing noise, I have had this issue in the past myself occasionally, I have taken all the necessary steps to ensure the faceplate does not become unseated. 

I believe ADSL is no longer offered for new connections except for exceptional reasons or when the only service available. FTTC will only be offered as SoGEA (copper broadband with no landline phone)