My interleaving was over 1200 as well, I thought I had my DLM manually reset this morning following a conversation with an openreach bod, but turns out it was automated, so you could if line is stable be back to fast path in 2 days.
Of course with an ongoing fault it doesnt mean a lot. As you could just as easily be back to interleaving 2 days after.
You should have reported right when your sync was really low, a clear no brainer fault in such a situation.
not too happy with sky at the moment tho, as well as the weird congestion behaviour in the mornings, I now have these pings on fast path, it used to be 7-8ms.
C:\Windows\system32>ping -t -4 bbc.co.uk
Pinging bbc.co.uk [212.58.246.78] with 32 bytes of data:
Reply from 212.58.246.78: bytes=32 time=14ms TTL=57
Reply from 212.58.246.78: bytes=32 time=13ms TTL=57
Reply from 212.58.246.78: bytes=32 time=14ms TTL=57
ipv6 is a bit lower but only 12ms.
tbb is a bit dodgy on single threaded ipv4 tests but ipv6 is flatlined max. I am wondering with so much of sky's traffic now going over ipv6 (think its more than half) they may have dialled back their ipv4 peering/transit capacity.
a single threaded ipv4 test of one of my servers is fine tho.