Update - We are continuing our monitoring throughout today to ensure services remain stable.
Jun 23, 2026 - 10:53 UTC
Monitoring - Mitigation steps have been completed and are showing immediate improvements in success rate and latency, and are burning down the backlog. We will maintain a period of monitoring for continued stability.
Jun 23, 2026 - 02:34 UTC
Update - Snyk Engineering is continuing to investigate the issue. Mitigation steps are progressing but will take some time to be fully effective.
Current scope of effect:

* Customers may notice increased latency across the Snyk UI platform, as well as API, CLI, SCM based projects and PR Checks. 
* Due to the increased latency, some tests may be observed to timeout and fail.
* There is currently no known observed impact to analytics and reporting.
This issue is not affecting other environments.
We will continue to work on mitigation efforts and provide updates as the issue progresses.

Jun 23, 2026 - 00:52 UTC
Update - Snyk engineers are continuing their investigation. We have applied initial mitigation steps and are seeing signs of recovery, though some performance degradation persists. Our teams remain focused on a full resolution, and we will share another update shortly.
Jun 22, 2026 - 23:06 UTC
Identified - Our engineering team is currently investigating reports of degraded performance in the SNYK-US-01 US Multi-tenant environment (app.snyk.io). We are actively working to isolate the cause and will provide updates as we the investigation progresses.
Jun 22, 2026 - 22:21 UTC
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.

Jun 22, 2026 - 22:12 UTC
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.

Jun 19, 2026 - 23:15 UTC
SNYK-US-01 (app.snyk.io) Operational
Snyk AppRisk Operational
Snyk Code Operational
Snyk Container Operational
Snyk IaC Operational
Snyk Open Source Operational
Snyk Learn Operational
Evo by Snyk Operational
Snyk API & Web Operational
SNYK-US-02 (app.us.snyk.io) Operational
Snyk AppRisk Operational
Snyk Code Operational
Snyk Container Operational
Snyk IaC Operational
Snyk Open Source Operational
Snyk Learn Operational
Evo by Snyk Operational
Snyk API & Web Operational
SNYK-EU-01 (app.eu.snyk.io) Operational
Snyk AppRisk Operational
Snyk Code Operational
Snyk Container Operational
Snyk IaC Operational
Snyk Open Source Operational
Snyk Learn Operational
Evo by Snyk Operational
Snyk API & Web Operational
SNYK-AU-01 (app.au.snyk.io) Operational
Snyk AppRisk Operational
Snyk Code Operational
Snyk Container Operational
Snyk IaC Operational
Snyk Open Source Operational
Snyk Learn Operational
Evo by Snyk Operational
Snyk API & Web Operational
SNYK-GOV-01 (app.snykgov.io) Operational
Snyk Code Operational
Snyk Container Operational
Snyk IaC Operational
Snyk Open Source Operational
Snyk Support (support.snyk.io) Operational
Support Portal Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Jun 24, 2026

No incidents reported today.

Jun 23, 2026

Unresolved incidents: Degraded Performance SNYK-US-01, Third-Party Vendor Security Incident (Klue).

Jun 22, 2026
Resolved - Both the Issues API data freshness and reporting data freshness have been fully restored and are operating normally.

Our investigation is now complete, and the Snyk Incident Response has been stood down.

We apologise for any inconvenience this may have caused and thank you for your patience throughout.

Jun 22, 10:12 UTC
Update - We are no longer observing delays affecting our reporting data freshness.

However, the Issues API data freshness remains delayed, and our investigation into this is ongoing.

We will provide a further update as soon as we have more information.

Jun 18, 15:00 UTC
Update - Snyk Engineering has identified a data freshness delay within Issues Reporting. Our teams are actively investigating the root cause, and we will provide further updates as the situation progresses.
Jun 16, 18:21 UTC
Investigating - Engineering have detected a delay in data affecting Issue API results on the app.snyk.io environment.
Project data, UI based Reporting, and Export API are not affected.
We are investigating and will report back here with any updates.

Jun 16, 04:52 UTC
Jun 21, 2026

No incidents reported.

Jun 20, 2026

No incidents reported.

Jun 19, 2026
Resolved - The issue affecting SAST scans and API-driven automated tests has been successfully resolved, and all services have returned to normal status. Our engineering team identified the root cause as an expensive SQL query that triggered database degradation. The query has been mitigated, and performance has stabilized.

Thank you for your patience while we worked through this.

Jun 19, 22:13 UTC
Investigating - We are currently experiencing an unexpected issue affecting our SAST scans and certain API triggered tests. Our engineering team is actively monitoring the situation to fully understand the impact and isolate the root cause. While we work to restore full functionality, some users may experience intermittent or immediate failures in their running scans and automated test suites.

We will provide updates as they become available.

Jun 19, 20:13 UTC
Jun 18, 2026
Resolved - No further issues have been observed during our monitoring period.

The Snyk Incident Response has been stood down.

Jun 18, 10:59 UTC
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.

Jun 17, 23:31 UTC
Jun 17, 2026
Jun 16, 2026
Jun 15, 2026

No incidents reported.

Jun 14, 2026

No incidents reported.

Jun 13, 2026

No incidents reported.

Jun 12, 2026

No incidents reported.

Jun 11, 2026

No incidents reported.

Jun 10, 2026
Resolved - Services have remained unaffected during our monitoring period.

The Snyk Incident Response has been stood down.

Jun 10, 06:22 UTC
Monitoring - We have re-enabled the email-to-case feature, allowing customers to create and reply to cases via email.

Monitoring is now underway to ensure the services remains stable.

Jun 9, 14:13 UTC
Identified - Please note that the ability to create or reply to cases via email has been temporarily turned off.
If you need to log a new issue or update an existing case, please do so directly through the ticketing portal. We will let you know as soon as email functionality is restored. Thank you for your patience!

Jun 8, 15:47 UTC