This incident has been resolved.
Dec 2, 22:47 CET
We identified and removed a service which was consuming excess CPU on the affected node. After removing/restarting the service, we are seeing all monitoring returned to healthy.
Dec 2, 21:46 CET
We are continuing to work on a fix for this issue.
Dec 2, 21:16 CET
The issue has been identified and a fix is being implemented.
Dec 2, 21:07 CET
Two nodes in the US1 cluster have indicated some service errors. We are attempting to shuffle production workloads away from these servers as we investigate.
Dec 2, 21:02 CET