Our platform is continuously monitored for outages, slowdowns, or other issues. Should there be any interruptions in service or a software release, we'll provide status updates here. Subscribe via SMS or Email and
never miss an update again.
Get email notifications whenever Epos Now creates, updates or resolves an incident.
Get text message notifications whenever Epos Now creates or resolves an incident.
Get incident updates and maintenance status messages in Slack.
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.