Live / Blackduck / Incident
Blackduck: KB is having issues with MaaS scans
Blackduck · blackduck.comResolved2026-10-06 21:31 UTC
Public — what happened
Summary
Blackduck said that on October 6, 2026 at 20:34 UTC it found a problem in its North America region causing binary and package manager matching to fail during MaaS scans, while signature matching kept working normally. By 21:11 UTC the company reported that scans were working properly again, though it was still looking into what had caused the problem. Blackduck did not share a cause, and the incident was marked resolved at 21:31.
Affected
Scan Service
Timeline
- Started — 2026-10-06 20:34 UTC
- Investigating — 2026-10-06 20:34 UTC (2 updates)
- Resolved — 2026-10-06 21:31 UTC · 57 min after it started
With SquidGrid — where it starts on the route
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 seeCustomers 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
Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.