Störungsverlauf von Snyk

1. 30. August 2026 um 14:32 UTCmonitoring

   Ein Fix wurde angewendet, und die Fehlerraten bei der Verbindung zu unseren Broker-Servern sind auf ein normales Niveau zurückgegangen. Verbindungen über vermittelte Integrationen funktionieren wie erwartet. Wir überwachen weiterhin die Leistung, um volle Stabilität zu gewährleisten.

2. 31. August 2026 um 15:02 UTCmonitoring

   Der Fix wird in allen Umgebungen eingesetzt. Wir beobachten weiterhin weitere Stabilitätsprobleme.

3. 2. September 2026 um 06:42 UTCresolved

   Während des gesamten Überwachungszeitraums wurden keine weiteren Auswirkungen beobachtet. Die Snyk Incident Response wurde abgelehnt.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 30. August 2026 um 12:20 UTCinvestigating

   Unser Engineering-Team hat ein Problem erkannt, das Kunden mithilfe von vermittelten Integrationen betrifft. Einige Kunden melden derzeit Fehler, wenn sie versuchen, sich mit unseren Broker-Servern zu verbinden. Zu diesem Zeitpunkt ist nur eine Teilmenge der Kunden betroffen. Wir messen aktiv die Auswirkungen dieser Service-Degradation und untersuchen die Ursache. Wir werden ein weiteres Update bereitstellen, sobald wir weitere Informationen haben.

2. 30. August 2026 um 13:31 UTCresolved

   Ein Fix wurde angewendet, und die Fehlerraten bei der Verbindung zu unseren Broker-Servern sind auf ein normales Niveau zurückgegangen. Verbindungen über vermittelte Integrationen funktionieren wie erwartet. Wir überwachen weiterhin die Leistung, um volle Stabilität zu gewährleisten.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 20. August 2026 um 12:42 UTCinvestigating

   Unsere Ingenieure identifizierten eine Verschlechterung, die Snyk Code beeinflusste. Kunden haben möglicherweise Fehler beim CLI-Test zwischen 08:55 UTC und 11:20 UTC beobachtet.

2. 20. August 2026 um 12:43 UTCresolved

   Das Problem wurde gemildert und der Service wurde wiederhergestellt.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 19. August 2026 um 18:30 UTCinvestigating

   Snyk Engineers untersuchen ein Problem, das Kunden betrifft, die die GitHub Cloud App installieren.

2. 19. August 2026 um 18:56 UTCidentified

   Snyk Engineers haben die Ursache identifiziert und arbeiten an einer Minderung.

3. 19. August 2026 um 19:35 UTCresolved

   Snyk-Ingenieure haben einen Fix bereitgestellt und bestätigt, dass die Installation der GitHub Cloud App wie erwartet funktioniert. Der Vorfall ist nun gelöst.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 17. August 2026 um 15:01 UTCidentified

   Snyk erlebt derzeit erhöhte Fehlerquoten (bis zu 20%) aufgrund eines anhaltenden Vorfalls mit GitHub durch Dritte. Funktionen, die von der GitHub-Integration abhängig sind, sind betroffen. Wir beobachten die Situation aktiv und werden Updates bereitstellen, wenn GitHub das Problem löst.

2. 17. August 2026 um 19:42 UTCresolved

   Snyk Ingenieure haben Service Recovery bestätigt. Der Vorfall ist nun gelöst.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 11. August 2026 um 14:54 UTCidentified

   Snyk engineers have identified an issue affecting SAST Push tests in the Snyk-US-01 Multi-tenant environment. The root cause has been identified, and mitigation efforts are underway.

2. 11. August 2026 um 16:05 UTCidentified

   Snyk Engineers are deploying a fix for the SAST Test Failures. Currently, Snyk Code (SAST) results are not updating in the UI. Projects are displaying issue counts and findings from their previous test rather than the latest scan. New scan results are being captured, and no data has been lost; affected projects will display current results once the fix is deployed and the next successful test completes.

3. 11. August 2026 um 18:52 UTCmonitoring

   Snyk engineers have deployed a fix, and all services have been restored. We are monitoring the environment to ensure stability.

4. 11. August 2026 um 21:55 UTCresolved

   All systems remain stable during the monitoring period after the mitigation was implemented. The incident response has been stood down.

1. 5. August 2026 um 19:26 UTCinvestigating

   Snyk engineers are observing increased latency affecting Test Services in the SNYK-US-01 environment. Our Incident Response process has been enacted. Our engineers are investigating the issue. Thank you.

2. 5. August 2026 um 20:51 UTCinvestigating

   Snyk engineers remain engaged under an incident footing. Our engineers are implementing mitigation measures to mitigate the impact. Further updates to follow.

3. 5. August 2026 um 22:54 UTCmonitoring

   Snyk engineers have implemented a mitigation. Test latency has returned to normal ranges. Our engineers are monitoring the environment.

4. 7. August 2026 um 07:29 UTCresolved

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

1. 5. August 2026 um 04:28 UTCinvestigating

   We are investigating degraded performance on the snyk Vuln DB page, security.snyk.io Currently, the /vuln page is working, but some individual vulnerability reports are returning 502 responses. Testing and Reporting is not affected.

2. 5. August 2026 um 04:57 UTCmonitoring

   We have implemented a fix. Service has returned to normal levels. We are monitoring for stability

3. 5. August 2026 um 05:34 UTCinvestigating

   Monitoring has shown that the fix was only temporarily successful and the issue has recurred. We are continuing to investigate.

4. 5. August 2026 um 10:00 UTCinvestigating

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

