Incidentsby GlyphImports and PR Checks Degraded
Sep 9, 14:37 UTCSep 9, 17:02 UTC
Duration
2h 25m
Impact
Minor
Root cause
Not disclosed
Snyk, 90 days
24 incidents
Affected
Snyk CodeSnyk Open SourceSNYK-US-01 (app.snyk.io) - Snyk CodeSNYK-US-01 (app.snyk.io) - Snyk Open SourceSNYK-US-02 (app.us.snyk.io) - Snyk CodeSNYK-US-02 (app.us.snyk.io) - Snyk Open SourceSNYK-EU-01 (app.eu.snyk.io) - Snyk CodeSNYK-EU-01 (app.eu.snyk.io) - Snyk Open SourceSNYK-AU-01 (app.au.snyk.io) - Snyk CodeSNYK-AU-01 (app.au.snyk.io) - Snyk Open SourceSNYK-GOV-01 (app.snykgov.io) - Snyk CodeSNYK-GOV-01 (app.snykgov.io) - Snyk Open Source
Final update
Snyk engineers have deployed the mitigation to all environments, which has resolved the Invalid Credentials errors for customers using the GitHub Cloud integration. No further errors observed during the monitoring period. The incident has been stood down.
Timeline
- Resolved · Sep 9, 17:02 UTC
Snyk engineers have deployed the mitigation to all environments, which has resolved the Invalid Credentials errors for customers using the GitHub Cloud integration. No further errors observed during the monitoring period. The incident has been stood down.
- Identified · Sep 9, 15:47 UTC
Snyk engineers have identified the root cause of the issue and are now deploying a mitigation across all affected environments.
- Investigating · Sep 9, 15:29 UTC
Our investigations remain ongoing. We will keep you updated with our progress.
- Investigating · Sep 9, 14:37 UTC
We're currently investigating reports of degradation affecting some Imports and PR Checks across the Snyk platform. Full impact analysis is currently underway, we will provide further details as the incident progresses. The Snyk Incident Response has been invoked.