Snyk Outage History

Started Jul 10, 2026, 01:41 PM UTC· resolved Jul 10, 2026, 08:08 PM UTC

1. investigating Jul 10, 2026, 01:41 PM UTC

   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.

2. identified Jul 10, 2026, 03:45 PM UTC

   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.

3. monitoring Jul 10, 2026, 07:14 PM UTC

   Snyk Engineers have implemented a fix and we are currently monitoring the outcomes. We will provide updates as they become available.

4. resolved Jul 10, 2026, 08:08 PM UTC

   The incident has been resolved after we have monitored the overall performance.

Read the full incident report →

Started Jun 24, 2026, 09:39 PM UTC· resolved Jun 25, 2026, 12:14 PM UTC

1. investigating Jun 24, 2026, 09:39 PM UTC

   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.

2. monitoring Jun 24, 2026, 10:14 PM UTC

   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.

3. monitoring Jun 25, 2026, 12:14 PM UTC

   No further issues were observed during our monitoring period. The Snyk Incident Response has been stood down.

4. resolved Jun 25, 2026, 12:14 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 22, 2026, 10:21 PM UTC· resolved Jun 24, 2026, 09:34 PM UTC

1. identified Jun 22, 2026, 10:21 PM UTC

   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.

2. identified Jun 22, 2026, 11:06 PM UTC

   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.

3. identified Jun 23, 2026, 12:52 AM UTC

   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.

4. monitoring Jun 23, 2026, 02:34 AM UTC

   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.

5. monitoring Jun 23, 2026, 10:53 AM UTC

   We are continuing our monitoring throughout today to ensure services remain stable.

6. resolved Jun 24, 2026, 09:34 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 19, 2026, 11:15 PM UTC· resolved Jul 08, 2026, 03:26 PM UTC

1. investigating Jun 19, 2026, 11:15 PM UTC

   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.

2. monitoring Jun 22, 2026, 10:12 PM UTC

   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. Currently, based on the actions we have taken to date and the advice of our third-party experts, we do not believe that impacted data will be made public or further misused. 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.

3. resolved Jul 08, 2026, 03:26 PM UTC

   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/).

Read the full incident report →

Started Jun 19, 2026, 08:13 PM UTC· resolved Jun 19, 2026, 10:13 PM UTC

1. investigating Jun 19, 2026, 08:13 PM UTC

   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.

2. resolved Jun 19, 2026, 10:13 PM UTC

   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.

Read the full incident report →

Started Jun 17, 2026, 11:31 PM UTC· resolved Jun 18, 2026, 10:59 AM UTC

1. monitoring Jun 17, 2026, 11:31 PM UTC

   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.

2. resolved Jun 18, 2026, 10:59 AM UTC

   No further issues have been observed during our monitoring period. The Snyk Incident Response has been stood down.

Read the full incident report →

Started Jun 16, 2026, 04:52 AM UTC· resolved Jun 22, 2026, 10:12 AM UTC

1. investigating Jun 16, 2026, 04:52 AM UTC

   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.

2. investigating Jun 16, 2026, 06:21 PM UTC

   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.

3. investigating Jun 18, 2026, 03:00 PM UTC

   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.

4. resolved Jun 22, 2026, 10:12 AM UTC

   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.

Read the full incident report →

Started Jun 09, 2026, 11:22 AM UTC· resolved Jun 09, 2026, 02:14 PM UTC

1. investigating Jun 09, 2026, 11:22 AM UTC

   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.

2. monitoring Jun 09, 2026, 12:15 PM UTC

   A fix has been implemented, and initial signs are positive. We will continue to monitor to ensure services fully recover and remain stable.

3. resolved Jun 09, 2026, 02:14 PM UTC

   No further issues have been observed during our monitoring period. The Snyk Incident Response has been stood down.

Read the full incident report →

Started Jun 08, 2026, 03:47 PM UTC· resolved Jun 10, 2026, 06:22 AM UTC

1. identified Jun 08, 2026, 03:47 PM UTC

   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!

2. monitoring Jun 09, 2026, 02:13 PM UTC

   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.

3. resolved Jun 10, 2026, 06:22 AM UTC

   Services have remained unaffected during our monitoring period. The Snyk Incident Response has been stood down.

Read the full incident report →

Started Jun 02, 2026, 09:37 AM UTC· resolved Jun 04, 2026, 06:39 AM UTC

1. monitoring Jun 02, 2026, 09:37 AM UTC

   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.

2. monitoring Jun 02, 2026, 12:47 PM UTC

   We are observing delays affecting some Daily Recurring Tests as a result of our mitigation actions.

3. resolved Jun 04, 2026, 06:39 AM UTC

   We are no longer observing delays affecting Recurring Tests. All tests have caught up, and services are operating normally. The Snyk Incident Response has now been stood down.

Read the full incident report →

Started May 23, 2026, 08:43 AM UTC· resolved May 23, 2026, 07:46 PM UTC

1. investigating May 23, 2026, 08:43 AM UTC

   We are currently investigating reports of intermittent failures affecting our GitHub Cloud App integration, specifically impacting repository scans, project imports, and Pull Request status checks. During this time, customers may see failures on PR checks, recurring tests and imports. Because the issue is intermittent, manually re-running a scan or retrying an import may succeed. Our engineering team is actively analyzing system logs to pinpoint the root cause, and we will provide regular updates until full stability is restored

2. resolved May 23, 2026, 07:46 PM UTC

   The intermittent issues affecting repository scans, project imports, and Pull Request status checks have been fully resolved. The root cause was an upstream degradation with GitHub Cloud app installation token authentication, which has now been mitigated on the GitHub side (ref: GitHub Incident k5z4d1v1tqmt). If you continue to experience issues with your PRs, imports, or repository scans, please reach out to our support team for further assistance.

Read the full incident report →

Started May 22, 2026, 05:26 PM UTC· resolved May 22, 2026, 07:14 PM UTC

1. identified May 22, 2026, 05:26 PM UTC

   Snyk engineers have identified the root cause of degraded performance affecting Open Source across all environments, leading to PR Checks and recurring test failures. A fix is currently being rolled out globally. We will provide further updates as the deployment progresses.

2. resolved May 22, 2026, 07:14 PM UTC

   Snyk engineers have rolled out a fix across all environments. Our engineers will continue to monitor the situation. The Snyk Incident Response has been stood down.

Read the full incident report →

Started May 22, 2026, 02:29 AM UTC· resolved May 26, 2026, 01:20 PM UTC

1. identified May 22, 2026, 02:29 AM UTC

   Snyk Engineers have identified degraded Open Source scanning performance for Gradle projects in the US-01 (app.snyk.io) and AU-01 (app.au.snyk.io) environments. The affect services include Repo Imports, Recurring tests, Manual Retests, and PR Checks. The investigation is ongoing under the Snyk Incident Response process.

2. identified May 22, 2026, 02:52 PM UTC

   Our Engineers have confirmed that the US-01 (app.snyk.io) environment has shown no further degradation following re-deployment and appears to be stable. Investigation into the AU-01 (app.au.snyk.io) environment is still ongoing, and we will provide a further update as we progress.

3. monitoring May 25, 2026, 11:26 PM UTC

   Our Engineers have implemented a fix, and we're no longer observing the degradation on the AU-01 (app.au.snyk.io) environment. We will continue to monitor for ongoing stability.

4. resolved May 26, 2026, 01:20 PM UTC

   We have observed no further impact on services during our monitoring period. The Snyk Incident Response has now been stood down.

Read the full incident report →

Started May 21, 2026, 11:37 AM UTC· resolved May 21, 2026, 05:16 PM UTC

1. investigating May 21, 2026, 11:37 AM UTC

   We're currently investigating degradation affecting our app.snyk.io environment. Customers may experience slowness and/or failures affecting project imports and recurring tests. The Snyk Incident Response has been invoked.

2. identified May 21, 2026, 12:22 PM UTC

   Success rates have now recovered. However, the environment remains under close monitoring while our investigation into the root cause and further mitigations continues. We will keep you updated as we progress.

3. identified May 21, 2026, 02:56 PM UTC

   A fix has been deployed, and initial signs are positive. We will continue to monitor service to ensure services remain stable.

4. resolved May 21, 2026, 05:16 PM UTC

   All services remain stable after the mitigation. The Snyk Incident Response has been stood down.

Read the full incident report →

Started May 19, 2026, 05:08 PM UTC· resolved May 20, 2026, 08:06 AM UTC

1. investigating May 19, 2026, 05:08 PM UTC

   Snyk engineers are currently tracking Code Scan and Open Source Reachability scan failures—including Recurring Tests—within the Multi-tenant Snyk-US-01 environment. Our incident response team has been activated, and we are actively working to resolve the issue.

2. investigating May 19, 2026, 08:09 PM UTC

   We have successfully mitigated the issue impacting Open Source Reachability Scans and are actively monitoring the environment to ensure continued stability. Meanwhile, our engineering team is continuing to investigate the performance degradation affecting Code Scans. We will provide further updates as they become available.

3. resolved May 20, 2026, 08:06 AM UTC

   We observed no further impact during our monitoring period. The Snyk Incident Response has now been stood down.

Read the full incident report →

Started May 19, 2026, 02:19 PM UTC· resolved May 20, 2026, 10:51 AM UTC

