Aqua incident

Potential Delays in Image Scanning in Workload Protection

Minor Resolved View vendor source →

Aqua experienced a minor incident on November 28, 2024 affecting Aqua Cloud API Status and Cloud Account Scanning and 1 more component, lasting 3h 18m. The incident has been resolved; the full update timeline is below.

Started
Nov 28, 2024, 01:47 PM UTC
Resolved
Nov 28, 2024, 05:06 PM UTC
Duration
3h 18m
Detected by Pingoru
Nov 28, 2024, 01:47 PM UTC

Affected components

Aqua Cloud API StatusCloud Account ScanningVulnerability ScanningESEReal-Time Events ServiceAqua Cloud Console StatusDynamic Threat Analysis (DTA) ScanningRemediation Service

Update timeline

  1. investigating Nov 28, 2024, 01:47 PM UTC

    We are currently observing elevated scan queue activity in the Image Scanning feature within Workload Protection. As a result, you may experience slight delays in scan processing. Impact: While most scans are processing as expected, some may take longer than usual. All other Aqua platform functionalities remain unaffected. Next Steps: Our team is actively investigating the situation and working to ensure normal scan performance is restored as quickly as possible.

  2. identified Nov 28, 2024, 02:01 PM UTC

    We have identified the root cause of elevated scan queue activity affecting the Image Scanning feature in Workload Protection. This may result in slight delays for some scan processes. Impact: While most scans are progressing as expected, some may experience minor delays. Other Aqua platform functionalities are operating normally. Current Status: Our team is actively working on implementing a fix to restore optimal scan performance.

  3. monitoring Nov 28, 2024, 02:33 PM UTC

    We will be deploying a fix in the next 30 minutes to address the ongoing issue and we will closely monitor the system to ensure stability and performance.

  4. resolved Nov 28, 2024, 05:06 PM UTC

    The issue with the scan queue activity in the Image Scanning feature within Workload Protection has been resolved. The fix has been successfully deployed. All services are back to normal and fully operational.