Minor impactResolvedDevOps

Snyk incident: Intermittent failures for Go-based projects

Snyk reported this minor-impact incident on its official status page on Nov 11, 2026, 20:34 UTC. It was resolved after 14h 16m.

Right now Snyk is operational. Live Snyk status →

🔔 Get alerted when Snyk has issuesFree · email alerts · no credit card
Nov 11, 2026, 20:34 UTC
started
Nov 12, 2026, 10:50 UTC
resolved
14h 16m
duration
Minor
impact

Affected components

  • Snyk Open Source
  1. resolvedNov 12, 2026, 10:50 UTC

    PR checks for projects using Go modules are working as expected, and success rates have remained stable throughout the monitoring period. The Snyk Incident Response has been stood down.

  2. monitoringNov 11, 2026, 21:37 UTC

    We’ve applied a fix for the elevated error rate in PR checks for projects using Go modules, and success rates are back to normal. If a PR check failed earlier today, re-running it or pushing a new commit should now succeed. We’re continuing to monitor and will post an update once the incident is resolved.

  3. investigatingNov 11, 2026, 20:34 UTC

    Snyk engineers are investigating an issue with intermittent failures for Go-based projects for all flows except the CLI flow. The Snyk Incident response has been enacted.

What APIStatus.watch saw

  • Nov 11, 2026, 20:36 UTCoperational → degraded
  • Nov 12, 2026, 10:51 UTCdegraded → operational

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Snyk have incidents?

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