the big suprise is not just a return to lower (8ms) interleaving but I'm back on fast path woo! Graph looks the same lol..
If your connection is now near 'perfect' condition-wise, hopefully you will stay on fastpath (interleaving off).
However, following various engineer repairs, DLM for my connection has been reset on a wide open profile a few times (on fastpath).
After a few days, interleaving has always been switched back on again by DLM.
This has taken between the next day and up to 8 days.
AFAIK, none of us know how DLM determines interleaving is required for stability reasons, but it is no doubt based upom a combination of errored seconds, serious errored seconds & various other cumulative error counts over a period of time.
See the attached graphs (not from my own connection).
We can see the effect of interleaving eventually being switched on after 13 days from installation.
Once forward error connection has been applied via the interleaving process (Reed Solomon - RSCorr), see how the errored seconds, CRC errors & HEC errors more or less disappear, to be replaced by RS Corrected errors with the expense of lowered sync speed.
There had been other resyncs within the 13 days before interleaving was applied.