Scanii.com Status

Resolved: The incident has been resolved and service fully restored.

Identified: Our monitors have identified an issue with our administrative portal (www.scanii.com) and our engineers were dispatched to address it. This does not impact content processing.

Resolved: The incident has been resolved and service fully restored.

Identified: The source of the issue appears to be problems with our cloud provider, AWS (https://health.aws.amazon.com/health/status), in the us-east-1 region

Identified: We are continuing to work on a fix for this issue.

Identified: Our monitors have identified an issue with our administrative portal (www.scanii.com) and our engineers were dispatched to address it. This does not impact content processing.

Resolved: The incident has been resolved and service fully restored.

Identified: Our monitors have identified an issue with our administrative portal (www.scanii.com) and our engineers were dispatched to address it. This does not impact content processing.

Resolved: The incident has been resolved and service fully restored.

Identified: Our monitors have identified an issue with our administrative portal (www.scanii.com) and our engineers were dispatched to address it. This does not impact content processing.

Resolved: The incident has been resolved and service fully restored.

Identified: Our monitors have identified an issue with our administrative portal (www.scanii.com) and our engineers were dispatched to address it. This does not impact content processing.

Resolved: This incident has been resolved.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: 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

Monitoring: Still ongoing

Identified: We are continuing to work on a fix for this issue.

Identified: 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

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

Investigating: We are continuing to investigate this issue.

Investigating: We are continuing to investigate this issue.

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

Resolved: This incident has been resolved.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: 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

Monitoring: Still ongoing

Identified: We are continuing to work on a fix for this issue.

Identified: 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

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

Investigating: We are continuing to investigate this issue.

Investigating: We are continuing to investigate this issue.

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

Resolved: This incident has been resolved.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: 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

Monitoring: Still ongoing

Identified: We are continuing to work on a fix for this issue.

Identified: 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

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

Investigating: We are continuing to investigate this issue.

Investigating: We are continuing to investigate this issue.

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

Resolved: This incident has been resolved.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: 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

Monitoring: Still ongoing

Identified: We are continuing to work on a fix for this issue.

Identified: 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

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

Investigating: We are continuing to investigate this issue.

Investigating: We are continuing to investigate this issue.

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

Resolved: This incident has been resolved.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: 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

Monitoring: Still ongoing

Identified: We are continuing to work on a fix for this issue.

Identified: 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

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

Investigating: We are continuing to investigate this issue.

Investigating: We are continuing to investigate this issue.

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

Resolved: The incident has been resolved and service fully restored.

Identified: Our monitoring system has identified issues with the region and our engineers have been dispatch to investigate.

Resolved: This incident has been resolved.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: 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

Monitoring: Still ongoing

Identified: We are continuing to work on a fix for this issue.

Identified: 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

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

Investigating: We are continuing to investigate this issue.

Investigating: We are continuing to investigate this issue.

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