A rather sad ADSL2 connection...

[#1]

Your line is connected at around the speed I'd expect on the upstream, it the throughput that's the issue now/

Quote

Connection speed (kbps):  3318      972

One simple thing to try is a disconnect/reconnect from within the router pages. Can you give that a go.

[#2]

@Chris, as you say the modem upstream speed has gone up after the uncapping, but the throughput is still more less the same. I've disconnected from the router admin page, waited a minute, reconnected and then ran the BTW Speedtest. The upload is speed is still very low?
[tt]Download speed achieved during the test was - 2.85 Mbps
For your connection, the acceptable range of speeds is 1.2 Mbps-4 Mbps.
IP Profile for your line is - 2.93 Mbps
Upload speed achieved during the test was - 0.36Mbps
Additional Information:
Upstream Rate IP profile on your line is - 0.83 Mbps[/tt]

[#3]

The ping monitor looks a bit odd as it now features regular spikes.
My Broadband Ping
I believe the PlusNet connection speed looks at a different profile from the exchange, the two are quite different?
[tt]Phone exchange:THATCHAM
Estimated line speed:10Mb
(Download speed could vary depending on line conditions. Estimates are the maximum speeds that your phone line can support. These speeds are dependent on the package you choose.)  -
Checked on 2014-10-21 10:46:24
Current line speed:2.9 Mb [/tt]

[#4]

That 10Mbps estimate on a 53dB attenuated line is simply wrong. 3.5 to 4 would be more realistic.
Something does not add up here - are BT's database content correct?

[#5]

The date listed as the check date, was back in the days when it was a 61-63 db line. I guess that makes it an even wilder estimate and the reason for hoping that FTTC would be even better.
I re-ran the BTW speedtest as the Boost engineer is due this afternoon and the upload speed has now doubled 
[tt] Download speed achieved during the test was - 2.89 Mbps
For your connection, the acceptable range of speeds is 1.2 Mbps-4 Mbps.
IP Profile for your line is - 2.93 Mbps
Upload speed achieved during the test was - 0.79Mbps
Additional Information:
Upstream Rate IP profile on your line is - 0.83 Mbps[/tt]

[#6]

@Townman
Sorry 3.5 - 4 Mbps would not be realistic. Around 6.5Mbps would be more realistic as the line should be no longer than 3.5km according to the information in the CLT. Zixus would appear to be connected on sub-standard pairs both 'D' side and 'E' side (the latter being based on the previous engineers comments). The 'D' side conclusion came from the abysmal attempted Fibre connection.
I'm glad the Upload speed got resolved Zixus, I hope the boost engineer found you some better pairs and sorted any iffy joints.

[#7]

Hi Anotherone,
My suggestion was qualified in the context of the reported attenuation.  Based on other data a different estimate might be equally valid.  There is a lot of inconsistent data around this problem, however I think there is agreement that the reported estimation of 10Mbps is not realistic..
Kevin

[#8]

Your suggestion in the context of the reported attenuation by the modem/router implies that this is acceptable and the estimated speed for such is acceptable - none of which is acceptable.

[#9]

The Boost engineer arrived on Wednesday afternoon and spent a couple of hours in the study. I believe some form of RF filter was fitted in the white junction box (the one that joins the white twisted pair cable to the master socket and the black cable that wraps around the house to the BT66 junction box).
Unfortunately the engineers test equipment did not register any faults and only slight variations in downstream SNRM. When the Plusnet modem was hooked up to the master socket, DSLStats was reporting variations in SNRM and a fair few errors.
The engineer also informed me that his equipment was showing the line length at 4.1Km. I did try to point out that this would mean that either our house or the exchange might have to move to a different village for that to be likely.
The engineer also tested for REIN and did not find anything suspicious.
I then tried using RouterStats (I'm not to familiar with the set-up) and it also showed the variations in downstream SNRM. I can't get my head around how it plots errors.
The engineer did not inspect the poles in our garden or the BT66. I did ask if these should be checked, but as he could not see any errors, the engineer did not see the point.
I believe our line now has a target of 12db.
In summary, no improvement just greater ambiguity over the actual length of the cable that feeds our house.
[tt]Noise Margin:  10.2  dB
Bandwidth:    2994  kbps
Attenuation:  54.5  dB
Power:        0.0    dBm
Errors:
  FEC:  23792
  CRC:  422
  HEC:  1816
Failures since last reset:
  LOF:  5
  LOS:  45
  LPR:  0
  ES :  1287[/tt]
[tt]Noise Margin:  6.3    dB
Bandwidth:    964    kbps
Attenuation:  30.3  dB
Power:        12.7  dBm
Errors:
  FEC:  3590
  CRC:  440
  HEC:  N/A[/tt]

[#10]

The engineer was right about REIN......BUT only because it wasn't present when he was there
I'll have a look through these graphs  - I think I spotted something the other day that you might need to look at, but want to double check.

[#11]

.. and we're back.
It was a little windy recently and the voice service developed a crackling/buzzing sound.
Today the BT Engineer arrived (who was very pleasant) could hear the issue and set off to resolve it. Unfortunately, rather than fix the fault that exists between the telephone pole nearest our house and the main distribution point, we've been swapped on to a 'new line'.
The net effect is no broadband. It was briefly available at 1.5Mbs, but it was unusable and has now stopped connecting ("xDSL linestat down"). Note that we were connecting at 3.5Mbs before todays visit. We are also now back to the awful line attenuation that we had 7 months ago. It's 63db (as opposed to 53db before todays visit).
This is engineering visit number 6. I hope that everyone will agree that it is unacceptable to expect customers to take days off waiting on engineers, who then can't resolve the underlying issue .
Can someone please fix this line (properly)? This is seriously unimpressive.
Our exasperation is reaching the point where it feels that contacting the office of Gavin Patterson everyday until this is fixed is the only route left.
Fault no: 102011689

[#12]

Quite frankly I would do that anyway. It's clear that Openretch need to replace the sub-standard cables affecting your connection. This has gone on long enough and the cable performance is well below par.
Did the engineer not come back to you after he swapped the pair and check all was OK? Sloppy and very unprofessional.

[#13]

I'm sorry to hear what's happened.
I can see Tony was dealing with this for you last time around. I'll have a word with him and see what we can do.