Thanks for the responses.
I was indeed interleaved, which I should have mentioned and what I should have also asked, was whether the service was banded, not capped. I blame the sleep deprevation from having a 9 week old!
The line had G.INP enabled the following day and after 1 or 2 resyncs (Lost Carrier), has been climbing back up to nigh on the max I've seen on the line, sync wise. The upstream sync is also the highest it's been since the line initially settled down after being fibre enabled.
Latency has increased from around 11ms to 16ms to www.bbc.co.uk,
my usual benchmark. So I'd like to understand why that's happened.
I'm monitoring it for a separate gateway related issue but it seens to be more resiliant than before, despite some choppiness on the SNRM. Maybe that's because i'm now going via TTB backhaul and not BTW?!
Thus far I'm very impressed with AA. Bearing in mind when I migrated, I chose the 2TB package and as of today, I have 2.98TB of capacity, which just adds the icing on the cake.
The control panel is excellent too, meaning I no longer feel the need for the TB BQM. And the listed view of occurences on the service and account. Now I just need them to sort out the log running line issue!
Service: TT FTTC 80/20 (2TB)
Modem/ router: Billion BiPAC 8800AXL R2
Current sync: 54623/ 9366
Edited by youngsyp (Mon 01-Oct-18 13:06:57)