Resolved -
This incident has been now been resolved.
May 8, 01:05 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
May 8, 00:42 UTC
Update -
We are continuing to work on a fix for this issue.
May 8, 00:11 UTC
Update -
Our engineers are continuing to work on a fix for this issue.
May 7, 22:35 UTC
Identified -
The issue has been identified and is isolated to a specific region in US East only. We are working with our cloud provider to implement a fix.
May 7, 21:30 UTC
Update -
Our engineers are continuing to investigate.
May 7, 21:07 UTC
Investigating -
We are currently investigating elevated 4xx errors on the platform.
May 7, 20:36 UTC