Container Scanning in Pipelines Degraded

Incident Report for Snyk

Resolved

Snyk engineers have monitored the fix, and all services are functioning as expected. The Snyk incident response has been stood down, and the incident is now resolved.

Posted Jul 17, 2025 - 21:15 UTC

Monitoring

Our engineers have deployed a fix to address the issue leading to failed scans.

We are now monitoring to ensure the success of the fix.

Posted Jul 17, 2025 - 11:40 UTC

Identified

Our Engineers have identified what they believe to be the root cause of the issue and are now working on a fix.

We will keep you updated with our progress.

Posted Jul 17, 2025 - 06:24 UTC

Investigating

Snyk is currently investigating reports of failed scans related to container images. The Snyk incident response team has been activated and investigating this issue further. Current impact scope appears to be limited to scans of locally built images within pipelines that use Snyk images, such as GitHub Actions and Bitbucket pipelines, when utilizing the latest CLI version (1.1298.0).

Posted Jul 16, 2025 - 20:13 UTC

This incident affected: SNYK-GOV-01 (app.snykgov.io) (Snyk Container), SNYK-US-01 (app.snyk.io) (Snyk Container), SNYK-US-02 (app.us.snyk.io) (Snyk Container), SNYK-EU-01 (app.eu.snyk.io) (Snyk Container), and SNYK-AU-01 (app.au.snyk.io) (Snyk Container).