Minor impactResolvedDevOps

Snyk incident: Snyk Import and Recurring Test Degradation

Snyk reported this minor-impact incident on its official status page on May 21, 2026, 11:37 UTC. It was resolved after 5h 39m.

Right now Snyk is degraded. Live Snyk status →

🔔 Get alerted when Snyk has issuesFree · email alerts · no credit card
May 21, 2026, 11:37 UTC
started
May 21, 2026, 17:16 UTC
resolved
5h 39m
duration
Minor
impact

Affected components

  • Snyk AppRisk
  • Snyk Code
  • Snyk Container
  • Snyk IaC
  • Snyk Open Source
  1. resolvedMay 21, 2026, 17:16 UTC

    All services remain stable after the mitigation. The Snyk Incident Response has been stood down.

  2. identifiedMay 21, 2026, 14:56 UTC

    A fix has been deployed, and initial signs are positive. We will continue to monitor service to ensure services remain stable.

  3. identifiedMay 21, 2026, 12:22 UTC

    Success rates have now recovered. However, the environment remains under close monitoring while our investigation into the root cause and further mitigations continues. We will keep you updated as we progress.

  4. investigatingMay 21, 2026, 11:37 UTC

    We're currently investigating degradation affecting our <a href="https://app.snyk.io/">app.snyk.io</a> environment. Customers may experience slowness and/or failures affecting project imports and recurring tests. The Snyk Incident Response has been invoked.

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 21, 2026: Snyk Import and Recurring Test Degradation · APIStatus.watch