All scans are now running without delay. We apologise for the inconvenience.

Scan queue performance has returned to normal, and all scans are now running without delay. We will continue monitoring the system closely.

Since yesterday, we’ve seen noticeable improvements in performance, with scans launching with much lower delay. We’ve deployed an additional fix and are gradually bringing workers back to clear the scan queue.

In parallel, we’re closely monitoring the service to minimize any further impact.

We identified that scans are running with significant delays due to the issue found. We are currently applying configuration changes and closely monitoring the system to restore performance to expected levels.

We’ve deployed a fix and are actively monitoring the results.

In parallel, we’re closely monitoring the service to minimize impact as much as possible.

We identified an issue where ECS tasks launched for scans were not shutting down after completion. While investigating the container logs, we noticed an entry-point log line that normally appears only during container startup.

As a result, tasks that should have exited cleanly after completing the scan were instead restarted, remaining in a running state indefinitely and causing unnecessary resource consumption. As the task is restarted it keeps listening to the scans queue rejecting scan tasks as their assigned one was successfully completed. Therefore, it increases the number of available tasks ready to pick a scan decreasing the possibility of getting the assigned one. This is making scans not to run as the underlying task is not getting the scan that is assigned.

This was introduced by a new restart policy conflicting with the scan task lifecycle. We are updating the configuration to explicitly disable the restart policy.