Get webhook notifications whenever All Blackduck Status Page creates an incident, updates an incident, resolves an incident or changes a component status.
We are pleased to confirm that the previously reported issue affecting Polaris SCA has been fully resolved, and normal service has been restored as of 6 pm EDT.
All systems are now operating as expected. Our teams will continue to monitor closely to ensure ongoing stability.
We appreciate your patience and understanding throughout this incident. Should you experience any further issues, please contact our support team.
Posted Sep 01, 2026 - 22:16 UTC
Update
We are currently investigating a service degradation affecting the SCA Scan Service associated with the Component Locator. Our engineering team is actively investigating and working to restore normal operation as soon as possible. We will continue to provide periodic updates supplemented with additional updates as more information becomes available. We appreciate your patience while we work to resolve this issue. Scans Affected Polaris SCA scans On-prem and hosted bridge CLI-initiated SCA scans
Manifestation Affected customers will experience scan failures with the following messages logged:
Running Component Locator v2.4.2 Detect run failed. Index 1 out of bounds for length 1 Generating Component Location Analysis File for All Components: FAILURE Overall Status: FAILURE_UNKNOWN_ERROR
Workaround Polaris Source Upload Scans: None Polaris SCM Scans: None Polaris, on-prem, or hosted bridge CLI Scans: Disabling Component Location Analysis (CLA) by modifying the bridge CLI command will allow scans to complete:
Current Status A fix has been developed, has completed QA and end-to-end testing, and is now being prepared for deployment. ETA for completion of fix deployment is Friday, Sept. 4th, 2026.
Next Scheduled Status Update Wednesday, Sept. 2nd, 2026
Posted Aug 28, 2026 - 17:17 UTC
Update
We are currently investigating a service degradation affecting the SCA Scan Service associated with the Component Locator. Our engineering team is actively investigating and working to restore normal operation as soon as possible. We will continue to provide periodic updates supplemented with additional updates as more information becomes available. We appreciate your patience while we work to resolve this issue. Scans Affected Polaris SCA scans On-prem and hosted bridge CLI-initiated SCA scans
Manifestation Affected customers will experience scan failures with the following messages logged:
Running Component Locator v2.4.2 Detect run failed. Index 1 out of bounds for length 1 Generating Component Location Analysis File for All Components: FAILURE Overall Status: FAILURE_UNKNOWN_ERROR
Workaround Polaris Source Upload Scans: None Polaris SCM Scans: None Polaris, on-prem, or hosted bridge CLI Scans: Disabling Component Location Analysis (CLA) by modifying the bridge CLI command will allow scans to complete:
Current Status The root cause of the issue has been identified, a fix has been developed, and is now in QA and end-to-end testing. ETA for completion of testing is Wednesday, Aug 26th or Thursday, August 27th.
Next Scheduled Status Update Wednesday, August 26th, 2026
Posted Aug 25, 2026 - 05:49 UTC
Update
We are currently investigating a service degradation affecting the SCA Scan Service associated with the Component Locator. Our engineering team is actively investigating and working to restore normal operation as soon as possible. We will continue to provide periodic updates supplemented with additional updates as more information becomes available. We appreciate your patience while we work to resolve this issue. Scans Affected Polaris SCA scans On-prem and hosted bridge CLI-initiated SCA scans
Manifestation Affected customers will experience scan failures with the following messages logged:
Running Component Locator v2.4.2 Detect run failed. Index 1 out of bounds for length 1 Generating Component Location Analysis File for All Components: FAILURE Overall Status: FAILURE_UNKNOWN_ERROR
Workaround Polaris Source Upload Scans: None Polaris SCM Scans: None Polaris, on-prem, or hosted bridge CLI Scans: Disabling Component Location Analysis (CLA) by modifying the bridge CLI command will allow scans to complete:
Current Status The root cause of the issue has been identified, a fix has been developed, and is now in QA and end-to-end testing. ETA for completion of testing is Wednesday, Aug 26th or Thursday, August 27th.
Next Scheduled Status Update Wednesday, August 26th, 2026
Posted Aug 25, 2026 - 05:47 UTC
Update
We are currently investigating a service degradation affecting the SCA Scan Service associated with the Component Locator. Our engineering team is actively investigating and working to restore normal operation as soon as possible. We will continue to provide periodic updates supplemented with additional updates as more information becomes available. We appreciate your patience while we work to resolve this issue.
Manifestation Affected customers will experience scan failures with the following messages logged: Running Component Locator v2.4.2 Detect run failed. Index 1 out of bounds for length 1 Generating Component Location Analysis File for All Components: FAILURE Overall Status: FAILURE_UNKNOWN_ERROR
Workaround Polaris Source Upload Scans: None Polaris SCM Scans: None Polaris, on-prem, or hosted bridge CLI Scans: Disabling Component Location Analysis (CLA) by modifying the bridge CLI command will allow scans to complete: ./bridge-cli.exe --stage polaris --input input.json --diagnostics detect.args='--detect.component.location.analysis.enabled=false'
Current Status The root cause of the issue has been identified and a fix is in progress. Estimated time for resolution is 2-3 days.
Next Scheduled Status Update Monday, August 24th, 2026
Posted Aug 21, 2026 - 22:39 UTC
Identified
We are currently investigating a service degradation affecting the SCA Scan Service associated with the Component Locator. Our engineering team is actively investigating and working to restore normal operation as soon as possible. We will continue to provide periodic updates supplemented with additional updates as more information becomes available. We appreciate your patience while we work to resolve this issue.
Manifestation Affected customers will experience scan failures with the following messages logged: Running Component Locator v2.4.2 Detect run failed. Index 1 out of bounds for length 1 Generating Component Location Analysis File for All Components: FAILURE Overall Status: FAILURE_UNKNOWN_ERROR
Workaround Polaris Source Upload Scans: None Polaris SCM Scans: None Polaris, on-prem, or hosted bridge CLI Scans: Disabling Component Location Analysis (CLA) by modifying the bridge CLI command will allow scans to complete: ./bridge-cli.exe --stage polaris --input input.json --diagnostics detect.args='--detect.component.location.analysis.enabled=false'
Current Status The root cause of the issue has been identified and a fix is in progress. Estimated time for resolution is 2-3 days.
Posted Aug 21, 2026 - 18:01 UTC
This incident affected: Polaris: North America (Scan Service, Integrations), Polaris: Europe (Scan Service, Integrations), and Polaris: Saudi Arabia (Scan Service, Integrations).