Profile update please !

[#1]

Hi,
My Plusnet IP profile has been stuck on 7.1Mbps for the best part of a week (after a few bad connections during major roadworks outside my house), even though I am connecting at a DSL sync of >14Mbps at the moment.
Prior to this, I always connected at between 18M and 20M.
I raised a ticket to get this unstuck (48257132), but this has inappropriately started the standard fault reporting procedure.
As this looks overwhelmingly like another broken BT 'missing delta update' issue, this ticket is also broken.
Can someone please unstick the Plusnet IP profile and get it responding correctly again ?


ps
Why is this sort of thing _still_ happening, btw ?  Last time I had problems back in early summer, there was talk of a new system to remove the 'missing delta' issue that has plagued so many Plusnet customers.

[#2]

Yes it does not seem to be updating as it should lately.
ADSL uptime 6 days 6,936    BT IP 6119
Plusnet Current line speed:    5.5 Mb

[#3]

Hi there,
@disfroot - your line's definitely still dropping connection and I'm afraid that until that's sorted there's not much we can do to improve the profile. If you could confirm the checks requested on the ticket we'll get it escalated and investigated for you.
@billnotben - I suspect until the whole quantization thing is sorted your delta reports will keep coming through at 5500 though they might go up to 6000 if the sync speed stays where it is (not sure off the top of my head where the dividers are) but I've put your profile on our side to 6000 anyway, hope it improves things for you.

[#4]

Look - this 'stuck at 7.1Mbps' behaviour is new and is _not_ connected to the fact that my router re-boots itself from time to time. I've had no problems with the router doing this while I was connecting at 19M - my Plusnet IP profile was always at 16M. The infrequent re-boot events were not sufficient to cause this new behaviour. Keeping my IP Profile locked at _half_ my effective sync rate without letting the DLM do its thing is an unacceptable redefinition of service on your part.
Can you please post the graph you have of my Radius events ? I would like to know whether you are interpreting infrequent router re-boots as line instability or not.

[#5]

Hi disfroot,
Here's the graph, as you requested:
<img src="http://ccgi.psmith12.plus.com/visradius/generated/image13203983343043.png" />
I've also checked the profile at the exchange (on the delta report side of things) and that's set at 7150 on BTs side, so if the profile is stuck, it's there.
Further to that I've checked for a profile mismatch across the MSAN and BRAS, and while the check did come out as failed it's failed because the speed is lower than the fault threshold rate rather than the profile being mismatched - it's not, so the 7150 profile is consistent across the exchange kit.
That all points to a line fault, either with the profile not adjusting as it should or that the drops - as few as they are - are keeping your profile lowered. Whether we investigate the drops or the profile being below the FTR though, it still requires pushing as a fault.

[#6]

My profile also appears to be stuck. I've wait three days for it to change but it hasn't done so. 3mb when should be 5mb ( BT's profile on my exchange is more correct - using the 88% thing ).

[#7]

Hi there,
Currently the delta reports we're receiving for your line are for 3000 so we've set ours to match - that's correct as things stand at the moment (don't forget the bRAS quantization doesn't roll out in full until December).
In addition it's best not to make any changes to the profile or reset the SNR when a fault is open on the line I'm afraid. Things should settle down and improve when the fault has been resolved.