Looking for an update now? Check the current status, or follow Snyk for future changes.
70.2%of 57 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
80%
30
6
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 23Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
We've deployed a fix and are now monitoring closely to confirm full resolution.
investigating
We've identified an increase in impact. Some Secrets PR checks are still showing as failed, despite the underlying scan completing successfully. We're continuing to investigate and will share more as soon as we have it.
investigating
Our Engineers are investigating degradation affecting Snyk Open Source, across our <a href="https://app.snyk.io/">app.snyk.io</a> environment.
Customers may see CLI errors on Secrets and dependency graph scans.
The Snyk Incident Response has been invoked.
A fix has been successfully deployed, resolving the issue. All systems are operating as expected, and our team continues to monitor the environment to ensure stability.
identified
The fix has been deployed, and Snyk Code tests are completing. We are currently processing the remaining backlog.
identified
Snyk Engineers have identified the root cause and are deploying a fix to production. We will update when the fix is fully deployed.
identified
Snyk engineers are investigating an issue affecting Snyk Code flows and Snyk Secrets in the Multi-Tenant US-01 environment. The Snyk Incident Response has been enacted.
We're continuing to monitor today's scheduled Recurring Tests closely to ensure there are no further delays.
We'll share another update once we can confirm all tests have completed successfully.
identified
Our Engineers are investigating degradation which is impacting Recurring Tests.
Customers may observe that daily Recurring Tests have not executed as scheduled for yesterday's (17th September) run. We expect these tests to be executed during today's schedule. Weekly recurring tests are scheduled as expected.
The Snyk Incident Response has been invoked.
Snyk CodeSnyk CodeSnyk CodeSnyk CodeSnyk CodeSnyk Open SourceSnyk Open SourceSnyk Open SourceSnyk Open SourceSnyk Open Source
identified
Snyk engineers have identified the root cause of the issue and are now deploying a mitigation across all affected environments.
investigating
Our investigations remain ongoing.
We will keep you updated with our progress.
investigating
We're currently investigating reports of degradation affecting some Imports and PR Checks across the Snyk platform.
Full impact analysis is currently underway, we will provide further details as the incident progresses.
The Snyk Incident Response has been invoked.
Snyk AppRiskSnyk AppRiskSnyk AppRiskSnyk CodeSnyk CodeSnyk CodeSnyk ContainerSnyk ContainerSnyk ContainerSnyk IaCSnyk IaCSnyk IaCSnyk Open SourceSnyk Open SourceSnyk Open Source
monitoring
The fix is deployed across all environments. We're continuing to monitor for any further stability issues.
monitoring
A fix has been applied, and error rates connecting to our broker servers have dropped back to normal levels. Connections via brokered integrations are functioning as expected. We are continuing to monitor performance to ensure full stability.
Snyk AppRiskSnyk CodeSnyk ContainerSnyk IaCSnyk Open Source
investigating
Our engineering team has detected an issue impacting customers using brokered integrations. Some customers are currently reporting errors when attempting to connect to our broker servers.
At this time, only a subset of customers is affected. We are actively measuring the impact of this service degradation and investigating the root cause. We will provide another update as soon as we have more information.
Legacy Incident Archive
54 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
July 2026
Snyk Partial Test Degradation
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Snyk Engineers have implemented a fix and we are currently monitoring the outcomes.
We will provide updates as they become available.
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.
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.
June 2026
Degraded Peformance Affecting SNYK-US-01
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Snyk engineers have identified the issue and deployed a mitigation to restore service. The team is now actively monitoring the environment to ensure continued stability.
investigating
Our engineering team is investigating reports of degraded performance in the SNYK-US-01 US Multi-tenant environment (app.snyk.io), affecting multiple services. We are actively working to isolate the cause and will provide updates as we the investigation progresses.
Degraded Performance SNYK-US-01
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are continuing our monitoring throughout today to ensure services remain stable.
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.
identified
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...
identified
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.
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.
Third-Party Vendor Security Incident (Klue)
minorSource not attested
Last archived state: resolved
View archived record details
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...
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-sal...
Snyk Code (SAST) Scan service degraded
minorSource not attested
Last archived state: resolved
View archived record details
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.
Degredation affecting app.snyk.io
Source not attested
Last archived state: resolved
View archived record details
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.
Data Freshness delay in Issues API for customers on app.snyk.io
minorSource not attested
Last archived state: resolved
View archived record details
investigating
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.
investigating
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.
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.
Degradation Affecting app.snyk.io
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented, and initial signs are positive.
We will continue to monitor to ensure services fully recover and remain stable.
investigating
Our engineers are investigating degradation affecting app.snyk.io.
Customers may experience continuous loading and/or slowness when accessing the Snyk UI. This may also impact the testing of projects.
The Snyk Incident Response has been invoked.
Email-to-Case Temporarily Disabled
minorSource not attested
Last archived state: resolved
View archived record details
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.
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!
Snyk Recurring Test Email Notification
Source not attested
Last archived state: resolved
View archived record details
monitoring
We are observing delays affecting some Daily Recurring Tests as a result of our mitigation actions.
monitoring
During our recent Recurring Tests, we observed that some email notifications were not sent to alert customers to new vulnerabilities.
All Recurring Tests have completed successfully, and customers can view their results within the Snyk UI.
We have now implemented a fix. Email notifications will resume with the next scheduled run.
