This incident has been resolved.
The issue has been identified and a fix is being implemented.
21:02 UTC - 10 September 2018