Started 6 Jun at 08:27am BST, resolved 6 Jun at 08:58am BST.
This issue is now resolved.
We are aware of this and currently deploying a fix.