On August 10, 2015 we were affected by another vendor level outage from Amazon Web Services (AWS).
Around 3:15pm we started noticing a subtle increase in the error rates that we were getting from the AWS S3 API, the AWS service we are using for file storage for storing files like clocking photos for example. Around 5:31pm AWS updated their status dashboard that the service was down.
Around 6:23pm we started evaluating how big the damage was and we ruled out that it was only MyClock Web that was affected by the outage. Clockings made through MyClock web were not reaching our Time server. Around 7:57pm we completed the full recovery of the lost clockings.
If you have any questions please let us know by clicking here .
— Vincent Paca