US data center database read replica lagging
Incident Report for Cronofy
This incident has been resolved.
Posted May 08, 2019 - 00:49 BST
We are continuing to monitor for any further issues.
Posted May 08, 2019 - 00:24 BST
Replica lag is back to normal levels (near zero) and we are continuing to monitor as all processing catches back up.

We will also review if there are any actions we need to take to ensure nothing has been missed or lost in the meantime (though that should not be the case).
Posted May 07, 2019 - 17:23 BST
Our read replica, used to serve portions of our workload, is lagging significantly behind the primary database. This may lead to stale results being returned from our API and slower synchronization than normal.

We are investigating and in contact with AWS to resolve the problem.
Posted May 07, 2019 - 16:32 BST
This incident affected: API, Background Processing, and Web App.