We discovered an incorrect version had been deployed accidentally. We have re-deployed the correct version and services have been restored.

We are reviewing this issue now and rolling back an update that was pushed earlier today.