Resolved -
This incident has been resolved.
Oct 30, 08:59 UTC
Identified -
The issue has been traced to errors and network timeouts from a vendor. We are engaging our contacts with that vendor to resolve the issue.
Oct 29, 21:52 UTC
Update -
We are continuing to investigate this issue.
Oct 29, 20:41 UTC
Investigating -
We are currently investigating this issue.
Oct 29, 20:41 UTC