Snyk: Snyk Code Degradation
Affected components: Snyk CodeSNYK-EU-01 (app.eu.snyk.io) - Snyk CodeSnyk CodeSNYK-US-02 (app.us.snyk.io) - Snyk Code
Timeline of updates
- resolved
Between 12:03 and 12:04 UTC today (1st June 2026), Snyk experienced a brief period of degradation affecting Snyk Code scans and custom Rule Extension tests. This impacted scans run via the CLI, IDE plugins, CLI uploads, as well as PR Checks.
Services have now fully recovered. Please retry any scans or tests that failed during this window.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-17 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
c740ab34f6290973…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Snyk, started 2026-06-01 14:17 UTC, resolved after 0 min, 1 update(s).
- Title
- Snyk Code Degradation
- Vendor
- Snyk
- Date
- URL
- https://rewindex.com/company/snyk/incidents/xhxp90qk3506
Snyk profileRecent Snyk incidentsAll outages on June 1, 2026Snyk in June 2026MarkdownJSON