Good luck to the Kraken IT team! Bugs like these bugs can be a complete nightmare, anyone involved in both Infra and Development knows this. All the pressure of solving performance issues quickly probably caused this.
At least they are updating us and we can subscribe to email and sms updates also.
My only question is why they do not roleback to the working state and solve the problem the coming weeks??
Maybe because the last working state was 2 years ago and their backups don't reach that far in the past?
Before starting any new upgrade/update/release, it is the common practise to take a whole image backup of the current working state. So that, if any thing goes wrong it can be easily rolled back within hours if not minutes.
I am 100% sure there is some thing fishyyyy going on which KRAKEN is not telling us and that is what making all of us upset. Bottom line is, KRAKEN is not telling us the 100% tryth about what is actually happening.