Resolved
Database is back online
Identified
The database is currently restarting, and we expect it to be back online in the next few minutes. Once the database is back online, we're going to mark this incident resolved for now as we continue to investigate what caused this to happen
Identified
We are continuing to work on a fix for this issue.
Identified
We're seeing the same issues that occurred last night with one of our main cluster databases. This database hosts a subset of our applications on the main cluster. The issues involve the database getting into a bad state where it has increased latency. We're able to resolve the issues by restarting the database, and are doing that now. We still haven't identified what cause the issues to start in the first place, however, so there's risk of the problems recurring.