On February 14, 2024, our users experienced a service disruption when attempting to log in. The impacted users would have experienced intermittent logins and received 5xx error messages between 17:38 and 18:38 UTC. We sincerely apologize for the impact this has caused you. On February 14th, at 17:30 UTC, Engineers made back-end updates to the infrastructure’s extensibility repository, introducing a regression. This implementation inadvertently applied previous DNS record values that targeted our the wrong infrastructure. These environments had since been scaled down, resulting in the 100% requests failing with HTTP 503 errors. DNS records were manually updated to proxy via the network edge provider to mitigate the impact. Furthermore, records were synchronised accordingly to avoid similar issues in the future.