Resolved -
It appears we had a CPU spike on our database server which caused the outage. We are researching the root cause.
Mar 14, 13:57 UTC
Update -
We are continuing to investigate this issue.
Mar 14, 13:54 UTC
Investigating -
We are currently investigating this issue.
Mar 14, 13:38 UTC