- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us
What to do
Check whether you use Snyk in us. 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 2d 20h it lasted.
Anything that failed between 2026-10-17 01:43 UTC and 2026-10-19 22:02 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 5
- investigating
Snyk Engineers are investigating an issue affecting Snyk Code performance including scans and PR checks in the SNYK-US-02 environment. The Snyk Incident Response has been enacted.
provider
- investigating
We are continuing to investigate this issue.
provider
- investigating
We are continuing to investigate this issue.
provider
- monitoring
A fix has been successfully deployed and all systems are now operating as expected. Our team will continue to monitor the environment to ensure stability.
provider
- resolved
All services remain stable during our monitoring period. The Snyk Incident Response has been stood down.
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-8fc9af41ac
Is Snyk still down?
No, this incident was resolved 2026-10-19 22:02 UTC. For Snyk's live state, see https://down.guide/snyk.
How long did it last?
2d 20h, from 2026-10-17 01:43 UTC to 2026-10-19 22:02 UTC, by the times Snyk posted.
What was affected?
Snyk named in us.
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.