Minor impactResolvedDevOps

Snyk incident: Scan and Recurring Test Degradation

Snyk reported this minor-impact incident on its official status page on May 19, 2026, 17:08 UTC. It was resolved after 14h 58m.

Right now Snyk is operational. Live Snyk status →

🔔 Get alerted when Snyk has issuesFree · email alerts · no credit card
May 19, 2026, 17:08 UTC
started
May 20, 2026, 08:06 UTC
resolved
14h 58m
duration
Minor
impact

Affected components

  • Snyk Code
  • Snyk Open Source
  1. resolvedMay 20, 2026, 08:06 UTC

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

  2. investigatingMay 19, 2026, 20:09 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. investigatingMay 19, 2026, 17:08 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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Snyk's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Snyk have incidents?

Snyk reported 17 incidents in the last 90 days, 2 of them major or critical. A typical incident lasted 6h 27m. See Snyk's uptime and incident history

Snyk incident on May 19, 2026: Scan and Recurring Test Degradation · APIStatus.watch