# Snyk: PR Check Invalid Credential Error

> Snyk status incident “PR Check Invalid Credential Error” on 2026-10-20: impact minor (vendor’s label), 3.0 h, 5 update(s). Archived by Rewindex.

Canonical: https://rewindex.com/company/snyk/incidents/056wv8l3cnz2
Last updated: 2026-10-20T19:43:01Z

- Impact (vendor’s label): minor
- Status: resolved · edited after publishing
- Started: 2026-10-20 16:33 UTC · Resolved: 2026-10-20 19:31 UTC · Duration: 3.0 h
- Updates: 5 · Affected components: SNYK-AU-01 (app.au.snyk.io) - Snyk Code, Snyk Code, Snyk Code, SNYK-EU-01 (app.eu.snyk.io) - Snyk Code, Snyk Code, SNYK-US-02 (app.us.snyk.io) - Snyk Code, Snyk Code, SNYK-US-01 (app.snyk.io) - Snyk Code, Snyk Code, SNYK-GOV-01 (app.snykgov.io) - Snyk Code
- [Vendor status page: https://stspg.io/bmgj058stjbk](https://stspg.io/bmgj058stjbk)
- [Company: Snyk](https://rewindex.com/company/snyk.md)

## Timeline of updates

- **investigating** 2026-10-20 16:33 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** 2026-10-20 17:16 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** 2026-10-20 17:53 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** 2026-10-20 18:22 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** 2026-10-20 19:31 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.

## Rewindex changes for this incident

- 2026-10-20 17:23 UTC: [Incident updated: PR Check Invalid Credential Error](https://rewindex.com/change/r36be8d183b5aec.md)
- 2026-10-20 18:03 UTC: [Incident updated: PR Check Invalid Credential Error](https://rewindex.com/change/r582752b2f6baa5.md)
- 2026-10-20 18:23 UTC: [Incident updated: PR Check Invalid Credential Error](https://rewindex.com/change/r3796c643c3732e.md)
- 2026-10-20 19:43 UTC: [Incident updated: PR Check Invalid Credential Error](https://rewindex.com/change/rdaae531f03fa37.md)

## Cite this

Status incident (vendor impact label: minor) posted by Snyk, started 2026-10-20 16:33 UTC, resolved after 3.0 h, 5 update(s); edited after publishing.

- Canonical URL: https://rewindex.com/company/snyk/incidents/056wv8l3cnz2
- Citation: Snyk, “PR Check Invalid Credential Error” (2026-10-20 16:33 UTC). Archived by Rewindex: https://rewindex.com/company/snyk/incidents/056wv8l3cnz2 (CC BY 4.0).
- Markdown link: `[Snyk: PR Check Invalid Credential Error (2026-10-20)](https://rewindex.com/company/snyk/incidents/056wv8l3cnz2)`


---
Canonical: https://rewindex.com/company/snyk/incidents/056wv8l3cnz2 · Markdown: https://rewindex.com/company/snyk/incidents/056wv8l3cnz2.md · JSON: https://rewindex.com/api/v1/companies/snyk/incidents/056wv8l3cnz2 · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-04T13:53:34.610Z