KB Service Degradation Impacting Polaris and Black Duck SCA Scan Services

Final update

Our automation and data pipelines are fully operational, and they are making progress on reducing the OSS inventory backlog while also catching up on vulnerability information. To reach this state, we had to pause mappings for vulnerabilities reported against Chromium after 1:30 EDT on 09/02. We are investigating how to resume that without affecting the rest of the automation.

1. Resolved · Sep 4, 17:54 UTC
   Our automation and data pipelines are fully operational, and they are making progress on reducing the OSS inventory backlog while also catching up on vulnerability information. To reach this state, we had to pause mappings for vulnerabilities reported against Chromium after 1:30 EDT on 09/02. We are investigating how to resume that without affecting the rest of the automation.
2. Monitoring · Sep 3, 21:13 UTC
   System performance and stability continues to improve, and vulnerability data processing is now back to normal. The process responsible for adding components and new component versions has been brought online and will be monitored overnight. The team will determine in the morning if the rest of the data pipelines can be brought online. The next update is scheduled for 11am Eastern Sept 4, 2026
3. Monitoring · Sep 3, 16:29 UTC
   We have successfully processed a large volume of data associated with the affected project and continue to make steady progress reducing the remaining backlog. System performance remains stable, and current indicators are encouraging as we work toward restoring normal processing timelines for vulnerability data. We are also evaluating the activation of additional data pipelines to restore normal operations. The next update is scheduled for 5pm Eastern Sept 3, 2026.
4. Monitoring · Sep 2, 21:36 UTC
   The changes implemented earlier today continue to improve system performance, and backlog processing is progressing steadily. Additional data sources remain paused while we ensure the system can continue to operate reliably under increased load. We are closely monitoring the situation and will restore additional data processing as soon as conditions allow. The next update is scheduled for 11am Eastern on September 3rd
5. Monitoring · Sep 2, 16:27 UTC
   The team has identified the source of a substantial increase in data to be processed and is implementing controls to mitigate the adverse impact on the broader set of vulnerability data in the queue. Our immediate priority remains restoring the timely processing of vulnerability intelligence. To maximize recovery progress, we are letting the curated vulnerability pipeline jobs continue through the afternoon. Subsequently, the team will evaluate system performance and backlog reduction by 5pm EST before determining when additional data pipelines can be brought back online. As capacity is restored and stability is verified, those pipelines will be reintroduced in a controlled manner to help ensure sustained system reliability.
6. Monitoring · Sep 1, 21:17 UTC
   The team has successfully increased processing throughput and continues to see significant progress in getting through the vulnerability processing queue backlog. We continue to implement additional improvements focused on efficiency, resiliency, and long-term reliability, with positive results observed from the changes already deployed. Our immediate priority remains restoring the timely processing of vulnerability intelligence. To maximize recovery progress, we are letting the vulnerability pipeline jobs continue overnight and will evaluate system performance and backlog reduction in the morning before determining when additional data pipelines can be brought back online. As capacity is restored and stability is verified, those pipelines will be reintroduced in a controlled manner to help ensure sustained system reliability. The next update is scheduled for 11am Eastern on 9/2/26
7. Monitoring · Sep 1, 17:27 UTC
   We are continuing to monitor for any further issues.
8. Monitoring · Sep 1, 17:14 UTC
   We continue to make steady progress restoring normal performance to our KnowledgeBase (KB) processing pipeline. Through our ongoing investigation, the team identified several areas where performance and scalability could be further optimized. We have implemented a series of improvements across the platform, and those changes are already producing positive results. While delays remain in processing newly received data, there is no impact on customer access to existing KB content. Customers can continue to query KB data normally, and scans continue to use the latest available KB information currently in production. Our immediate focus is on restoring the timely processing of vulnerability intelligence (e.g., CVE and BDSA updates), which remain our highest-priority data stream. These processes are being closely monitored as we work through the accumulated backlog. Additional data pipelines (e.g., new component version coverage and license data) are being brought back online in a controlled manner as capacity is restored and system stability is validated. The next update is scheduled for 5pm Eastern
9. Identified · Aug 28, 17:33 UTC
   The issue has been identified and a fix is being implemented.
10. Investigating · Aug 28, 17:30 UTC
    We are currently experiencing a performance degradation in our KnowledgeBase (KB) pipeline, resulting in delays in message processing. We understand the critical role the KB plays in delivering timely license and vulnerability intelligence to our customers, and any disruption to that data flow is taken seriously. Restoring expected performance is the KB team's top priority, and remediation efforts are actively underway. We will continue to provide updates as progress is made.