The issue appears to be fully resolved. We will continue to investigate (and check with partners) concerning root cause.

We may be on our way to recovery now. The flipped db server is taking hold, and a new string of API servers have healthy status now. Still suspect this is AWS related. Setting status to degraded performance until we're sure everything is okay...

Of of the primary database shard servers (hosted on AWS) appears to be non-responsive. We are attempting to manually flip another server to primary. [Should have happened automatically, but if AWS is having communications issues, it may have interfered].

We are continuing to investigate this issue.

Our team is investigating a service interruption. It appears to be an issue with AWS, but we have not confirmed that yet.