A member of our Dev Team noticed on the OSM Slack that they had issues with the same error. They fixed it by removing the refer-check at around 02:00. It might seem like OSM rolled out some changes that did not work as expected.
// Erik