This incident has been resolved.
A fix has been implemented and we are monitoring the results.
14:46 UTC - 9 May 2019