We don't have full stats to see what happened on the day. Wouldn't be too surprised if activity at the cab has perhaps caused SNRm to start oscillating and subsequently errors to start racking up and DLM takes note. If it was one of the oscillating SNRm factors that we do see from time to time on various routers after a cab outage or power cut, the a quick reboot seldom clears it and it needs a full modem power down.
Why he was using the HubOne when he has a Billion available I've no idea. Because DLM doesn't take action until the next day, then the damage could have already been done before he put the Billion back on.
If he is fortunate he may be able to get a DLM reset. Plusnet arent one of those who can request it yet on the new system (neither are BTr come to that). Problem now is trying to get an OR engineer visit to do a full reset.
If this is first offence then DLM could be more lenient, but the fact it now appears to be banded doesnt look too good :/
I hope adslmax doesn't think it's below the low end of the estimate based on the IP Profile.
Once upon a time adslmax and I used to have very similar line stats and similar atten. Over the years I've lost quite a lot of headline speed to cross-talk. Max is one of the very few fortunates who is on a vectored cab and reaped back any cross-talk losses.
Me I'm stuck on an ECI cab with no hope of vectoring and things like G.INP and xdB looking increasingly slim.
According to Openreach my speed range estimate is 80-69.1
There have been times when my sync speed is below that when DLM kicks in, but PN refuse to do anything because the MGAL is 63.1.
It's why I have to watch my line so close because when it starts oscillating, DLM kicks in and there is not much I can do. One of the reasons if I migrated anywhere else it would have to be someone who uses Speed profile otherwise I'd get stuck even worse. Aside from watching out for the oscillations and trying to catch it before DLM notices, then there's no point me stressing out.