Resolved -
The issue was observed to occur as of 6:22 am. Ater ensuring all server components were working correctly, the incident was resolved at 8:29 am.
Apr 18, 08:38 CEST
Investigating -
We are currently investigating this issue.
Apr 18, 08:36 CEST