Is my Line Going through DLM?

[#1]

Apologies for not getting back sooner I was bogged down with other IT matters! @jab1 see below results of the test. My speeds appear to be random using the BT test, anything from 0.36mbps to 22 mbps. I can't seem to use the diagnostic part of the test, it says...

"Summary Advanced Test

Your speed test has completed and the results are shown above, however during the test an error occurred while trying to retrieve additional details regarding your service. As a result we are unable to determine if the speed you received during the test is acceptable for your service. Please re-run the test if you require this additional information."

I only know my telephone number though.

[#2]

@AWB70 Can't remember if I asked - are you on Unlimited Fibre or 'Unlimited Fibre Extra'? Either way, you are under the handback threshold, so my suggestion is to report a Broadband fault via  https://www.plus.net/help/report-a-problem/broadband/ and let us know the result. If they say there is no issue, they are not telling the truth.

The advanced diagnostic on the BTw site appears to be broken - again - as you are the second or third person to have reported this today. No matter, the screenshot above tells us all we need to know.

[#3]

Thanks John, I'm on unlimited fibre, are you saying there is information in that screenshot that suggests there is a fault, if so what in particular?

[#4]

OK, so the 40/10 product then. Given that, with the line/signal attenuation figures on your Help desk pages, I would have expected something closer to the low to mid 30Mb/s range for download and maybe a bit more than you are seeing for upload,

Your wildly fluctuating speeds, and the very low uptime in your Help Desk shot, strongly suggest you are having constant xDSL drops. At one time, the Help Team would post the RADIUS logs to confirm/disprove this, but they seem strangely reluctant to do this these days.

[#5]

Thanks @jab1 I'll look into it. To be fair the internet in my home is mainly used (by me anyway) for streaming tv these days which I guess may not be affected by "dropouts" as I guess it would be buffered a bit up in advance? i know my daughter was doing some  complaining when she was doing teams stuff for her college work but I assumed it was something on the other end as it wasn't really affecting me, perhaps she was right all along!

[#6]

One more thing before I suggest you report a fault - if you haven't already done so - can you post the current WAN tab from your Event log? That should confirm or otherwise that this is indeed xDSL drops.

[#7]

Hey @jab1 not sure what happened here! I was wondering why I didn't get a response. I thought I'd posted this last week, must have typed it up and didn't hit post.

00:03:01, 16 Apr. WAN Sensing Auto sensing Complete, interface selected
00:03:01, 16 Apr. WAN Sensing Auto sensing Running
00:03:01, 16 Apr. Success - secondary DNS servers
00:03:01, 16 Apr. Success - primary DNS servers
00:03:01, 16 Apr. WAN connection WAN2_INTERNET_PTM connected
00:02:57, 16 Apr. DSL Link Up: Down Rate=24991kbps, Up Rate=6204kbps; SNR Margin Down=6.3dB, Up=6.1dB
00:02:49, 16 Apr. WAN Auto-sensing detected port DSL WAN
00:02:07, 16 Apr. WAN Auto-sensing last connection port: DSL WAN
13:32:01, 12 Apr. WAN Sensing Auto sensing Complete, interface selected
13:32:01, 12 Apr. WAN Sensing Auto sensing Running
13:32:01, 12 Apr. Success - secondary DNS servers
13:32:01, 12 Apr. Success - primary DNS servers
13:32:01, 12 Apr. WAN connection WAN2_INTERNET_PTM connected
13:32:00, 12 Apr. DSL Link Up: Down Rate=24630kbps, Up Rate=6208kbps; SNR Margin Down=6.3dB, Up=6.1dB
13:31:50, 12 Apr. WAN Auto-sensing detected port DSL WAN
13:31:04, 12 Apr. WAN Auto-sensing last connection port: DSL WAN
02:02:01, 11 Apr. WAN Sensing Auto sensing Complete, interface selected
02:02:00, 11 Apr. WAN Sensing Auto sensing Running
02:02:00, 11 Apr. Success - secondary DNS servers
02:02:00, 11 Apr. Success - primary DNS servers
02:02:00, 11 Apr. WAN connection WAN2_INTERNET_PTM connected
02:01:56, 11 Apr. DSL Link Up: Down Rate=25095kbps, Up Rate=6179kbps; SNR Margin Down=6.2dB, Up=6.2dB
02:01:49, 11 Apr. WAN Auto-sensing detected port DSL WAN
02:01:07, 11 Apr. WAN Auto-sensing last connection port: DSL WAN
13:05:25, 10 Apr. WAN Sensing Auto sensing Complete, interface selected
13:05:22, 10 Apr. WAN Sensing Auto sensing Running
13:05:22, 10 Apr. Success - secondary DNS servers
13:05:22, 10 Apr. Success - primary DNS servers
13:05:22, 10 Apr. WAN connection WAN2_INTERNET_PTM connected
13:05:12, 10 Apr. WAN Auto-sensing detected port DSL WAN
13:05:11, 10 Apr. WAN Auto-sensing detected port DSL WAN
13:05:11, 10 Apr. WAN Sensing Auto sensing Complete, interface selected
13:05:10, 10 Apr. WAN Sensing Auto sensing Running
13:05:10, 10 Apr. WAN connection WAN2_INTERNET_PTM disconnected.[ERROR_NO_CARRIER]
13:05:09, 10 Apr. WAN Auto-sensing detected port Ethernet WAN
13:03:56, 10 Apr. WAN Sensing Auto sensing Complete, interface selected
13:03:53, 10 Apr. DSL Link Up: Down Rate=25147kbps, Up Rate=6530kbps; SNR Margin Down=6.3dB, Up=6.0dB
13:03:51, 10 Apr. WAN Sensing Auto sensing Running
13:03:51, 10 Apr. Success - secondary DNS servers
13:03:51, 10 Apr. Success - primary DNS servers
13:03:51, 10 Apr. WAN connection WAN2_INTERNET_PTM connected
13:03:45, 10 Apr. WAN Auto-sensing detected port DSL WAN

---

---

[#8]

Let me know if a more up to date one would give more insight.

[#9]

No problem, @AWB70 , it happens. 😉

I'm a little confused though - you had one DSL down event at 13.05 on 10/5 with ERR_NO_CARRIER , but then no corresponding DSL UP message, although you must have reconnected, and then three reconnection's, with no DSL down message.

If I am totally honest, I really don't know what is going on here, just hope @Anonymous  or @RealAleMadrid  - or anyone else who spots this - can shed some light.

Hows it been behaving since?

EDIT: yes please to a more up-to-date one - you posted while I was deciphering it and typing my reply.

[#10]

To be fair mate. like I mentioned earlier, I don't do much internet wise in the house other than stream TV. Although that's changing as I'm doing a bit more working from home. Only thing I've noticed was youtube buffering last night. I've done a few speed tests and they seem to be up and down.

Here's a more up yo date wan report, take into account there was a power cut last weekend on Saturday and Sunday night probably around eight coming back on around eleven,

02:43:25, 18 Apr. DSL Link Up: Down Rate=25800kbps, Up Rate=6211kbps; SNR Margin Down=6.3dB, Up=6.1dB
02:43:25, 18 Apr. WAN Sensing Auto sensing Complete, interface selected
02:43:25, 18 Apr. WAN Sensing Auto sensing Running
02:43:25, 18 Apr. Success - secondary DNS servers
02:43:25, 18 Apr. Success - primary DNS servers
02:43:25, 18 Apr. WAN connection WAN2_INTERNET_PTM connected
02:43:17, 18 Apr. WAN Auto-sensing detected port DSL WAN
02:42:49, 18 Apr. WAN Sensing Auto sensing Complete, interface selected
02:42:49, 18 Apr. WAN Sensing Auto sensing Running
02:42:49, 18 Apr. WAN connection WAN2_INTERNET_PTM disconnected.[ERROR_NO_CARRIER]
02:42:47, 18 Apr. DSL Link Down: duration was 98754 seconds
23:17:05, 16 Apr. WAN Sensing Auto sensing Complete, interface selected
23:17:04, 16 Apr. WAN Sensing Auto sensing Running
23:17:04, 16 Apr. Success - secondary DNS servers
23:17:04, 16 Apr. Success - primary DNS servers
23:17:04, 16 Apr. WAN connection WAN2_INTERNET_PTM connected
23:17:01, 16 Apr. DSL Link Up: Down Rate=25017kbps, Up Rate=6155kbps; SNR Margin Down=6.3dB, Up=6.1dB
23:16:53, 16 Apr. WAN Auto-sensing detected port DSL WAN
23:16:11, 16 Apr. WAN Auto-sensing last connection port: DSL WAN
00:03:00, 16 Apr. WAN Sensing Auto sensing Complete, interface selected
00:03:00, 16 Apr. WAN Sensing Auto sensing Running
00:03:00, 16 Apr. Success - secondary DNS servers
00:03:00, 16 Apr. Success - primary DNS servers
00:03:00, 16 Apr. WAN connection WAN2_INTERNET_PTM connected
00:02:56, 16 Apr. DSL Link Up: Down Rate=24991kbps, Up Rate=6204kbps; SNR Margin Down=6.3dB, Up=6.1dB
00:02:48, 16 Apr. WAN Auto-sensing detected port DSL WAN
00:02:06, 16 Apr. WAN Auto-sensing last connection port: DSL WAN
13:32:01, 12 Apr. WAN Sensing Auto sensing Complete, interface selected
13:32:01, 12 Apr. WAN Sensing Auto sensing Running
13:32:01, 12 Apr. Success - secondary DNS servers
13:32:01, 12 Apr. Success - primary DNS servers
13:32:01, 12 Apr. WAN connection WAN2_INTERNET_PTM connected
13:32:00, 12 Apr. DSL Link Up: Down Rate=24630kbps, Up Rate=6208kbps; SNR Margin Down=6.3dB, Up=6.1dB
13:31:50, 12 Apr. WAN Auto-sensing detected port DSL WAN
13:31:04, 12 Apr. WAN Auto-sensing last connection port: DSL WAN
02:02:01, 11 Apr. WAN Sensing Auto sensing Complete, interface selected
02:02:00, 11 Apr. WAN Sensing Auto sensing Running
02:02:00, 11 Apr. Success - secondary DNS servers
02:02:00, 11 Apr. Success - primary DNS servers
02:02:00, 11 Apr. WAN connection WAN2_INTERNET_PTM connected
02:01:56, 11 Apr. DSL Link Up: Down Rate=25095kbps, Up Rate=6179kbps; SNR Margin Down=6.2dB, Up=6.2dB
02:01:49, 11 Apr. WAN Auto-sensing detected port DSL WAN
02:01:07, 11 Apr. WAN Auto-sensing last connection port: DSL WAN
13:05:25, 10 Apr. WAN Sensing Auto sensing Complete, interface selected
13:05:22, 10 Apr. WAN Sensing Auto sensing Running
13:05:22, 10 Apr. Success - secondary DNS servers
13:05:22, 10 Apr. Success - primary DNS servers
13:05:22, 10 Apr. WAN connection WAN2_INTERNET_PTM connected
13:05:12, 10 Apr. WAN Auto-sensing detected port DSL WAN
13:05:11, 10 Apr. WAN Auto-sensing detected port DSL WAN
13:05:11, 10 Apr. WAN Sensing Auto sensing Complete, interface selected
13:05:10, 10 Apr. WAN Sensing Auto sensing Running
13:05:10, 10 Apr. WAN connection WAN2_INTERNET_PTM disconnected.[ERROR_NO_CARRIER]
13:05:09, 10 Apr. WAN Auto-sensing detected port Ethernet WAN
13:03:56, 10 Apr. WAN Sensing Auto sensing Complete, interface selected
13:03:53, 10 Apr. DSL Link Up: Down Rate=25147kbps, Up Rate=6530kbps; SNR Margin Down=6.3dB, Up=6.0dB
13:03:51, 10 Apr. WAN Sensing Auto sensing Running
13:03:51, 10 Apr. Success - secondary DNS servers
13:03:51, 10 Apr. Success - primary DNS servers
13:03:51, 10 Apr. WAN connection WAN2_INTERNET_PTM connected
13:03:45, 10 Apr. WAN Auto-sensing detected port DSL WAN

[#11]

Thanks for that. Do you mind if I reply tomorrow - I'm in the middle of setting another machine up for a family member and having to keep my eye on that a bit?

[#12]

@AWB70 strange you should mention YouTube - I've seen that a couple of times on other topics, but I suspect that is possibly a YT problem, nothing to do with your issue.

As to your problem, you only seem to have had one event - at 02.42 on the 18th, again including the ERROR_NO_CARRIER message, and then you have reconnected at your usual (but still low  d/l speeds).

As I've said, I can't understand it, my only thought is still a BT/OR network issue.

[#13]

@AWB70 

The WAN event log is not giving the full story of what is happening, so event log ALL exported from the Hub would be useful. It is exported as a CSV file.

Does the firmware version show v0.08.00.08297-PN now?

@jab1 

 ERROR_NO_CARRIER would follow a DSL Link Down, if you you're only seeing DSL Link Up then is likely the Hub has been switched off/on or had power restored, you will see message "WAN Auto-sensing detected port DSL WAN" during startup.

[#14]

Thanks @Dan_the_Van - that makes sense now. Never used a PN Hub, so I'm still learning. Agree we need the full event log.