Hello Community!
As promised, we've done a bit of investigating into the issue that happened.
Essentially a database failed for unknown reasons. - most likely a hardware failure. It was a compounding issue after that when the database did come back online some issues were caused by the outage itself.
We've since resolved those issues and we have put in contingencies to prevent this from happening again in the future with "read-replica" databases - essentially a redundancy plan - so that if the primary database fails, the app will still function.
Sincerely apologize for the inconvenience this downtime has caused - we know first hand, how important these tools are to your workflow.
