Previous incidents

We have now successfully moved to a new region and the backlog of missing destination messages have been emptied.

We are sorry for the inconvenience caused for this destination outage. We are awaiting a expiation from our cloud service provider and will based on that evaluate what can be done to prevent similar problems in the future.

After observing the metrics after the implemented workaround yesterday afternoon, we can now resolve the Ingest API degradation issue.

We will update with a full post mortem when we have debriefed with our cloud service provider.

Sorry for the inconvenience and please reach out if you have any questions.

Recovered after Azure returned to normal operations.

During the night Microsoft have declared the incident mitigated and there should be no further impact on Enterspeed services.

If you experience any problems or have any questions please write to us on your Slack support channel or via support@enterspeed.com.

All services are now back online and fully restored. The Delivery API was not affected by this incident.

What we know so far, is that a routine deployment, proved not to be business as usual. Despite being peer reviewed, manual and automated tested on test environments our upgrade of a key component broke when applied in production. We will further investigate why this was the case.

We are very sorry for the inconvenience, and standby to answer any questions either on your Slack support...