All times in this report are in BST.
At around 17:02 the ResDiary support team we were notified that users were experiencing issues accessing their restaurant diary on the UK/Europe server. This was escalated to an engineer to investigate at 17:10 and after initial investigation and performance of the database was identified as the underlying issue.
At 17:35 the engineer made a configuration change to the database to improve the performance and shortly after the system returned to normal.
We’d like to sincerely apologise for any inconvenience caused and assure you that we are focused on identifying and implementing the changes required to prevent situations like this in the future.
We are currently working on improving our monitoring of our SQL Server databases, and should have improved monitoring and alerting online within the next few weeks. This will allow us to react faster to situations like this, ideally solving them before they become user visible.
We are working on identifying the parts of our application that cause the highest database usage, and will be making changes to make it less likely we have these kinds of incidents in the first place.
We will investigate the particular query that caused the problem on Sunday, and will aim to prevent it from causing us problems in future.