Skip to main content
Menu
Snyk

Incident

Intermittent failures for Go-based projects

Maintenance Lasted 14h 16m · started · Snyk's page

DWN-3110bb9496

Level
confirmed
Worst impact
Maintenance
Components
Snyk Open Source

Summary

Snyk says Go-based projects had intermittent failures in all flows except the CLI. A fix was applied for elevated PR check errors on Go modules projects, success rates are back to normal, and Snyk is monitoring.

Written by anthropic/claude-haiku-5.5 from Snyk's own updates.

What to do

  • Check whether you use Snyk Snyk Open Source. Check your stack

    Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.
  • Check that everything you run on Snyk came back after the window closed 2026-11-12 10:50 UTC.

  • Subscribe to Snyk's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=snyk works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Snyk 3

  1. investigating

    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.

    provider

  2. monitoring

    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.

    provider

  3. resolved

    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.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-3110bb9496

Is this Snyk maintenance still going on?

No, it ended 2026-11-12 10:50 UTC.

How long did it last?

14h 16m, from 2026-11-11 20:34 UTC to 2026-11-12 10:50 UTC, by the times Snyk posted.

What was affected?

Snyk named Snyk Open Source.

What caused it?

Snyk hasn't published a root cause. If it does, it shows here.

Where does this come from?

Snyk's official status page, https://status.snyk.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.