Same thing was happening at US site.

 

It seems to have resolved itself now.

View solution in original post