Minor impactResolvedDevOps

Snyk incident: PR Checks and Imports Degraded in SNYK-US-01

Snyk reported this minor-impact incident on its official status page on Oct 15, 2026, 20:39 UTC. It was resolved after 1h 7m.

Right now Snyk is degraded. Live Snyk status →

🔔 Get alerted when Snyk has issuesFree · email alerts · no credit card
Oct 15, 2026, 20:39 UTC
started
Oct 15, 2026, 21:47 UTC
resolved
1h 7m
duration
Minor
impact

Affected components

  • Snyk API & Web
  • Snyk Code
  • Snyk Container
  • Snyk IaC
  • Snyk Open Source
  • Snyk Secrets
  1. resolvedOct 15, 2026, 21:47 UTC

    All services remain operational during the monitoring period. The Snyk Incident response has been stood down.

  2. monitoringOct 15, 2026, 21:09 UTC

    The import backlog has been processed. Services are operating within normal ranges. Snyk engineers continue to monitor the environment.

  3. monitoringOct 15, 2026, 21:04 UTC

    Snyk engineers have deployed a mitigation, and PR checks are currently operating within normal parameters. The backlog of imports is being actively processed, and we are closely monitoring both the queue and the overall health of the environment.

  4. identifiedOct 15, 2026, 20:39 UTC

    Snyk engineers are investigating degraded performance affecting PR Checks and Imports in the multi-tenant SNYK-US-01 environment. The incident response protocol has been activated. The issue has been identified, and mitigation steps are currently underway.

What APIStatus.watch saw

  • Oct 15, 2026, 20:44 UTCoperational → degraded
  • Oct 15, 2026, 21:14 UTCdegraded → operational

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Snyk have incidents?

Snyk reported 22 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