We have identified the issue and fixed it. It was caused by a networking error in our DC and incorrect error handling by the underlying OTA infrastructure. We're continuing to monitor the performance of the service.
We apologize for any inconvenience caused.
Posted Aug 29, 2021 - 10:40 CEST
We are experiencing an interruption of the service. We are investigating the issue.