Live  /  Blackduck  /  Incident

Blackduck: Service degradation affecting the Polaris SCA Scan Service associated with the Component Locator

Blackduck · blackduck.comMinor incidentResolved2026-09-01 16:03 UTC
Public — what happened

Summary

Blackduck reported a minor degradation starting 2026-08-21 at 18:01 UTC that caused software composition analysis (SCA) scans in Polaris to fail, including scans launched through the on-prem or hosted bridge command-line tool, with the problem tied to a feature called the Component Locator. Blackduck said customers using the command-line tool could get scans to finish by turning off Component Location Analysis, which comes with some limitations, but that no workaround was available for source upload or SCM scans. The company said a fix had passed testing and was being readied for rollout, with deployment expected to be finished by Friday, Sept. 4th, 2026, and the next update planned for Wednesday, Sept. 2nd, 2026. The incident was still listed as identified, though the facts given record a resolution time of 2026-09-01 at 22:27.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Blackduck against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Blackduck: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Blackduck report →

More from Blackduck

The full archive is on the Blackduck status & history page.

Related: Blackduck status & history. SquidGrid is not affiliated with Blackduck.