We have found that an onld deployment had been pushed which caused issues with our redis server, forcing it to halt. Once we saw that the old image was deployed, we re-deployed the recent one and redis could get back on it's feet again.

We will continue to monitor for the next hours, and deploy a fix so that this issue does not repeat itself.