1. investigating May 19, 2026, 02:19 PM UTC

   We're currently investigating an issue affecting Jira integrations. Users will be unable to manage Jira integrations, view associated Jira tickets on Snyk issues, or create new Jira tickets through the platform. Jira Cloud integrations are unaffected. The Snyk Incident Response has been invoked.

2. identified May 19, 2026, 03:35 PM UTC

   Snyk engineers have identified the root cause of the Jira integration issue and are actively developing a fix.

3. monitoring May 19, 2026, 07:47 PM UTC

   A fix has been deployed to production, and we are monitoring the impacted Jira integration workflows to confirm the issue is fully resolved.

4. resolved May 20, 2026, 10:51 AM UTC

   We are no longer observing any impact affecting Jira integration workflows. The Snyk Incident Response has been stood down.

Read the full incident report →

Started May 19, 2026, 05:29 AM UTC· resolved May 20, 2026, 02:57 PM UTC

1. investigating May 19, 2026, 05:29 AM UTC

   Snyk is currently investigating a potential supply chain compromise. Current scope appears to be: over 630 malicious package versions across more than 315 unique packages, with AntV suite heavily impacted As an active investigation, this is subject to change. We are currently working on confirming the known scope and providing vulnerability advice, reporting, blog and trust centre updates Please subscribe to this incident for further updates as they become available. Links to additional resources will be provided here.

