Resolved -
We identified an internal networking upgrade as the cause of the elevated errors. This has been resolved.
Jun 19, 01:35 UTC
Identified -
The issue has been identified and a fix is being implemented.
Jun 19, 01:27 UTC
Update -
We are continuing to investigate this issue.
Jun 19, 00:52 UTC
Update -
We are continuing to investigate this issue.
Jun 19, 00:52 UTC
Investigating -
We have identified an networking issue, we are investigating and will provide updates soon
Jun 19, 00:43 UTC