Resolved -
This incident has been resolved.
Apr 22, 16:55 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Apr 22, 15:24 UTC
Update -
We are continuing to investigate the issue and believe it may be related to a network problem. Further updates will be provided as we learn more.
Apr 22, 14:45 UTC
Update -
We are still investigating the issue and will provide further updates as more information becomes available.
Apr 22, 13:44 UTC
Investigating -
We are actively investigating the issue. Further updates will be posted shortly.
Apr 22, 12:41 UTC