My main question, how do I encourage my broadband to return to normal download speeds (it is now 50 or so times slower) following a period of trouble culminating in complete phone line failure? The ADSL has now been on uninterrupted for four (and a half) days and I'd like to speed up return to normality. Upload is better than download. Would switching the Hub on and off again now help, or just delay the restoration of line profile?
Background below, data details after:
Normally I was getting 13+ Mbps download, up until a few weeks ago. It slowly got worse. Last night I did the BT speedtest, following all the instructions except I did not first switch the HomeHub4 off and then on again. Download is 0.25 Mbps, and upload 0.44 Mbps.
I reported a broadband fault 8th March and it was apparently fixed 14th March, though there was no change. Then the phone line went completely dead on the 15th, although the broadband still staggered on. There must have been some more fundamental problem. This new fault was fixed at 10am on the 17th March, Thursday.
An engineer came in to the house, tested the line internally, and fixed something in the manhole in the pavement down the road. He also put on a new OpenReach front plate and also disconnected the unused extension wiring. (I have both the fault ref numbers if that helps). There was a previous complete phone-line failure back in November 2015 as well, by the way. Other than that, I can't think of another phone fault in ten years or more.
Since fixing on Thursday 17th at 10am or so - nearly the full week now - the ADSL line has been (almost entirely) stable, and it has been uninterrupted solid for the last four days. It was a bit glitchy for a bit after fixing, then stabilised. 24 hours after the fix I restarted the HomeHub (as recommended by the online chat helpdesk). Then the line was stable for a few hours, until Saturday 19th evening, when it disconnected and restarted several times over about four hours. But since 18:31 Saturday it has been solid.
I also tried the Quiet Line test, on a corded phone... it doesn't sound completely silent. There's a low continuous and fairly quiet hiss, but no crackling.
Some specific data below:
DSL noise margin: 9.10 dB upstream, 19.80 dB downstream
DSL line rate: 552 Kbps upstream, 287 Kbps downstream
4. Board version: BT Hub 4A
5. ADSL uptime: 4 days, 13:04:02
6. Bandwidth: 552 / 287
1. Best Effort Test: -provides background information.
Download speed achieved during the test was - 0.25 Mbps
For your connection, the acceptable range of speeds is 0.1 Mbps-0.25 Mbps.
IP Profile for your line is - 0.25 Mbps
2. Upstream Test: -provides background information.
Upload speed achieved during the test was - 0.44Mbps
Upstream Rate IP profile on your line is - 0.83 Mbps
BT Broadband Availability Checker http://dslchecker.bt.com
Home Hub Events
(ADSL connection been continuous since this last late flurry of disconnections, which were the entire set of uncommanded disconnections since I deliberately switched the Hub off and on again at 10am or so on Friday. Before that on-and-off, the line had been stable for another 15 hours or so, I think)
18:31:10, 19 Mar. (116182.290000) DSL is up
18:31:09, 19 Mar. (116181.270000) DSL noise margin: 9.10 dB upstream, 19.80 dB downstream
18:31:08, 19 Mar. (116180.360000) DSL line rate: 552 Kbps upstream, 287 Kbps downstream
18:30:21, 19 Mar. (116133.050000) DSL is down after 45 minutes uptime
17:18:39, 19 Mar. (111831.300000) DSL is up
17:18:38, 19 Mar. (111830.290000) DSL noise margin: 10.70 dB upstream, 26.20 dB downstream
17:18:37, 19 Mar. (111829.170000) DSL line rate: 888 Kbps upstream, 287 Kbps downstream
17:17:49, 19 Mar. (111780.720000) DSL is down after 2 minutes uptime
17:44:50, 19 Mar. (113402.080000) DSL is up
17:44:49, 19 Mar. (113401.050000) DSL noise margin: 8.90 dB upstream, 19.60 dB downstream
17:44:48, 19 Mar. (113400.140000) DSL line rate: 664 Kbps upstream, 287 Kbps downstream
17:44:00, 19 Mar. (113352.110000) DSL is down after 25 minutes uptime
17:15:32, 19 Mar. (111644.000000) DSL is up
17:15:31, 19 Mar. (111642.990000) DSL noise margin: 8.90 dB upstream, 25.40 dB downstream
17:15:30, 19 Mar. (111642.080000) DSL line rate: 832 Kbps upstream, 287 Kbps downstream
17:14:26, 19 Mar. (111577.730000) DSL is down after 70 minutes uptime
16:04:06, 19 Mar. (107358.540000) DSL is up
16:04:05, 19 Mar. (107357.530000) DSL noise margin: 8.90 dB upstream, 25.50 dB downstream
16:04:04, 19 Mar. (107356.520000) DSL line rate: 851 Kbps upstream, 287 Kbps downstream
16:02:51, 19 Mar. (107283.100000) DSL is down after 72 minutes uptime
14:49:54, 19 Mar. (102906.540000) DSL is up
14:49:53, 19 Mar. (102905.510000) DSL noise margin: 8.90 dB upstream, 23.20 dB downstream
14:49:53, 19 Mar. (102904.580000) DSL line rate: 696 Kbps upstream, 287 Kbps downstream
14:49:05, 19 Mar. (102856.580000) DSL is down after 0 minutes uptime
14:48:35, 19 Mar. (102827.190000) DSL is up
14:48:34, 19 Mar. (102826.170000) DSL noise margin: 8.90 dB upstream, 23.70 dB downstream
14:48:33, 19 Mar. (102825.260000) DSL line rate: 728 Kbps upstream, 287 Kbps downstream
14:47:44, 19 Mar. (102776.090000) DSL is down after 43 minutes uptime
14:04:31, 19 Mar. (100182.970000) DSL is up
14:04:30, 19 Mar. (100181.960000) DSL noise margin: 8.90 dB upstream, 24.10 dB downstream
14:04:29, 19 Mar. (100181.030000) DSL line rate: 776 Kbps upstream, 287 Kbps downstream
14:04:03, 19 Mar. (100154.910000) DSL is down after 0 minutes uptime
14:04:01, 19 Mar. (100152.670000) DSL is up
14:04:00, 19 Mar. (100151.670000) DSL noise margin: 0.00 dB upstream, 0.00 dB downstream
14:03:58, 19 Mar. (100150.250000) DSL line rate: 819 Kbps upstream, 287 Kbps downstream
14:02:33, 19 Mar. (100064.610000) DSL is down after 1665 minutes uptime
this explains about banded profile now need stable conmnection 24/7 and normality will return possibly in stages
I see that Plusnet site says "Once the problem is fixed, your sync speed should return to normal quickly" but I guess what "quickly" means is arguable. I suppose I was hoping that there was someone somewhere who could make a physical intervention - given there was an actual phone line repair - or there was something I could do, rather than simply wait for the DLM system to play out over 10 days.
Well, five days down, five to go I guess. I did read somewhere that 3-5 days might also be enough for movement, but no change so far and I'm at nearly five days.
As a point of interest, does it make any difference to DLM whether the broadband is used extensively (within the limits of the speed; the iPlayer doesn't work for instance) for down and up loading, or if everyone in the house was on holiday and no-one used it at all?
usage makes no difference to DLM most important is a stable connection 24/7 - no resets/drops in connection
From my website archive for future reference.
Changes in your connection speed are automatically managed by the exchange equipment, using a process called
Dynamic Line Management (DLM).
Its purpose it to give you the best speed possible, without introducing a lot of errors back into the BT network.
These errors impact on other users, and can slow their connection down, as your data packets have to keep being resent.
This is a continous process, but certain things can cause it to make drastic changes to your connection speed.
These can include the following:-
You could have also been recently moved from ADSL max to ADSL2+, this would mean that the line
would have to re-train again, and must be left undisturbed for at least 10 days.
If you keep restarting or disconnecting your BT Home hub, then the exchange equipment will see this as a fault condition, and reduce your connection speed, in an attempt to stabilise your line.
You have recently had a fault on your line which has just been fixed.
Sometimes a single interruption to your line can cause this too, especially if it generates a large error burst.
The effect is that you get placed in a low banded speed profile, and you will notice that your downstream margin is high, usually over 15dB.
The lower the banded speed profile, the quicker it will recover, but it could take up to a month before the fullspeed is recovered.
If you want your speed to recover, then these are the steps you need to take.
DO NOT restart or disconnect the power to your BT Home Hub.
DO NOT disconnect your BT Home hub from your phone line.
Leave everything alone for at least 10 days, so that the exchange can record a stable connection.
During this time, the exchange may drop the connection, and re-establish a faster connection.
If you use the BT Speedtester, then do not restart the BT Home Hub, even if it tells you to.
If after 10 days your speed does not increase, then please return to your forum post.
showing that you have 10 days of connection time, then the problem can be escalated.
You can calculate your final speed by using this website.
Maximum speed calculator
A similar process is applied to the connection between the Infinity cabinet, and the Openreach modem.
You cannot view that connection information, but the same thing applies, do not restart or disconnect the Openreach modem.
The BT home hub only acts as a router, and restarting it will not affect your physical connection speed to the cabinet.
BT broadband is line adaptive, if you have a good line, you get good broadband , BUT consider this, you only get good broadband
from the outset, if you let the exchange "train" the connection, when it is new, simply because it has to try various methods of modulation.
And once it is running at full speed and set the MSR (maximum stable rate) provided you don't keep disconnecting the router, it will stay that way.
So two important things: ALWAYS leave the router on, 24/7 and DO NOT impede the training process which can take up to 10 days.
The reasons are vaguely the same for both scenarios: DLM trains the connection during setup, and DLM runs the connection in a similar but different mode once it's running.
And the most common issue apart from line faults in causing poor broadband is FREQUENT RESETS and DISCONNECTIONS of the router or hub, because if you interupt line management it will demote the line profile if done to excess, with often time consuming efforts and long waits to get it back.
BT don't punish users indiscriminently by making them wait for their broadband speed to come up, but the line management is in place to DEFEND the network against bad and corrupted data, and if the exchange sees your line being reset too often it assumes a fault,
whereby your linespeed is demoted, and often profoundly so.
Also, because the exchange can't tell the difference between you messing around resetting all the time, and a real line fault, it assumes (using logic) the worst and demotes the line profile.
If you get a real line fault and the noise margin increases, the linespeed will decrease, it's normal, again it's a defence to help give you a service allbeit a depleted one, and at the same time stop corrupted data getting back to the exchanges.
But unfortunatlely it's at this point when people in general start to become frustrated, and guess what?
They then start to reset the router in an attempt to "repair" the connection. And in doing so, impede the line management from promoting the linespeed again. (providing any fault is or was fixed).
And to summarise, if the connection is left to run unimpeded, no excess resetting, and left to its own devices, it actually benefits from the good line
history that the exchange has accumulated for your connection, simply because the attention span by the line management is not so profound when it does bite the dust, for whatever reason.
So regardless of the opinions of some, switching off broadband routers is NOT a good idea, not if you want consistent broadband and a good line rate.
I was away from home the last few days, but the speed has now recovered... up to about 9.8Mbps from around 0.25, after 7.8 days if I read the log correctly, and all in one go, not a steady recovery. Not quite 13Mbps, which I had before, but maybe that will come in time. Cheers all! N
Your noise margin is more than likely still not down to the normal 6db so it will take at least one more DLM reset to get back to speed you previously received