Previous incidents

We traced the issue to a recent front-end update, and deployed a fix. We apologize for any inconvenience and are implementing additional measures to prevent similar incidents in the future.