Recent Incident Statement
Incident Report for Epos Now
Resolved
On Sunday, the 1st of May, the 'read' replica of our central database became corrupted. We couldn't recreate the replica database, where we run the back office reports, due to long-running activities that ensured the main database was in good shape, plus additional backups required to reestablish the replica.

Unfortunately, the new replica didn't work as we expected. Consequently, the decision was made to temporarily disable reports in the back office to guarantee the continuity of Till transactions operation.

Over the last few days, we have implemented several performance optimisations in the main database and enabled reports in that database. We also ensured all our backups are correct as expected. We are currently working towards reestablishing the read replica, so we can keep reports and operations running on different databases again.
Posted May 06, 2022 - 16:10 BST
This incident affected: EPOS NOW HQ.