This incident has been resolved.
One of the backend databases crashed. We are working on restoring service.
We are currently investigating this issue.
14:44 UTC - 4 July 2019