Snyk kesinti geçmişi

1. 30 Ağustos 2026 14:32 UTCmonitoring

   Bir düzeltme uygulandı ve broker sunucularımıza bağlanan hata oranları normal seviyelere geri döndü. brokerli entegrasyonlar yoluyla bağlantılar beklendiği gibi çalışır. Tam istikrarı sağlamak için performans izlemeye devam ediyoruz.

2. 31 Ağustos 2026 15:02 UTCmonitoring

   Düzlem tüm ortamlarda dağıtılır. Daha fazla istikrar sorunu için izlemeye devam ediyoruz.

3. 2 Eylül 2026 06:42 UTCresolved

   İzleme döneminde daha fazla etki gözlemlenmedi. Snyk Olay Yanıtı durdu.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 30 Ağustos 2026 12:20 UTCinvestigating

   Mühendislik ekibimiz, brokerleşmiş entegrasyonları kullanarak müşterilerin etkilendiğini tespit etti. Bazı müşteriler şu anda broker sunucularımıza bağlanmaya çalışırken hataları rapor ediyor. Bu zamanda, sadece müşterilerin alt kümesi etkilenir. Bu hizmet bozulmasının etkisini aktif olarak ölçüyoruz ve kök nedenini araştırıyoruz. Daha fazla bilgimiz olduğu sürece başka bir güncelleme sağlayacağız.

2. 30 Ağustos 2026 13:31 UTCresolved

   Bir düzeltme uygulandı ve broker sunucularımıza bağlanan hata oranları normal seviyelere geri döndü. brokerli entegrasyonlar yoluyla bağlantılar beklendiği gibi çalışır. Tam istikrarı sağlamak için performans izlemeye devam ediyoruz.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 20 Ağustos 2026 12:42 UTCinvestigating

   Mühendislerimiz Snyk Code'u etkileyen bir bozulma tespit etti. Müşteriler 08:55 UTC ve 11:20 UTC arasındaki 97 testi ile hataları gözlemleyebilirler.

2. 20 Ağustos 2026 12:43 UTCresolved

   Sorun azaltıldı ve hizmet restore edildi.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 19 Ağustos 2026 18:30 UTCinvestigating

   Snyk Mühendisleri, GitHub Cloud App'i kuran müşterileri etkileyen bir konu araştırıyorlar. Zaten yüklenen uygulama olan müşteriler etkilenmez.

2. 19 Ağustos 2026 18:56 UTCidentified

   Snyk Mühendisleri kök nedenini belirlediler ve bir mitigation üzerinde çalışıyorlar.

3. 19 Ağustos 2026 19:35 UTCresolved

   Snyk mühendisleri bir düzeltme yaptılar ve GitHub Cloud App kurulumunun beklendiği gibi çalıştığını doğruladılar. Olay şimdi çözüldü.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 17 Ağustos 2026 15:01 UTCidentified

   Snyk şu anda GitHub ile devam eden üçüncü taraf bir olay nedeniyle yüksek hata oranları (% 20'ye kadar) yaşıyor. GitHub entegrasyonuna bağlı özellikler etkilenir. Durumu aktif olarak takip ediyoruz ve GitHub sorunu çözdüğü gibi güncelleştirmeler sağlayacaktır.

2. 17 Ağustos 2026 19:42 UTCresolved

   Snyk mühendisleri hizmet kurtarmasını doğruladı. Olay şimdi çözüldü.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 11 Ağustos 2026 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 Ağustos 2026 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 Ağustos 2026 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 Ağustos 2026 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 Ağustos 2026 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 Ağustos 2026 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 Ağustos 2026 22:54 UTCmonitoring

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

4. 7 Ağustos 2026 07:29 UTCresolved

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

1. 5 Ağustos 2026 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 Ağustos 2026 04:57 UTCmonitoring

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

3. 5 Ağustos 2026 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 Ağustos 2026 10:00 UTCinvestigating

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

5. 5 Ağustos 2026 12:51 UTCmonitoring

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

6. 5 Ağustos 2026 13:35 UTCresolved

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

1. 4 Ağustos 2026 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 Ağustos 2026 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 Ağustos 2026 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 Temmuz 2026 19:59 UTCinvestigating

   Şu anda tüm ürün hatlarında bazı testler için kısmi bozulma yaşıyoruz. Mevcut oldukları gibi güncellemeler vereceğiz.

2. 23 Temmuz 2026 20:59 UTCmonitoring

   Sistem iyileşti ve Snyk Mühendisleri şu anda platformu izliyor.

3. 24 Temmuz 2026 10:34 UTCresolved

   İzleme dönemimizde daha fazla hata gözlemlenmedi. Snyk Olay Yanıtı şimdi durdu.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 23 Temmuz 2026 14:56 UTCresolved

   Dün yaşanan olayın kısa bir tekrarlayıcısı vardı, müşterileri iki kısa pencerede etkiler: 14:27-14:36 UTC 14:37-14:42 UTC Servis şimdi geri döndü. Müşteriler bu pencereler sırasında hatalanan veya başarısız olan herhangi bir ithalat geri yüklemelidir.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 22 Temmuz 2026 09:41 UTCmonitoring

   09:08'den itibaren UTC müşterileri Snyk Open Source veya Snyk konteyner için ithalat yaparken deneyimli hatalar olabilir. Ayrıca, bazı müşteriler bu proje türleri için Project detaylarını incelemeye çalışırken deneyimli sorunlar olabilir. Snyk Olay cevabı aktive edildi ve düzeltici eylemler normale geri döndü. Takım durumu izlemeye devam ediyor.

2. 23 Temmuz 2026 07:09 UTCresolved

   İzleme dönemimizde daha fazla etki gözlemlenmedi. Müşteriler, dışlama penceresi sırasında hatalanan veya başarısız olan herhangi bir ithalata geri göndermelidir. Snyk Olay Yanıtı durdu.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 14 Temmuz 2026 18:18 UTCidentified

   Çalışma alanları Hizmetler ve Kod PR kontrollerini SNYK-EU-01 multi-tenant çevre içinde etkileyen bir sorunu tespit ettik. Lütfen Open Source ve Lisans özelliklerinin etkilenmediğini ve tamamen operasyonel kaldığını unutmayın. Mühendislik ekibimiz aktif olarak bir karar üzerinde çalışıyor.

2. 14 Temmuz 2026 18:58 UTCmonitoring

   Mühendislerimiz kök nedenini tespit ettiler ve bir mitigation, tamamen operasyonel duruma geri döndüler. istikrar sağlamak için çevreyi izlemeye devam edeceğiz.

3. 14 Temmuz 2026 20:12 UTCresolved

   Tüm hizmetler istikrarlı kalır. Olay şimdi çözüldü.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 14 Temmuz 2026 17:56 UTCidentified

   Bir subset of public-face API rotalarını etkileyen geçici başarısızlıkların farkındayız. Ekibimiz konuyu belirledi ve aktif olarak bir mitigation dağıtıyor. Sorun çözüldüğünde bir güncelleme sağlayacağız.

2. 14 Temmuz 2026 20:14 UTCresolved

   Bir düzeltme yapıldı ve tüm sistemler normalde performans gösteriyor. Bu olay çözüm olarak işaretlenmiştir.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

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

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

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

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

4. 25 Haziran 2026 12:14 UTCresolved

   This incident has been resolved.

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

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

6. 24 Haziran 2026 21:34 UTCresolved

   This incident has been resolved.

1. 19 Haziran 2026 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 Haziran 2026 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 Temmuz 2026 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 Haziran 2026 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 Haziran 2026 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 Haziran 2026 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 Haziran 2026 10:59 UTCresolved

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