We have reverted the change which was responsible for this issue.
We are currently investigating this incident.