Snyk incident

Scan and Recurring Test Degradation

Minor Resolved View vendor source →

Snyk experienced a minor incident on May 19, 2026 affecting Snyk Code and Snyk Open Source, lasting 14h 57m. The incident has been resolved; the full update timeline is below.

Started
May 19, 2026, 05:08 PM UTC
Resolved
May 20, 2026, 08:06 AM UTC
Duration
14h 57m
Detected by Pingoru
May 19, 2026, 05:08 PM UTC

Affected components

Snyk CodeSnyk Open Source

Update timeline

  1. investigating May 19, 2026, 05:08 PM UTC

    Snyk engineers are currently tracking Code Scan and Open Source Reachability scan failures—including Recurring Tests—within the Multi-tenant Snyk-US-01 environment. Our incident response team has been activated, and we are actively working to resolve the issue.

  2. investigating May 19, 2026, 08:09 PM UTC

    We have successfully mitigated the issue impacting Open Source Reachability Scans and are actively monitoring the environment to ensure continued stability. Meanwhile, our engineering team is continuing to investigate the performance degradation affecting Code Scans. We will provide further updates as they become available.

  3. resolved May 20, 2026, 08:06 AM UTC

    We observed no further impact during our monitoring period. The Snyk Incident Response has now been stood down.