Historial de interrupciones de Snyk

1. 9 de septiembre de 2026 a las 14:37 UTCinvestigating

   Actualmente estamos investigando informes de degradación que afectan a algunas importaciones y cheques de PR en la plataforma Snyk. Actualmente se está llevando a cabo un análisis completo de los efectos, proporcionaremos más detalles a medida que avance el incidente. The Snyk Incident Response has been invoked.

2. 9 de septiembre de 2026 a las 15:29 UTCinvestigating

   Nuestras investigaciones siguen en curso. Lo mantendremos actualizado con nuestro progreso.

3. 9 de septiembre de 2026 a las 15:47 UTCidentified

   Los ingenieros de Snyk han identificado la causa raíz de la cuestión y ahora están implementando una mitigación en todos los entornos afectados.

4. 9 de septiembre de 2026 a las 17:02 UTCresolved

   Los ingenieros de Snyk han desplegado la mitigación a todos los entornos, lo que ha resuelto los errores de Credenciales Inválidos para los clientes utilizando la integración de GitHub Cloud. No se observaron más errores durante el período de vigilancia. El incidente ha sido derribado.

Traducido automáticamente desde la actualización oficial del incidente.

1. 30 de agosto de 2026 a las 14:32 UTCmonitoring

   Se ha aplicado una solución, y las tasas de error que se conectan a nuestros servidores de corredores han retrocedido a niveles normales. Las conexiones a través de las integraciones intermediadas funcionan como se espera. Seguimos monitoreando el desempeño para garantizar la plena estabilidad.

2. 31 de agosto de 2026 a las 15:02 UTCmonitoring

   La solución se implementa en todos los entornos. Continuamos monitoreando para cualquier problema de estabilidad.

3. 2 de septiembre de 2026 a las 6:42 UTCresolved

   Durante el período de vigilancia no se han observado más efectos. The Snyk Incident Response has been stood down.

Traducido automáticamente desde la actualización oficial del incidente.

1. 30 de agosto de 2026 a las 12:20 UTCinvestigating

   Nuestro equipo de ingeniería ha detectado un problema que afecta a los clientes utilizando integraciones intermediadas. Algunos clientes están reportando errores al intentar conectarse a nuestros servidores de corredores. En este momento, sólo un subconjunto de clientes se ve afectado. Estamos midiendo activamente el impacto de esta degradación del servicio e investigando la causa raíz. Proporcionaremos otra actualización tan pronto como tengamos más información.

2. 30 de agosto de 2026 a las 13:31 UTCresolved

   Se ha aplicado una solución, y las tasas de error que se conectan a nuestros servidores de corredores han retrocedido a niveles normales. Las conexiones a través de las integraciones intermediadas funcionan como se espera. Seguimos monitoreando el desempeño para garantizar la plena estabilidad.

Traducido automáticamente desde la actualización oficial del incidente.

1. 20 de agosto de 2026 a las 12:42 UTCinvestigating

   Nuestros ingenieros identificaron una degradación que afectó al Código Snyk. Los clientes pueden haber observado errores con pruebas CLI entre 08:55 UTC y 11:20 UTC.

2. 20 de agosto de 2026 a las 12:43 UTCresolved

   La cuestión ha sido mitigada y se ha restablecido el servicio.

Traducido automáticamente desde la actualización oficial del incidente.

1. 19 de agosto de 2026 a las 18:30 UTCinvestigating

   Los ingenieros de Snyk están investigando un problema que afecta a los clientes que están instalando la aplicación GitHub Cloud. Los clientes que ya tienen la aplicación instalada no son impactados.

2. 19 de agosto de 2026 a las 18:56 UTCidentified

   Snyk Engineers han identificado la causa raíz y están trabajando en una mitigación.

3. 19 de agosto de 2026 a las 19:35 UTCresolved

   Los ingenieros de Snyk han implementado una solución y han confirmado que la instalación de GitHub Cloud App funciona como se espera. El incidente ya está resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 17 de agosto de 2026 a las 15:01 UTCidentified

   Snyk está experimentando tasas de error elevadas (hasta un 20%) debido a un incidente de terceros en curso con GitHub. Las características que dependen de la integración GitHub son afectadas. Estamos monitoreando activamente la situación y proporcionaremos actualizaciones mientras GitHub resuelve el problema.

2. 17 de agosto de 2026 a las 19:42 UTCresolved

   Los ingenieros de Snyk han confirmado la recuperación del servicio. El incidente ya está resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 11 de agosto de 2026 a las 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 de agosto de 2026 a las 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 de agosto de 2026 a las 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 de agosto de 2026 a las 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 de agosto de 2026 a las 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 de agosto de 2026 a las 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 de agosto de 2026 a las 22:54 UTCmonitoring

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

