Resolved after 10 minutes
Looks like our reverse-proxy was the culprit. We've juiced it to hopefully avoid this issue in the future :)
Posted 1 year ago
Monitoring
A fix has been implemented and we are monitoring the results.
Posted 1 year ago
Investigating
We are currently investigating this issue.
Posted 1 year ago
Component impacted: Caffeinated