The incident has been resolved and we are working on uncovering the root cause.

Update: Root cause was identified as an overloaded redis server component. A large key was identified as the cause of increased network bandwidth and latency of the redis server, decreasing performance and impacting downstream services such as our API components. This key has since been removed and additional logging added to allow us to catch similar incidents in the future.

We've been alerted to degraded response times on our APIs and are investigating.