The incident is now resolved. The root cause was due to a change in the SSL-version by a third party provider. We've since pinned the SSL version such that this cannot occur in the future.

We've detected that api.frigade.com returns invalid SSL certificate errors.