We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.