Is this Home Phone or Broadband

[#1]

I performed a quiet line test. I sat through several iterations; some were quiet, some had light 'snow', one had a couple of faint 'beeps'.

During the test the DSL connection dropped.

Before the quiet line test

18:45:03, 25 Jun.

DSL Link Up: Down Rate=3680kbps, Up Rate=658kbps; SNR Margin Down=6.4dB, Up=3.2dB

Now.

Data rate:336 Kbps / 3.403 Mbps

Maximum data rate:704 Kbps / 3.832 Mbps

Noise margin:10.5 / 6.4

Line attenuation:36.6 / 63.5

Signal attenuation:0.0 / 68.8

A short line from the HUB2 logfile (possibly of relevance)

22:45:33, 04 Jul. DSL Link Up: Down Rate=3488kbps, Up Rate=656kbps; SNR Margin Down=6.4dB, Up=6551.7dB

Up 6551.7dB?

I'm slightly confused.com on that bit.

[#2]

Of more relevance would be your WAN log file - what does it look like?

[#3]

A couple of [no-carrier] error-type messages.

Initial drop at the bottom (that's the way logfiles go).

23:13:28, 04 Jul. DSL Link Up: Down Rate=3403kbps, Up Rate=336kbps; SNR Margin Down=6.3dB, Up=2.7dB
23:13:28, 04 Jul. WAN DHCPv6 events: INIT
23:13:25, 04 Jul. WAN Sensing Auto sensing Complete, interface selected
23:13:25, 04 Jul. WAN Sensing Auto sensing Running
23:13:25, 04 Jul. Success - secondary DNS servers
23:13:25, 04 Jul. Success - primary DNS servers
23:13:25, 04 Jul. WAN connection WAN3_INTERNET_ATM_0_38 connected
23:13:19, 04 Jul. WAN Auto-sensing detected port DSL WAN
23:13:19, 04 Jul. WAN Auto-sensing detected port DSL WAN
23:11:08, 04 Jul. WAN Sensing Auto sensing Complete, interface selected
23:11:08, 04 Jul. WAN Sensing Auto sensing Running
23:11:08, 04 Jul. WAN connection WAN3_INTERNET_ATM_0_38 disconnected.[ERROR_NO_CARRIER]
23:11:06, 04 Jul. DSL Link Down: duration was 1540 seconds
22:45:35, 04 Jul. WAN Sensing Auto sensing Running
22:45:35, 04 Jul. Success - secondary DNS servers
22:45:35, 04 Jul. Success - primary DNS servers
22:45:35, 04 Jul. WAN connection WAN3_INTERNET_ATM_0_38 connected
22:45:34, 04 Jul. DSL Link Up: Down Rate=3488kbps, Up Rate=656kbps; SNR Margin Down=6.4dB, Up=6551.7dB
22:45:27, 04 Jul. WAN Auto-sensing detected port DSL WAN
22:45:26, 04 Jul. WAN Auto-sensing detected port DSL WAN
22:45:02, 04 Jul. WAN Sensing Auto sensing Complete, interface selected
22:45:01, 04 Jul. WAN Sensing Auto sensing Running
22:45:01, 04 Jul. WAN connection WAN3_INTERNET_ATM_0_38 disconnected.[ERROR_NO_CARRIER]
22:45:00, 04 Jul. DSL Link Down: duration was 792004 seconds

The SNR figures are/have subsequently changed, but upstream and downstream are still slower than what they were. A subsequent reboot of the hub brought

02:40:25, 05 Jul. DSL Link Up: Down Rate=3467kbps, Up Rate=602kbps; SNR Margin Down=6.1dB, Up=2.2dB

\n

SNR currently 8.5 / 6.0

\n

It's awkward when quibbling about k's  and m's rather than m's and m's. But that's what a significant minority of the UK population have. A significant minority that is swallowing an annual adjustement of CPI + 3.9% for no apparent benefit. I'm pretty much certain that FTTC/VDSL isn't going to be giving me any proportional bang per proverbial buck. (Possibly a very different topic - I know infrastructure investment money has to come from somewhere, but).

[#4]

I know that is the way logfiles go.

From that brief snippet, I would suspect you have a problem somewhere in the BT/OR network, so would suggest you raise a fault via the autobot: https://www.plus.net/help/report-a-problem/broadband/ . Has it continued in that fashion - that detail is a couple of days old?

[#5]

Line was stable, but with reduced up and down b/w

The up has now increased (after a couple of restarts of the hub, but leaving it up for a couple of days), but the down has decreased.

02:29:15, 09 Jul. DSL Link Up: Down Rate=3395kbps, Up Rate=742kbps; SNR Margin Down=6.1dB, Up=4.8dB

I'd still be interested in any possible explanation of the upstream SNR in this.

22:45:34, 04 Jul. DSL Link Up: Down Rate=3488kbps, Up Rate=656kbps; SNR Margin Down=6.4dB, Up=6551.7dB

[#6]

I recall someone querying this in the dim and distant past, but can't seem to find the thread, and can't remember the answer - sorry.

I would be rather more concerned about the DSL drops reported in the WAN logs.

[#7 · Accepted solution]

Nay problem. It's something I've never seen before so I was wondering if someone, somewhere had a vague idea (or even just a random thought).

The line is (obviously) copper, the path to the exchange is long. It's a bit Wimbledon Wombledon (undergound, overground, etc.). I suppose I could ask for/order a new (phone) line but I feel it may very well be provisioned over the same in-situ infrastructure and hence I'd be paying for zero benefit. I'm not holding my breath in the hope of fibre coming anywhere near.

So, I suppose this is gonna have to be a 'fixed' for some value of 'not resolved'