4. 7 de agosto de 2026 a las 7:29 UTCresolved

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

1. 5 de agosto de 2026 a las 4:28 UTCinvestigating

   Estamos investigando el rendimiento degradado en la página de snyk Vuln DB, seguridad.snyk.io Actualmente, la página /vuln está funcionando, pero algunos informes individuales de vulnerabilidad están volviendo 502 respuestas. La prueba y la presentación de informes no se ve afectada.

2. 5 de agosto de 2026 a las 4:57 UTCmonitoring

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

3. 5 de agosto de 2026 a las 5:34 UTCinvestigating

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

4. 5 de agosto de 2026 a las 10:00 UTCinvestigating

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

5. 5 de agosto de 2026 a las 12:51 UTCmonitoring

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

6. 5 de agosto de 2026 a las 13:35 UTCresolved

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

Traducido automáticamente desde la actualización oficial del incidente.

1. 4 de agosto de 2026 a las 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 de agosto de 2026 a las 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 de agosto de 2026 a las 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 de julio de 2026 a las 19:59 UTCinvestigating

   Actualmente estamos experimentando degradación parcial para algunas pruebas en todas las líneas de productos. Proporcionaremos actualizaciones cuando estén disponibles.

2. 23 de julio de 2026 a las 20:59 UTCmonitoring

   El sistema se ha recuperado y los ingenieros Snyk están monitoreando la plataforma.

3. 24 de julio de 2026 a las 10:34 UTCresolved

   No se han observado más errores durante nuestro período de vigilancia. The Snyk Incident Response has now been stood down.

Traducido automáticamente desde la actualización oficial del incidente.

1. 23 de julio de 2026 a las 14:56 UTCresolved

   Tuvimos una breve repetición del incidente de ayer, afectando a los clientes en dos ventanas cortas: 14:27-14:36 UTC 14:37-14:42 UTC El servicio se ha recuperado. Los clientes deben reimportar cualquier importación que haya errado o fallado durante estas ventanas.

Traducido automáticamente desde la actualización oficial del incidente.

1. 22 de julio de 2026 a las 9:41 UTCmonitoring

   De 09:08 a 09:30 Los clientes de UTC pueden haber experimentado errores al ejecutar importaciones para Snyk Open Source o Snyk Container. Además, algunos clientes pueden haber experimentado problemas al intentar ver detalles del proyecto para estos tipos de proyectos. La respuesta de Snyk Incident fue activada y las acciones correctivas han devuelto las operaciones a la normalidad. El equipo sigue vigilando la situación.

2. 23 de julio de 2026 a las 7:09 UTCresolved

   Durante nuestro período de vigilancia no se observó ningún impacto adicional. Los clientes deben reimportar cualquier importación que haya errado o fallado durante la ventana de salida. The Snyk Incident Response has been stood down.

Traducido automáticamente desde la actualización oficial del incidente.

1. 14 de julio de 2026 a las 18:18 UTCidentified

   Hemos identificado un problema que afecta a los servicios de espacios de trabajo y los cheques de código PR dentro del entorno multi-tenant SNYK-EU-01. Tenga en cuenta que las características de Open Source y License no son afectadas y siguen siendo plenamente operacionales. Nuestro equipo de ingeniería está trabajando activamente en una resolución.

2. 14 de julio de 2026 a las 18:58 UTCmonitoring

   Nuestros ingenieros han identificado la causa raíz y han desplegado una mitigación, devolviendo los servicios al estado de pleno funcionamiento. Seguiremos vigilando el medio ambiente para garantizar la estabilidad.

3. 14 de julio de 2026 a las 20:12 UTCresolved

   Todos los servicios permanecen estables. El incidente ya está resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 14 de julio de 2026 a las 17:56 UTCidentified

   Somos conscientes de los fallos intermitentes que afectan a un subconjunto de rutas de API orientadas al público. Nuestro equipo ha identificado la cuestión y está implementando activamente una mitigación. Proporcionaremos una actualización una vez resuelto el problema.

2. 14 de julio de 2026 a las 20:14 UTCresolved

   Se ha implementado una solución y todos los sistemas funcionan normalmente. Este incidente ha sido marcado como resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 10 de julio de 2026 a las 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 de julio de 2026 a las 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 de julio de 2026 a las 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 de julio de 2026 a las 20:08 UTCresolved

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

1. 24 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 12:14 UTCmonitoring

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

4. 25 de junio de 2026 a las 12:14 UTCresolved

   This incident has been resolved.

1. 22 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 0: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 de junio de 2026 a las 2: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 de junio de 2026 a las 10:53 UTCmonitoring

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

6. 24 de junio de 2026 a las 21:34 UTCresolved

   This incident has been resolved.

1. 19 de junio de 2026 a las 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 de junio de 2026 a las 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 de julio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 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.