Well after much more discussions I'm sure no one here will be surprised that the bottom line here is nothing will be done. As my line cannot attain a stable green ILQ they are unable or unwilling to do anything.
I have been doing a little testing over the past few days to see if my line could achieve and perhaps sustain a green ILQ but having reduced sync speed to 55000kbps and then 50000kbps I have proved that the line will not achieve a stable green ILQ at those speeds and frankly I suspect it will not matter how low I go the line behaviour seems to make it unlikely to get to a stable green ILQ at all. What this I believe indicates is that whatever was severely wrong with my line last June through September albeit intermittently has never been properly or fully diagnosed or resolved, whatever happened to resolve it has simply reduced in severity to an extent that I can achieve an amber ILQ status which is fairly stable and I am certain that nothing was actually done to the line to fix anything. I suspect that whatever the fault is it is likely to happen again in the future (maybe we need an HGV to hit the cab
or some other local disaster). If said fault does re-appear then I hope it goes solid and they cannot then slope shoulders on it as happened before.
As to the actual error rates I see there is no pattern to them and they occur at random times, last night for example it was most of the evening and night when ES were high. I see sudden spikes of CRCs at random times of the day and night otherwise it bumbles along at maybe one or two every couple of minutes.
I'd be interested to know how the ES count correlates to the other errors, for example does just 1 CRC in a second cause that second to be counted as an error second, and what other errors will cause the ES count to be incremented?