- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 23of 100
What to do
Check whether your product depends on Snyk. 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 11h 28m it lasted.
Anything that failed between 2026-06-17 23:31 UTC and 2026-06-18 10:59 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 2
- monitoring
Our engineers are investigating degradation affecting app.snyk.io. This impacts user-initiated events such as imports, manual retests, PR checks, CLI, API endpoints on the app.snyk.io environment. Other environments are unaffected. The Snyk Incident Response has identified and mitigated the issue. We will continue to monitor to ensure services fully recover and remain stable.
provider
- resolved
No further issues have been observed 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-36e619d8a3
Is Snyk still down?
No, this incident was resolved 2026-06-18 10:59 UTC. For Snyk's live state, see https://down.guide/snyk.
How long did it last?
11h 28m, from 2026-06-17 23:31 UTC to 2026-06-18 10:59 UTC, by the times Snyk posted.
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.