We've resolved the issue and apologize for the inconvenience caused.
Our authentication provider has found a resolution - we will investigate adding redundancy for our provider.
We fixed a loading issue which triggered an inadvertently triggered the Oops page.
We have resolved the issue and a refresh fixes it!
