Statistics Unavailable

• 7:06 AM PDT (UTC-7)

  The issue has been resolved and is being monitored while we fix the underlying cause of this issue. We have filed a ticket with our infrastructure provider to make them aware that the services were incorrectly seen as healthy.

  5:49 AM PDT (UTC-7)

  We lost management control over the node responsible for communicating with our data warehouse. Normally, whenever a failure occurs, this service will automatically migrate to a healthy node. However, due to the specific way in which the management backend stopped working properly, everything was seen as healthy by the part of our stack responsible for replacing unhealthy services.

  This should have automatically triggered an emergency response, however it only triggered a low priority response due to it being incorrectly configured in our alerting tool. This has been resolved.

  Thank you for your patience while we work on this issue.