- Level
- confirmed
- Worst impact
- Degraded
- Components
- Snyk Code, Snyk Container, Snyk IaC, Snyk Open Source
- Down Index
- 25of 100
What to do
Check whether you use Snyk Snyk Code, Snyk Container, Snyk IaC, Snyk Open Source. 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 13d 17h it lasted.
Anything that failed between 2026-04-21 18:58 UTC and 2026-05-05 12:23 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 9
- investigating
We’ve identified a regression impacting our recurring test performance. Specifically, both daily and weekly test suites are showing increased latency. Users affected by this degradation may see some tests failing intermittently or, in some cases, failing to execute entirely. Our engineers are currently investigating the root cause, and a fix is being prioritized. We will provide another update once the stabilization patch is deployed.
provider
- investigating
Our investigations remain ongoing. However, we are still observing degradation affecting our daily and weekly recurring tests. We will continue to keep you updated with our progress.
provider
- investigating
We have identified the root cause of the degraded performance affecting recurring tests and are working towards a fix. Customers will continue to experience delays and, in some cases, failures of their scheduled recurring tests. We will continue to keep you updated with our progress.
provider
- investigating
We are continuing our mitigation efforts. However, customers will continue to experience delays and, in some cases, failures of their scheduled recurring tests. Further updates will follow.
provider
- monitoring
We are no longer observing delays affecting Recurring Tests. Monitoring is now underway to ensure there are no further delays during today's schedule.
provider
- identified
We have observed further degradation and are investigating. Customers may observe a small percentage of Recurring Tests not executing as scheduled.
provider
- identified
We are continuing to observe the degradation affecting our Recurring Tests, and our investigations remain ongoing. Some customers may notice that a small percentage of their Recurring Tests are not executing as scheduled.
provider
- identified
Our investigation into the degradation affecting Recurring Tests is ongoing. Some customers may continue to notice that a small percentage of their Recurring Tests are not executing as scheduled.
provider
- resolved
We are no longer observing degradation affecting Recurring Tests. The Snyk Incident Response has now 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-5e30ad6217
Is Snyk still down?
No, this incident was resolved 2026-05-05 12:23 UTC. For Snyk's live state, see https://down.guide/snyk.
How long did it last?
13d 17h, from 2026-04-21 18:58 UTC to 2026-05-05 12:23 UTC, by the times Snyk posted.
What was affected?
Snyk named Snyk Code, Snyk Container, Snyk IaC, Snyk Open Source.
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.