I have a problem where I lost speed due to DLM intervention (understandable); while my sync speed recovered after de-intervention, the throughput speeds have never recovered back to their previous values.
As far as I can make out, the IP Profile returned to normal - the full 77.2 that is stand post-G.INP - at Plusnet's "Current Line Speed" (with a corresponding BT profile value), even though that is officially hidden now.
I've taken the usual steps to either re-sync, or to just disconnect PPP, but to no avail.
Is there something that still needs to be tweaked at PN towers?
These are small 2-3Mbps discrepancies that you wouldn't complain about normally (unless you only had 2-3Mbps), but they stand out very clearly in a graph. Given that most ISPs can achieve around 75Mbps throughput on an 80/20 line, and I was showing 74Mbps results myself, I find it is a bit annoying to have my line contribute poor statistics to Ofcom.
I'm sure I've reported similar discrepencies to Dave Tomlinson in the past...

---

Attached Graph
SamKnows test results from February to today.
This shows:
- Speed test results of either 71Mbps or 74Mbps from February through to April 10th.
- Results of either 66Mbps or 69Mbps on April 15th (after DLM de-intervention)
- Results of either 69Mbps or 72Mbps from April 16th through to July 12th - but obvious spots of degradation throughout June
- Results of mostly 72Mbps since the last PPP disconnection

---

Details
On the 10th April, DLM intervened because we were suffering power outages, with the RCD tripping up to 20 times in a couple of days.
G.INP (two-way) was in place at the time, and DLM intervention altered the settings a few times, but sync speed remained at 80/20. Eventually, DLM banded the line to 74/19 ... which caused a sync speed reduction, which in turn caused a throughput speed reduction. That's understandable.
The RCD problem went away. Not entirely (at first) but a new UPS stopped it having an ongoing effect on broadband. Hopefully fully solved since.
On the 14th April, DLM took away the banding, and a day later, it de-intervened entirely, leaving just the original G.INP setting. Since then, of course, G.INP has been made downstream-only.