Previous incidents

The issue appears to have been an intermittent issue from a third party component. The issue have been resolved, but may linger in some browsers.

Please reach out on your Slack support channel or via support@enterspeed.com.

Today's issues was a result of a configuration issue in our deployment process that caused a secret to be set incorrectly. While we believed the issue had been fixed last week, a later update unintentionally reverted the change. Today a service was restarted after our system automatically recovered from a failed probe. This caused one of our services to fail in connecting with the data store as the secret was incorrectly configured.

Resolution:
We manually updated the configuration to restor...

We have investigated the cause of the errors earlier today.

The cause of the problems was due to a new JSON serialiser that was part of today's deployment. As a side note, we can share that we process a lot of JSON, and we can gain a significant performance improvement with the new JSON serialiser, but we digress.

In one specific use case, we had not tested the new code, which resulted in 0.83% of Ingest API requests returning an error response in a scenario where the requests were supposed...