While the initial incident on our service provider is still not fully resolved, our systems have caught up, so we are closing this issue.
We are investigating increased latencies with the API. It seems the issue is related to an ongoing incident with one of our server providers.