2. investigating May 19, 2026, 07:55 AM UTC

   Update: Snyk is continuing to investigate and respond to the ongoing supply chain compromise of @antv and other packages. Affected packages: Current findings indicate that multiple npm packages have been identified as affected, including packages within the @antv/* namespace and related packages outside the AntV namespace. Scope: Over 639 malicious package versions across more than 323 unique packages, with numbers subject to change Cause: Investigations indicate the issue was caused by a compromised npm maintainer account, enabling automated malicious package publishing. Immediate action you can take: -Review dependency trees and lockfiles for affected packages, including packages within the @antv/* namespace and additional impacted npm packages size-sensor, echarts-for-react, timeago.js., canvas-nest.js -Pin to pre-May 19 versions, run npm install --ignore-scripts, rotate all credentials. We will update here as soon as we have additional information or links

3. investigating May 19, 2026, 08:45 AM UTC

   The Snyk Trust Center has been updated.

4. investigating May 19, 2026, 08:51 AM UTC

   Customers can now assess potential impact in the Snyk app by visiting: Analytics → Reports → Zero-Day → Active Security Incident Assessment for Antv Supply Chain Compromise - May 2026 Please continue to refer to the Snyk Trust Center for the latest official updates and customer communications.

5. investigating May 19, 2026, 09:13 AM UTC

   Our blog post is now available: Mini Shai-Hulud Hits AntV

6. investigating May 19, 2026, 10:44 AM UTC

   The Compromised Packages list is now available at https://security.snyk.io/antv-supply-chain-compromise-may-2026

7. investigating May 19, 2026, 09:39 PM UTC

   We are continuing to investigate this issue.

8. resolved May 20, 2026, 02:57 PM UTC

   Customer Projects: This Status Page incident, “Supply Chain Compromise on AntV,” was opened to share customer-facing updates regarding a third-party compromise within the AntV ecosystem. Because AntV is a Snyk-supported ecosystem, we used this incident to alert customers that they may have projects using the affected package versions. Snyk Systems: Snyk’s security team has reviewed Snyk's systems, and there is no indication of compromise to Snyk systems, products, or infrastructure. As this issue does not impact the availability or operation of Snyk services, we are resolving this Status Page incident. Going forward, customer-facing updates, affected package information, and remediation guidance for this issue will be provided through the Snyk Trust Center and related security resources. Snyk will continue to monitor for additional related advisories and update customer-facing resources as needed.

Read the full incident report →

Started May 18, 2026, 12:12 PM UTC· resolved May 19, 2026, 02:27 PM UTC

1. investigating May 18, 2026, 12:12 PM UTC

   Snyk Engineers have identified degraded performance in the Multi-Tenant US-01 environment (app.snyk.io), affecting multiple services. The investigation is ongoing under the Snyk Incident Response process.

2. investigating May 18, 2026, 02:57 PM UTC

   Our investigations into the root cause remain ongoing. We will keep you updated with our progress.

3. investigating May 19, 2026, 11:22 AM UTC

   Our investigation into the root cause remains ongoing. We are currently seeing a reduced frequency of the issue and are continuing to monitor performance closely. Further updates will be provided as our investigation progresses.

4. resolved May 19, 2026, 02:27 PM UTC

   We have identified and deployed a fix restoring normal service. The Snyk Incident Response has been stood down.

Read the full incident report →

Started May 18, 2026, 11:19 AM UTC· resolved May 18, 2026, 12:53 PM UTC

1. investigating May 18, 2026, 11:19 AM UTC

   We're currently investigating intermittent degradation affecting PR events. This is affecting GitHub, GitLab, Bitbucket Cloud and Bitbucket Server integrations. The Snyk Incident Response has been invoked.

2. resolved May 18, 2026, 12:53 PM UTC

   Following our investigation, we have determined that this issue is related to an existing incident. We are consolidating updates to centralise communication and will close this status page. For progress and resolution details, please follow: Service Degradation on US-01 (app.snyk.io).

Read the full incident report →

Started May 13, 2026, 02:49 PM UTC· resolved May 13, 2026, 07:01 PM UTC

1. investigating May 13, 2026, 02:49 PM UTC

   Snyk engineers are investigating degraded performance with the Reporting PDF in the Snyk-US-01 multi-tenant environment. Customers may observe longer generation times or failures to generate reports.

2. resolved May 13, 2026, 07:01 PM UTC

   Snyk engineers have successfully deployed a mitigation to address the reporting issues. PDF reports are now generating as expected. We have concluded the incident response.

Read the full incident report →

Started May 11, 2026, 02:35 PM UTC· resolved May 11, 2026, 02:41 PM UTC

1. identified May 11, 2026, 02:35 PM UTC

   We are currently experiencing degraded performance with our GitHub integrations due to an ongoing, broader service disruption on GitHub’s end. Our team is actively monitoring the situation and will automatically restore full connectivity as soon as the upstream issue is resolved.

2. resolved May 11, 2026, 02:41 PM UTC

   The upstream issues at GitHub have been resolved. Our engineering team has verified full recovery, and all Snyk GitHub integrations are operating normally. The Snyk Incident Response has been stood down.

Read the full incident report →

Started May 08, 2026, 07:09 PM UTC· resolved May 08, 2026, 09:51 PM UTC

1. monitoring May 08, 2026, 07:09 PM UTC

   Snyk engineers are currently investigating degraded performance in Multi-Tenant Snyk US-01. Customers may experience failures with the CLI Monitor. Our engineers have implemented a mitigation strategy and have observed an increase in the CLI Monitor's success rate. We are actively monitoring the environment.

2. resolved May 08, 2026, 09:51 PM UTC

   CLI Monitor performance is stable. Post-mitigation monitoring is complete, and the incident response has concluded.

Read the full incident report →

Started May 06, 2026, 08:45 PM UTC· resolved May 07, 2026, 08:30 AM UTC

1. identified May 06, 2026, 08:45 PM UTC

   Snyk engineers have identified latency affecting a small subset of customers. Affected customers may observe a delay in Issues API data freshness. Our engineers are investigating the issue. Impact is limited to the Multi-Tenant Snyk-US-01 environment.

2. resolved May 07, 2026, 08:30 AM UTC

   Our Engineers deployed a fix, and we're no longer observing delays affecting the Issues API data freshness. The Snyk Incident Response has been stood down.

Read the full incident report →

Started May 06, 2026, 03:32 PM UTC· resolved May 12, 2026, 07:20 AM UTC

1. investigating May 06, 2026, 03:32 PM UTC

   Snyk engineers have noticed delays in a small percentage of daily recurring tests in the Multi-Tenant Synk-US-01 (app.snyk.io) environment. The impact is limited to daily tests; weekly tests remain unaffected. Snyk engineers are investigating the issue.

2. investigating May 07, 2026, 01:19 PM UTC

   We are continuing to investigate the root cause of the delays. Customers may still experience delays affecting a small percentage of daily recurring tests.

3. identified May 08, 2026, 01:02 PM UTC

   We have identified the root cause of the delays and implemented mitigations. Some customers may still experience delayed daily recurring tests while these changes fully propagate We will continue to monitor the situation to ensure the mitigations have been successful.

4. identified May 11, 2026, 02:19 PM UTC

   We continue to see improvements as a result of the mitigation actions taken. However, we will monitor to ensure services fully recover.

5. resolved May 12, 2026, 07:20 AM UTC

   We are no longer observing delays affecting our Recurring Tests as a result of the mitigation actions taken. The Snyk Incident Response has now been stood down.

Read the full incident report →

Started Apr 29, 2026, 03:43 PM UTC· resolved Apr 29, 2026, 08:00 PM UTC

1. investigating Apr 29, 2026, 03:43 PM UTC

   Our Engineers are investigating the degradation affecting PDF Export of Reports. The Snyk Incident Response has been invoked. We will keep you updated with our progress.

2. monitoring Apr 29, 2026, 05:25 PM UTC

   Our Engineering team has implemented a fix and we are currently monitoring the behavior in the platform.

3. resolved Apr 29, 2026, 08:00 PM UTC

   We've observed no further issues during our monitoring period. The Snyk Incident Response has been stood down.

Read the full incident report →