Resolved -
This incident has been resolved.
Oct 20, 18:55 EDT
Update -
We are continuing to monitor for any further issues.
Oct 20, 15:53 EDT
Update -
We are now able to scale again and are processing through a large backlog of fetch/asynchronous work. Synchronous analysis calls should be mostly restored to normal - for US1
All other regions should be working normally now
Oct 20, 15:33 EDT
Monitoring -
Still ongoing
Oct 20, 11:57 EDT
Update -
We are continuing to work on a fix for this issue.
Oct 20, 11:56 EDT
Update -
We are also unable to harvest compute capacity in us-east-1, so we're at AWS's mercy in order to fully recover. It looks like they are actively working to restore EC2
Oct 20, 09:44 EDT
Identified -
The issue is primarily caused by SQS failing in us-east-1, that is unfortunately also impacting other regions that submit consumption data to us-east-1
Oct 20, 09:29 EDT
Update -
We are continuing to investigate this issue.
Oct 20, 09:07 EDT
Update -
We are continuing to investigate this issue.
Oct 20, 09:06 EDT
Investigating -
Processing is behind across multiple regions, we are investigating and will provide an update as soon as possible. At this point we believe this is fall out from the major AWS outage earlier
Oct 20, 05:05 EDT