The issues have been resolved. We are monitoring for other errors, OnClock should be fully available.
The downtime and the previous ones were caused by a bad authentication token submitted by a client. We had a bug were we didn't escape this error properly and it would crash the entire API. We apologize for the inconvenience and we will make sure this doesn't happen again.