5. 5. August 2026 um 12:51 UTCmonitoring

   A fix has been deployed to production, and we're closely monitoring the system.

6. 5. August 2026 um 13:35 UTCresolved

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

1. 4. August 2026 um 13:07 UTCinvestigating

   We've identified an issue affecting all .NET project workflows, including import, retest, and pull request checks. The Snyk Incident Response has been invoked, and our engineering team are investigating.

2. 4. August 2026 um 13:44 UTCidentified

   Our engineering team have identified the root cause and are working on deploying a fix. We will keep you updated on our progress.

3. 4. August 2026 um 14:29 UTCresolved

   Our engineers have deployed a fix and, after a brief monitoring period, have confirmed all services have recovered. The Snyk Incident Response has been stood down.

1. 23. Juli 2026 um 19:59 UTCinvestigating

   Wir erleben derzeit einen teilweisen Abbau für einige Tests in allen Produktlinien. Wir werden Updates bereitstellen, sobald sie verfügbar sind.

2. 23. Juli 2026 um 20:59 UTCmonitoring

   Das System hat sich erholt und Snyk Engineers überwacht derzeit die Plattform.

3. 24. Juli 2026 um 10:34 UTCresolved

   Während unseres Überwachungszeitraums wurden keine weiteren Fehler beobachtet. Die Snyk Incident Response wurde nun abgelehnt.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 23. Juli 2026 um 14:56 UTCresolved

   Wir hatten eine kurze Wiederholung des gestrigen Vorfalls, der die Kunden in zwei kurzen Fenstern betraf: 14:27–14:36 UTC 14:37-14:42 UTC Der Service hat sich nun erholt. Kunden sollten alle Importe, die während dieser Fenster fehlerhaft oder fehlgeschlagen sind, erneut importieren.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 22. Juli 2026 um 09:41 UTCmonitoring

   Von 09:08 bis 09:30 UTC-Kunden können Fehler bei der Ausführung von Importen für Snyk Open Source oder Snyk Container aufgetreten sein. Darüber hinaus haben einige Kunden möglicherweise Probleme beim Versuch, Projektdetails für diese Projekttypen anzuzeigen. Die Antwort auf Snyk Incident wurde aktiviert und Korrekturmaßnahmen haben den Betrieb wieder normalisiert. Das Team beobachtet die Situation weiterhin.

2. 23. Juli 2026 um 07:09 UTCresolved

   Während unseres Überwachungszeitraums wurden keine weiteren Auswirkungen beobachtet. Kunden sollten alle Importe, die während des Ausfallfensters fehlerhaft oder fehlgeschlagen sind, erneut importieren. Die Snyk Incident Response wurde abgelehnt.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 14. Juli 2026 um 18:18 UTCidentified

   Wir haben ein Problem identifiziert, das Workspaces Services und Code PR-Prüfungen innerhalb der SNYK-EU-01 Multi-Tenant-Umgebung betrifft. Bitte beachten Sie, dass Open Source- und Lizenzfunktionen nicht betroffen sind und voll funktionsfähig bleiben. Unser Engineering-Team arbeitet aktiv an einer Lösung.

2. 14. Juli 2026 um 18:58 UTCmonitoring

   Unsere Ingenieure haben die Ursache identifiziert und eine Minderung eingesetzt, die die Dienste in den vollen Betriebszustand zurückführt. Wir werden die Umwelt weiterhin überwachen, um Stabilität zu gewährleisten.

3. 14. Juli 2026 um 20:12 UTCresolved

   Alle Dienste bleiben stabil. Der Vorfall ist nun gelöst.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 14. Juli 2026 um 17:56 UTCidentified

   Wir sind uns der intermittierenden Ausfälle bewusst, die eine Teilmenge von öffentlich zugänglichen API-Routen betreffen. Unser Team hat das Problem identifiziert und setzt aktiv eine Minderung ein. Wir werden ein Update bereitstellen, sobald das Problem behoben ist.

2. 14. Juli 2026 um 20:14 UTCresolved

   Ein Fix wurde bereitgestellt und alle Systeme funktionieren normal. Dieser Vorfall wurde als gelöst markiert.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 10. Juli 2026 um 13:41 UTCinvestigating

   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. 10. Juli 2026 um 15:45 UTCidentified

   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. 10. Juli 2026 um 19:14 UTCmonitoring

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

4. 10. Juli 2026 um 20:08 UTCresolved

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

1. 24. Juni 2026 um 21:39 UTCinvestigating

   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. 24. Juni 2026 um 22:14 UTCmonitoring

   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. 25. Juni 2026 um 12:14 UTCmonitoring

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

4. 25. Juni 2026 um 12:14 UTCresolved

   This incident has been resolved.

1. 22. Juni 2026 um 22:21 UTCidentified

   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. 22. Juni 2026 um 23:06 UTCidentified

   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. 23. Juni 2026 um 00:52 UTCidentified

   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. 23. Juni 2026 um 02:34 UTCmonitoring

   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. 23. Juni 2026 um 10:53 UTCmonitoring

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

6. 24. Juni 2026 um 21:34 UTCresolved

   This incident has been resolved.

1. 19. Juni 2026 um 23:15 UTCinvestigating

   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. 22. Juni 2026 um 22:12 UTCmonitoring

   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.

3. 8. Juli 2026 um 15:26 UTCresolved

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

1. 19. Juni 2026 um 20:13 UTCinvestigating

   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. 19. Juni 2026 um 22:13 UTCresolved

   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.

1. 17. Juni 2026 um 23:31 UTCmonitoring

   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. 18. Juni 2026 um 10:59 UTCresolved

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