No incidents reported
We we're able to identify a Redis instance that had hit it's connection capacity due to increase load. We've managed to reduce the load on this server and restore service.
We'll be adding additional monitoring for this case as well as adding additional safety mechanisms around our scaling mechanism to prevent this in the future.
Internal tools alerted us to an elevation of API errors and exceptions coming from our application. Our team is investigating.