All Systems Operational

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

Scheduled Maintenance

Planned Maintenance Scheduled for 29th of August 2026 Aug 29, 2026 14:00-17:00 UTC

Maintenance is scheduled to take place between the following times:
Saturday 29th of August from 2:00PM UTC to 5:00PM UTC
07:00 PDT / 10:00 EDT / 15:00 BST / 16:00 CEST / 12:00 AEST (+1)

During this time, you will not be able to access Snyk services. We understand that our availability may be critical to your business operations and we have planned our maintenance activity to minimize disruption.

While we typically follow an established schedule of conducting maintenance on the second Saturday of the month every three months, we are shifting our August maintenance to the 29th. This delay allows us additional preparation time for essential database migrations, which will ultimately help us significantly reduce your downtime during future maintenance windows.

Upcoming maintenance windows:
29th August 2026
14th November 2026
13th February 2027

We will confirm each of these events nearer the time and wherever possible we will provide you with at least 30 days’ advance notice.

We have a support page summarizing what you can expect during the downtime, and to suggest mitigations you could consider. On the day of maintenance, our team will keep you informed of our progress via updates at https://status.snyk.io/. If you have any questions or need any assistance, please don't hesitate to contact our support team.

We appreciate your understanding as we work to improve your experience as a valued customer.
Posted on Jun 26, 2026 - 15:38 UTC
Jul 13, 2026

No incidents reported today.

Jul 12, 2026

No incidents reported.

Jul 11, 2026

No incidents reported.

Jul 10, 2026
Snyk Partial Test Degradation
Resolved - The incident has been resolved after we have monitored the overall performance.
Jul 10, 20:08 UTC
Monitoring - Snyk Engineers have implemented a fix and we are currently monitoring the outcomes.

We will provide updates as they become available.
Jul 10, 19:14 UTC
Identified - Snyk Engineers have identified the issue that was causing the degradation and are currently working on implementing a fix.

We will provide updates as they become available.
Jul 10, 15:45 UTC
Investigating - We are currently experiencing partial degradation for some tests including dep graph with risk score and/or reachability, Secrets, SBOM and SCM SAST.

We will provide updates as they become available.
Jul 10, 13:41 UTC
Jul 9, 2026

No incidents reported.

Jul 8, 2026
Third-Party Vendor Security Incident (Klue)
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/).
Jul 8, 15:26 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, 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, 23:15 UTC
Jul 7, 2026

No incidents reported.

Jul 6, 2026

No incidents reported.

Jul 5, 2026

No incidents reported.

Jul 4, 2026

No incidents reported.

Jul 3, 2026

No incidents reported.

Jul 2, 2026

No incidents reported.

Jul 1, 2026

No incidents reported.

Jun 30, 2026

No incidents reported.

Jun 29, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage