Live / Snyk / Incident
Snyk: Intermittent failures for Go-based projects
Snyk · snyk.ioMinor incidentResolved2026-11-12 10:50 UTC
Public — what happened
Summary
Snyk said it began investigating on November 11, 2026 at 20:34 UTC after Go-based projects were failing intermittently in every flow except the command-line tool. About an hour later, at 21:37 UTC, the company said it had applied a fix for the higher error rate in pull request checks for Go module projects, and that success rates had returned to normal. Snyk advised that anyone whose check failed earlier could re-run it or push a new commit, and the incident was marked resolved on November 12 at 10:50 after a period of monitoring.
Affected
Snyk Open Source
Timeline
- Started — 2026-11-11 20:34 UTC
- Investigating — 2026-11-11 20:34 UTC
- Monitoring — 2026-11-11 21:37 UTC
- Resolved — 2026-11-12 10:50 UTC · 14h 16m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Snyk against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Snyk: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Snyk report →
More from Snyk
Covered in The Squid’s Ink, Week 47, 2026, our weekly internet health report.