- Level
- confirmed
- Worst impact
- Degraded
- Components
- Snyk Code, Snyk Code
- Down Index
- 9of 100
What to do
Check whether you use Snyk Snyk Code, Snyk Code. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.
Anything that failed between 2026-06-01 14:17 UTC and 2026-06-01 14:17 UTC may need a replay.Subscribe to Snyk's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=snyk works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Snyk 1
- 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.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-92ab43aa64
Is Snyk still down?
No, this incident was resolved 2026-06-01 14:17 UTC. For Snyk's live state, see https://down.guide/snyk.
How long did it last?
0m, from 2026-06-01 14:17 UTC to 2026-06-01 14:17 UTC, by the times Snyk posted.
What was affected?
Snyk named Snyk Code, Snyk Code.
What caused it?
Snyk hasn't published a root cause. If it does, it shows here.
Where does this come from?
Snyk's official status page, https://status.snyk.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.