My chart is very much the same as yours. The original problem is still there with this regular repeating period of higher than normal latency, but no where near as bad, but I don't feel confident in Cerberus and their network as their latest service statement says the issue is resolved and they are closing the incident. Clearly whatever was faulty is still faulty and having an affect, yes it may be mitigated and not service affecting now, but there is definitely a weakness in their infrastructure that has not been fixed. Given the impending lock downs and needing a reliable connection and the premium many of us pay for a more business oriented ISP like Cerberus, I'm not impressed they are happy to suggest the issue is resolved when clearly it is still bubbling away..
The incident closed statement may just be poor wording and a break down in communication on their service status page and maybe some scheduled work is planned to swap out some faulty part and get things stable again in the week when parts arrive and we will get a more comprehensive update Monday.
For me I'm coming up to needing to move from FTTPoD first 12 months to a native FTTP product, I was planning on staying with Cerberus but now changing my mind.
For comparison sakes this is my typical BQM from just before the issues started:
Edited by E300 (Sun 01-Nov-20 08:37:50)