Live / Snyk / Incident
Snyk: PR Check Invalid Credential Error
Snyk · snyk.ioMinor incidentResolved2026-10-20 19:31 UTC
Public — what happened
Summary
Snyk said it began investigating at 16:33 UTC on 2026-10-20 after reports of "Invalid Credential" errors that blocked Snyk Code pull request checks in all environments. The company later said recurring tests could be delayed and other features relying on its Workspaces Service might be affected, with impact seemingly limited to GitHub and GitHub Enterprise workspaces. Snyk said it identified the root cause at 17:53 UTC and deployed a fix to all environments by 18:22 UTC, after which it said services were back to normal while it kept monitoring. The incident was marked resolved at 19:31 UTC.
Affected
Snyk Code, Snyk Code, Snyk Code, Snyk Code, Snyk Code
Timeline
- Started — 2026-10-20 16:33 UTC
- Investigating — 2026-10-20 16:33 UTC (2 updates)
- Identified — 2026-10-20 17:53 UTC
- Monitoring — 2026-10-20 18:22 UTC
- Resolved — 2026-10-20 19:31 UTC · 2h 58m 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 44, 2026, our weekly internet health report.