We've now resolved the incident. Thanks for your patience.
We already deployed a fix and monitoring the results of it.
12:10 UTC - 19 June 2019