This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are currently investigating this issue.
17:05 UTC - 14 November 2018