Histórico de interrupções do Snyk

1. 30 Eost 2026 da 14:32 UTCmonitoring

   Uma correção foi aplicada, e taxas de erro que se conectam aos nossos servidores corretores caíram de volta aos níveis normais. As conexões via integrações intermediadas estão funcionando como esperado. Continuamos a monitorizar o desempenho para garantir a plena estabilidade.

2. 31 Eost 2026 da 15:02 UTCmonitoring

   A correção é implantada em todos os ambientes. Continuamos a monitorizar quaisquer problemas de estabilidade.

3. 2 Gwengolo 2026 da 06:42 UTCresolved

   Não foi observado qualquer impacto adicional durante todo o período de monitorização. A resposta ao incidente Snyk foi suspensa.

Traduzido automaticamente da atualização oficial do incidente.

1. 30 Eost 2026 da 12:20 UTCinvestigating

   Nossa equipe de engenharia detectou um problema impactando os clientes usando integrações corretas. Alguns clientes estão atualmente relatando erros ao tentar se conectar aos nossos servidores de corretores. Neste momento, apenas um subconjunto de clientes é afetado. Estamos medindo ativamente o impacto da degradação deste serviço e investigando a causa raiz. Forneceremos outra atualização assim que tivermos mais informações.

2. 30 Eost 2026 da 13:31 UTCresolved

   Uma correção foi aplicada, e taxas de erro que se conectam aos nossos servidores corretores caíram de volta aos níveis normais. As conexões via integrações intermediadas estão funcionando como esperado. Continuamos a monitorizar o desempenho para garantir a plena estabilidade.

Traduzido automaticamente da atualização oficial do incidente.

1. 20 Eost 2026 da 12:42 UTCinvestigating

   Os nossos engenheiros identificaram uma degradação que afectou o Código Snyk. Os clientes podem ter observado erros com testes CLI entre 08:55 UTC e 11:20 UTC.

2. 20 Eost 2026 da 12:43 UTCresolved

   A questão foi atenuada e o serviço foi restaurado.

Traduzido automaticamente da atualização oficial do incidente.

1. 19 Eost 2026 da 18:30 UTCinvestigating

   Os engenheiros Snyk estão investigando um problema que afeta os clientes que estão instalando o aplicativo GitHub Cloud. Os clientes que já têm o aplicativo instalado não são afetados.

2. 19 Eost 2026 da 18:56 UTCidentified

   Os engenheiros Snyk identificaram a causa raiz e estão trabalhando em uma mitigação.

3. 19 Eost 2026 da 19:35 UTCresolved

   Os engenheiros Snyk implantaram uma correção e confirmaram que a instalação do GitHub Cloud App está funcionando como esperado. O incidente está agora resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 17 Eost 2026 da 15:01 UTCidentified

   Snyk está atualmente tendo taxas de erro elevadas (até 20%) devido a um incidente de terceiros em curso com o GitHub. Características dependentes da integração do GitHub são afetadas. Estamos monitorando ativamente a situação e forneceremos atualizações enquanto o GitHub resolve o problema.

2. 17 Eost 2026 da 19:42 UTCresolved

   Os engenheiros Snyk confirmaram a recuperação do serviço. O incidente está agora resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 11 Eost 2026 da 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 Eost 2026 da 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 Eost 2026 da 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 Eost 2026 da 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 Eost 2026 da 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 Eost 2026 da 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 Eost 2026 da 22:54 UTCmonitoring

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

4. 7 Eost 2026 da 07:29 UTCresolved

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

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

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

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

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

5. 5 Eost 2026 da 12:51 UTCmonitoring

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

6. 5 Eost 2026 da 13:35 UTCresolved

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

1. 4 Eost 2026 da 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 Eost 2026 da 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 Eost 2026 da 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 Gouere 2026 da 19:59 UTCinvestigating

   Estamos atualmente experimentando degradação parcial para alguns testes em todas as linhas de produtos. Forneceremos atualizações à medida que estiverem disponíveis.

2. 23 Gouere 2026 da 20:59 UTCmonitoring

   O sistema recuperou e os engenheiros Snyk estão atualmente monitorando a plataforma.

3. 24 Gouere 2026 da 10:34 UTCresolved

   Não foram observados mais erros durante o nosso período de monitorização. A Resposta ao Incidente Snyk foi suspensa.

Traduzido automaticamente da atualização oficial do incidente.

1. 23 Gouere 2026 da 14:56 UTCresolved

   Tivemos uma breve recorrência do incidente de ontem, afetando clientes em duas janelas curtas: 14:27-14:36 UTC 14:37-14:42 UTC O serviço já está recuperado. Os clientes devem re-importar quaisquer importações que errou ou falhou durante estas janelas.

Traduzido automaticamente da atualização oficial do incidente.

1. 22 Gouere 2026 da 09:41 UTCmonitoring

   De 09:08 a 09:30 clientes UTC podem ter experimentado erros ao executar as importações para Snyk Open Source ou Snyk Container. Além disso, alguns clientes podem ter experimentado problemas ao tentar visualizar detalhes do projeto para esses tipos de projeto. A resposta do incidente Snyk foi ativada e as ações corretivas retornaram às operações normais. A equipa continua a acompanhar a situação.

2. 23 Gouere 2026 da 07:09 UTCresolved

   Nenhum impacto adicional foi observado durante nosso período de monitoramento. Os clientes devem re-importar quaisquer importações que errou ou falhou durante a janela de saída. A resposta ao incidente Snyk foi suspensa.

Traduzido automaticamente da atualização oficial do incidente.

1. 14 Gouere 2026 da 18:18 UTCidentified

   Identificou-se uma questão que afecta os Serviços de Espaços de Trabalho e os controlos PR de código no ambiente multi-doente SNYK-EU-01. Por favor, note que os recursos de Código Aberto e Licença não são afetados e permanecem totalmente operacionais. Nossa equipe de engenharia está trabalhando ativamente em uma resolução.

2. 14 Gouere 2026 da 18:58 UTCmonitoring

   Nossos engenheiros identificaram a causa raiz e implantaram uma mitigação, retornando os serviços ao status totalmente operacional. Continuaremos a monitorizar o ambiente para garantir a estabilidade.

3. 14 Gouere 2026 da 20:12 UTCresolved

   Todos os serviços permanecem estáveis. O incidente está agora resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 14 Gouere 2026 da 17:56 UTCidentified

   Estamos cientes de falhas intermitentes que afetam um subconjunto de rotas API voltadas para o público. Nossa equipe identificou o problema e está ativamente implementando uma mitigação. Forneceremos uma atualização assim que o problema estiver resolvido.

2. 14 Gouere 2026 da 20:14 UTCresolved

   Uma correção foi implantada, e todos os sistemas estão funcionando normalmente. Este incidente foi marcado como resolvido.

Traduzido automaticamente da atualização oficial do incidente.

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

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

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

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

4. 25 Mezheven 2026 da 12:14 UTCresolved

   This incident has been resolved.

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

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

6. 24 Mezheven 2026 da 21:34 UTCresolved

   This incident has been resolved.

1. 19 Mezheven 2026 da 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 Mezheven 2026 da 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 Gouere 2026 da 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 Mezheven 2026 da 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 Mezheven 2026 da 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 Mezheven 2026 da 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 Mezheven 2026 da 10:59 UTCresolved

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