This incident has been resolved.
The issue has been identified and a fix is being implemented.
10:36 UTC - 20 June 2018