Cronofy experienced a notice incident on June 10, 2016, lasting 1d 18h. The incident has been resolved; the full update timeline is below.
Update timeline
- scheduled Jun 10, 2016, 02:10 PM UTC
We've been noticing occasional degraded performance from one of our Redis instances (the underlying cause of http://status.cronofy.com/incidents/8cfms7p23bl7 which was the most significant, usually it is barely noticeable). We've been advised by our provider that the best way forward is to move the instance onto a new server and the expected disruption of this process is 30 to 60 seconds, during which the API may be unresponsive. We've arranged for this to take place on Sunday 8am UTC and will be actively monitoring it.
- scheduled Jun 12, 2016, 06:44 AM UTC
Maintenance will begin as scheduled in 60 minutes.
- in progress Jun 12, 2016, 07:45 AM UTC
Scheduled maintenance is currently in progress. We will provide updates as necessary.
- monitoring Jun 12, 2016, 08:17 AM UTC
The instance has been moved, monitoring to ensure everything is ok.
- completed Jun 12, 2016, 08:32 AM UTC
The scheduled maintenance has been completed.