Minor impactResolvedDevOps

Snyk incident: Snyk Code Performance Degraded in SNYK-US-02

Snyk reported this minor-impact incident on its official status page on Oct 17, 2026, 01:43 UTC. It was resolved after 2d 20h.

Right now Snyk is operational. Live Snyk status →

🔔 Get alerted when Snyk has issuesFree · email alerts · no credit card
Oct 17, 2026, 01:43 UTC
started
Oct 19, 2026, 22:02 UTC
resolved
2d 20h
duration
Minor
impact

Affected components

  • SNYK-US-01 (app.snyk.io) - Snyk Code
  • SNYK-US-02 (app.us.snyk.io) - Snyk Code
  1. resolvedOct 19, 2026, 22:02 UTC

    All services remain stable during our monitoring period. The Snyk Incident Response has been stood down.

  2. monitoringOct 17, 2026, 02:30 UTC

    A fix has been successfully deployed and all systems are now operating as expected. Our team will continue to monitor the environment to ensure stability.

  3. investigatingOct 17, 2026, 02:06 UTC

    We are continuing to investigate this issue.

  4. investigatingOct 17, 2026, 02:05 UTC

    We are continuing to investigate this issue.

  5. investigatingOct 17, 2026, 01:43 UTC

    Snyk Engineers are investigating an issue affecting Snyk Code performance including scans and PR checks in the SNYK-US-02 environment. The Snyk Incident Response has been enacted.

What APIStatus.watch saw

  • Oct 17, 2026, 01:45 UTCoperational → degraded
  • Oct 17, 2026, 02:40 UTCdegraded → operational

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Snyk have incidents?

Snyk reported 21 incidents in the last 90 days, 1 of them major or critical. A typical incident lasted 9h 7m. See Snyk's uptime and incident history