Istoricul incidentelor Snyk

1. 9 septembrie 2026 la 14:37 UTCinvestigating

   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.

2. 9 septembrie 2026 la 15:29 UTCinvestigating

   Our investigations remain ongoing. We will keep you updated with our progress.

3. 9 septembrie 2026 la 15:47 UTCidentified

   Snyk engineers have identified the root cause of the issue and are now deploying a mitigation across all affected environments.

4. 9 septembrie 2026 la 17:02 UTCresolved

   Snyk engineers have deployed the mitigation to all environments, which has resolved the Invalid Credentials errors for customers using the GitHub Cloud integration. No further errors observed during the monitoring period. The incident has been stood down.

1. 30 august 2026 la 14:32 UTCmonitoring

   A fost aplicat un fix, iar ratele de eroare conectate la serverele noastre broker au scăzut înapoi la niveluri normale. Conexiunile prin intermediul integrării intermediate funcționează conform așteptărilor. Continuăm să monitorizăm performanța pentru a asigura stabilitatea deplină.

2. 31 august 2026 la 15:02 UTCmonitoring

   Fixarea este desfăşurată în toate mediile. Continuăm să monitorizăm orice alte probleme de stabilitate.

3. 2 septembrie 2026 la 06:42 UTCresolved

   Nu s-a observat niciun impact suplimentar pe parcursul perioadei de monitorizare. Răspunsul la incidentul cu Snyk a fost respins.

Traducere automată din actualizarea oficială a incidentului.

1. 30 august 2026 la 12:20 UTCinvestigating

   Echipa noastră de inginerie a detectat o problemă care afectează clienţii folosind integrarea intermediată. Unii clienți raportează în prezent erori atunci când încearcă să se conecteze la serverele noastre broker. În acest moment, doar un subset de clienți este afectat. Măsurăm în mod activ impactul degradării acestui serviciu şi investigăm cauza principală. Vom oferi o altă actualizare de îndată ce vom avea mai multe informații.

2. 30 august 2026 la 13:31 UTCresolved

   A fost aplicat un fix, iar ratele de eroare conectate la serverele noastre broker au scăzut înapoi la niveluri normale. Conexiunile prin intermediul integrării intermediate funcționează conform așteptărilor. Continuăm să monitorizăm performanța pentru a asigura stabilitatea deplină.

Traducere automată din actualizarea oficială a incidentului.

1. 20 august 2026 la 12:42 UTCinvestigating

   Inginerii noştri au identificat o degradare care a afectat Codul Snyk. Este posibil ca clienţii să fi observat erori la testarea CLI între 08:55 UTC şi 11:20 UTC.

2. 20 august 2026 la 12:43 UTCresolved

   Problema a fost atenuată, iar serviciul a fost restabilit.

Traducere automată din actualizarea oficială a incidentului.

1. 19 august 2026 la 18:30 UTCinvestigating

   Inginerii Snyk investighează o problemă care afectează clienții care instalează aplicația GitHub Cloud. Clienții care au deja aplicația instalată nu sunt afectate.

2. 19 august 2026 la 18:56 UTCidentified

   Inginerii Snyk au identificat cauza principală și lucrează la o atenuare.

3. 19 august 2026 la 19:35 UTCresolved

   Inginerii Snyk au implementat un fix și au confirmat instalarea GitHub Cloud App funcționează conform așteptărilor. Incidentul este acum rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 17 august 2026 la 15:01 UTCidentified

   Snyk se confruntă în prezent cu rate ridicate de eroare (până la 20%) din cauza unui incident în curs de desfășurare cu GitHub. Caracteristicile dependente de integrarea GitHub sunt afectate. Suntem monitorizarea activă a situației și va oferi actualizări, deoarece GitHub rezolvă problema.

2. 17 august 2026 la 19:42 UTCresolved

   Inginerii Snyk au confirmat recuperarea serviciului. Incidentul este acum rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 11 august 2026 la 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 la 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 la 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 la 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 la 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 la 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 la 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 la 07:29 UTCresolved

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

