> Thanks for your patience, the issue should be resolved now.
I unfortunately don't have any particularly juicy details to share about the underlying cause, but the short version is that we had a route that was hitting Redis when we didn't expect it to hit Redis and that ended up creating too much load in combination with our hourly scheduled routes.