We rolled back the update and restored to the last good version. This incident has been resolved.
We are currently investigating this incident. We believe it is due to a bad deployment and are rolling it back to last known good version