Resolved -
This incident has been resolved.
Mar 21, 14:51 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Mar 20, 21:09 UTC
Update -
The issue is now resolved
Mar 20, 21:07 UTC
Update -
We have found the cause for the issue and are working on deploying a solution.
Mar 20, 20:43 UTC
Investigating -
We are currently investigating this issue.
Mar 20, 19:57 UTC