Latency returned to normal and errors rates within acceptable limits. Interact uses an in-memory data storage technology to store logged in users details (session). The technology stores data across many nodes for scalability and redundancy. During this incident a single node had detected itself as unhealthy and was in the process of transferring it’s data to other healthy nodes. Logged in users who were allocated to the unhealthy node observed high than usual latency until the process was complete. The refresh rotation of the web server infrastructure aided in the draining of the unhealthy node.

Service returning to normal latency levels. Will update shortly

We have begun a forced rotation of infrastructure serving web traffic. No downtime or interruptions expected. API / Mobile / Asset Handling / In-line Preview / Login service remain unaffected

Interact is recieveing alerts of increased latency within our US pod. Investigating