This incident is resolved.
A fix has been implemented and we are monitoring the results.
We are currently investigating this issue.
18:24 UTC - 12 October 2020