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
![[object Object]](/_next/image?url=https%3A%2F%2Finstatus.com%2Fuser-content%2Fv1722037592%2Fsti2ckn7k49m8gbj2p3l.png&w=3840&q=75)