This issue was resolved and resulted in approximately 8 minutes of downtime. We are currently doing a root cause analysis.
Some users reported error 5000 which is a generic catch all error message.
10:23 EDT - 22 July 2020