1. 5 august 2026 la 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 la 04:57 UTCmonitoring

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

3. 5 august 2026 la 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 la 10:00 UTCinvestigating

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

5. 5 august 2026 la 12:51 UTCmonitoring

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

6. 5 august 2026 la 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 la 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 la 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 la 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 iulie 2026 la 19:59 UTCinvestigating

   În prezent ne confruntăm cu degradare parţială pentru unele teste în toate liniile de produse. Vom furniza actualizări pe măsură ce acestea devin disponibile.

2. 23 iulie 2026 la 20:59 UTCmonitoring

   Sistemul s-a recuperat şi inginerii Snyk monitorizează în prezent platforma.

3. 24 iulie 2026 la 10:34 UTCresolved

   Nu au fost observate alte erori în timpul perioadei noastre de monitorizare. Răspunsul la incidentul Snyk a fost acum oprit.

Traducere automată din actualizarea oficială a incidentului.

1. 23 iulie 2026 la 14:56 UTCresolved

   Am avut o scurtă recidivă a incidentului de ieri, afectând clienţii în două ferestre scurte: 14:27:14:36 UTC 14:37 Serviciul şi-a revenit. Clienții ar trebui să reimporte orice import care a eșuat sau a eșuat în timpul acestor ferestre.

Traducere automată din actualizarea oficială a incidentului.

1. 22 iulie 2026 la 09:41 UTCmonitoring

   De la 09:08 la 09:30 Clienții UTC pot avea erori în executarea importurilor pentru Snyk Open Source sau Snyk Container. În plus, este posibil ca unii clienți să fi avut probleme atunci când au încercat să vizualizeze detaliile proiectului pentru aceste tipuri de proiecte. Răspunsul incidentului Snyk a fost activat şi acţiunile corective au revenit la normal. Echipa continuă să monitorizeze situaţia.

2. 23 iulie 2026 la 07:09 UTCresolved

   Nu a mai fost observat niciun impact în timpul perioadei noastre de monitorizare. Clienții ar trebui să reimporte orice import care a eșuat sau a eșuat în timpul perioadei de întrerupere. Răspunsul la incidentul cu Snyk a fost respins.

Traducere automată din actualizarea oficială a incidentului.

1. 14 iulie 2026 la 18:18 UTCidentified

   Am identificat o problemă care afectează serviciile de spațiu de lucru și controalele PR de cod în mediul multi-tenant SNYK-UE-01. Vă rugăm să rețineți că caracteristicile Open Source și Licence nu sunt afectate și rămân pe deplin operaționale. Echipa noastră de ingineri lucrează activ la o rezoluţie.

2. 14 iulie 2026 la 18:58 UTCmonitoring

   Inginerii noştri au identificat cauza principală şi au implementat o atenuare, revenind serviciile la statutul complet operaţional. Vom continua să monitorizăm mediul pentru a asigura stabilitatea.

3. 14 iulie 2026 la 20:12 UTCresolved

   Toate serviciile rămân stabile. Incidentul este acum rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 14 iulie 2026 la 17:56 UTCidentified

   Suntem conştienţi de eşecuri intermitente care afectează un subset de rute API orientate spre public. Echipa noastră a identificat problema şi desfăşoară activ o atenuare. Vom oferi o actualizare odată ce problema este rezolvată.

2. 14 iulie 2026 la 20:14 UTCresolved

   A fost implementat un fix şi toate sistemele funcţionează normal. Acest incident a fost marcat ca rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 10 iulie 2026 la 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 iulie 2026 la 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 iulie 2026 la 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 iulie 2026 la 20:08 UTCresolved

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

1. 24 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 12:14 UTCmonitoring

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

4. 25 iunie 2026 la 12:14 UTCresolved

   This incident has been resolved.

1. 22 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 10:53 UTCmonitoring

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

6. 24 iunie 2026 la 21:34 UTCresolved

   This incident has been resolved.

1. 19 iunie 2026 la 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 iunie 2026 la 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 iulie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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.