Snyk experienced a minor incident on October 20, 2026 affecting Snyk Code and Snyk Code and 1 more component, lasting 2h 58m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Oct 20, 2026, 04:33 PM UTC
Snyk engineers are investigating reports of "Invalid Credential" errors affecting Snyk Code PR checks across all environments. Our incident response team has been activated, and we are working to resolve the issue as quickly as possible.
- investigating Oct 20, 2026, 05:16 PM UTC
Our engineering team is continuing to investigate the incident. In addition to blocked PR checks, customers may experience delays with recurring tests, and other features utilizing the Workspaces Service may be affected. Current impact appears to be isolated to GitHub and GitHub Enterprise workspaces. We will provide further updates as the investigation progresses.
- identified Oct 20, 2026, 05:53 PM UTC
Our engineering team has identified the root cause of the incident and is preparing a fix. We do not yet have an estimated time for deployment, but we will share updates as soon as they become available.
- monitoring Oct 20, 2026, 06:22 PM UTC
Snyk engineers have deployed a fix across all environments, and all services have returned to normal operation. We will continue monitoring system stability to ensure the issue is fully resolved.
- resolved Oct 20, 2026, 07:31 PM UTC
Post-mitigation monitoring confirms that all Snyk services are operating normally and remain stable. The incident response team has stood down, and this incident is now resolved.