- Level
- confirmed
- Worst impact
- Degraded
- Components
- Snyk AppRisk, Snyk AppRisk, Snyk AppRisk, Snyk AppRisk, Snyk Code, Support Portal, Snyk Code, Snyk Code, Snyk Code, Snyk Code, Snyk Container, Snyk Container, Snyk Container, Snyk Container, Snyk Container, Snyk IaC, Snyk IaC, Snyk IaC, Snyk IaC, Snyk IaC, Snyk Open Source, Snyk Open Source, Snyk Open Source, Snyk Open Source, Snyk Open Source, Snyk Learn, Snyk Learn, Snyk Learn, Snyk Learn, Evo by Snyk, Evo by Snyk, Evo by Snyk, Evo by Snyk
- Down Index
- 40of 100
What to do
Check whether you use Snyk Snyk AppRisk, Snyk AppRisk, Snyk AppRisk, Snyk AppRisk and 29 more. 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 18d 16h it lasted.
Anything that failed between 2026-06-19 23:15 UTC and 2026-07-08 15:26 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 3
- investigating
We were notified of a security incident involving Klue, a market intelligence platform used by Snyk and a wide range of companies for competitive intelligence. An unauthorized party accessed data from Snyk's Salesforce environment through Klue's integration. Other security vendors, such as Recorded Future (https://www.recordedfuture.com/blog/klue-security-incident), Tanium (https://www.tanium.com/blog/security-update-taniums-response-to-the-klue-breach-that-allowed-data-exfiltration-from-salesforce/), Huntress (https://www.huntress.com/blog/klue-breach-investigation), and Jamf (https://www.jamf.com/blog/klue-incident/) have been impacted and have shared updates publicly. Our investigation shows that, to our knowledge at this point in time, the impact was primarily limited to business data fields within the Salesforce environments. This includes customer business contact information and only the title and description from a limited subset of customer support cases. The body or contents of the support cases were not included nor did it affect Snyk's products. There was no impact on our ability to serve our customers. Snyk's platform, services, and infrastructure remain fully operational and were not involved. Upon notification from Klue, we promptly disabled the Klue integration in Salesforce and began our own review. We will post updates here as we learn more.
provider
- monitoring
We were notified of a security incident involving Klue, a market intelligence platform used by Snyk and a wide range of companies for competitive intelligence. An unauthorized party accessed data from Snyk's Salesforce environment through Klue's integration. Other security vendors, such as Recorded Future, Tanium, Huntress, and Jamf have been impacted and have shared updates publicly. Our investigation shows that, to our knowledge at this point in time, the impact was primarily limited to business data fields within the Salesforce environments. This includes customer business contact information and only the title and description from a limited subset of customer support cases. The body or contents of the support cases were not included nor did it affect Snyk's products. There was no impact on our ability to serve our customers. Snyk's platform, services, and infrastructure remain fully operational and were not involved. Upon notification from Klue, we promptly disabled the Klue integration in Salesforce and began our own review. We will post updates here as we learn more.
provider
- resolved
Our forensic investigation into the June 2026 Klue/Salesforce incident, conducted in partnership with Mandiant, is now complete. The investigation confirmed that the impact was limited to business CRM data. No evidence of impact to the Snyk platform, and any sensitive data within, was found. All impacted customers were notified directly and the data involved is consistent with what was disclosed in our June 22 blog post (https://snyk.io/blog/when-a-vendors-breach-becomes-yours-lessons-from-the-klue-incident/).
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-020bae8402
Is Snyk still down?
No, this incident was resolved 2026-07-08 15:26 UTC. For Snyk's live state, see https://down.guide/snyk.
How long did it last?
18d 16h, from 2026-06-19 23:15 UTC to 2026-07-08 15:26 UTC, by the times Snyk posted.
What was affected?
Snyk named Snyk AppRisk, Snyk AppRisk, Snyk AppRisk, Snyk AppRisk and 29 more.
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.