It seems to be a temporary issue. In case it happens again more update will be provided, marking this as finished.

We are monitoring, will provide more details and a fix