The issue was resolved and all services should be up and running again. The underlying issue was a faulty database node behaving in unexpected ways. Our operations team will analyze this issue further to ensure it will not happen again. If you are still experiencing any issues, please reach out to support.
