Wiz kesinti geçmişi

1. 3 Eylül 2026 22:31 UTCinvestigating

   AWS'de barındırılan kiracılar için bazı Wiz hizmetlerini etkileyen bir sorunu araştırıyoruz. Bu, devam eden bir AWS hizmeti kesintisiyle ilgili görünüyor: https://health.aws.amazon.com/health/status

2. 3 Eylül 2026 22:39 UTCmonitoring

   Bir düzeltme uygulandı ve sonuçları takip ediyoruz.

3. 3 Eylül 2026 23:50 UTCresolved

   Bu olay çözüldü.

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

1. 23 Temmuz 2026 16:51 UTCinvestigating

   Etkilenen veri merkezleri: US2, US6, US10, ABD14, ABD18, ABD21, ABD24, ABD27, ABD33, ABD38, ABD41, ABD44, ABD46, ABD49, ABD52, ABD56, ABD59 ve ABD62. Birden fazla ABD veri merkezinde barındırılan müşterileri etkileyen bir hizmet bozulması yaşıyoruz. Müşteriler bazı sayfaların yavaş veya başarısız ile karşılaşabilir, API hataları ve verilerin kesinti ve işlenmesinde gecikmeler. Bu, devam eden bir Microsoft Azure West US bölgesi kesintisiyle ilgilidir. Hizmeti geri yüklemek için aktif olarak çalışıyoruz ve mevcut oldukları gibi daha fazla güncelleme sağlayacaktır.

2. 23 Temmuz 2026 20:52 UTCmonitoring

   Microsoft Azure servisi kesintisi çözüldü ve hizmet kullanılabilirliği restore edildi. Data ingestion ve algılama operasyoneldir, ancak bazı müşteriler işlem yakalarken gecikmeler yaşamaya devam edebilir. Tüm hizmetleri normal performansa geri dönmek için kurtarmayı ve çalışmayı izliyoruz.

3. 23 Temmuz 2026 22:00 UTCresolved

   Bu olay çözüldü.

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

1. 10 Temmuz 2026 16:55 UTCinvestigating

   We are currently observing elevated error rates affecting some Wiz services due to an incident with an upstream dependency, LaunchDarkly. Our teams are monitoring the situation and assessing the scope of the impact. LaunchDarkly is providing updates on its status page: https://status.launchdarkly.com/ We will share additional information as it becomes available.

2. 10 Temmuz 2026 17:28 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 10 Temmuz 2026 18:08 UTCresolved

   This incident has been resolved.

1. 22 Haziran 2026 13:43 UTCinvestigating

   We are currently investigating this issue.

2. 22 Haziran 2026 14:08 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 22 Haziran 2026 17:13 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 22 Haziran 2026 18:39 UTCresolved

   This incident has been resolved.

1. 20 Haziran 2026 22:00 UTCinvestigating

   We are currently investigating this issue.

2. 20 Haziran 2026 23:39 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 21 Haziran 2026 04:01 UTCresolved

   This incident has been resolved.

1. 17 Haziran 2026 17:30 UTCinvestigating

   We are currently investigating this issue.

2. 17 Haziran 2026 17:38 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 17 Haziran 2026 17:43 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 17 Haziran 2026 17:58 UTCresolved

   This incident has been resolved.

1. 8 Haziran 2026 18:23 UTCidentified

   We have identified the cause and are deploying a fix.

2. 8 Haziran 2026 19:33 UTCresolved

   This incident has been resolved.

1. 20 Mayıs 2026 14:04 UTCidentified

   The issue has been identified and a fix is being implemented.

2. 20 Mayıs 2026 17:52 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 21 Mayıs 2026 04:17 UTCresolved

   This incident has been resolved.

1. 11 Mayıs 2026 06:17 UTCinvestigating

   We are currently investigating this issue.

2. 11 Mayıs 2026 06:17 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 11 Mayıs 2026 08:26 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 11 Mayıs 2026 08:29 UTCresolved

   This incident has been resolved.

1. 8 Mayıs 2026 07:06 UTCinvestigating

   We are monitoring an upstream AWS infrastructure issue and portal searches, affecting the us-east-1 region. AWS has reported an EC2 API issue, and we are tracking updates on the AWS Health Dashboard: https://health.aws.amazon.com/health/status At this stage, the main customer impact appears to be delays in asynchronous queue processing. As a result, some actions may be delayed or degraded, including notifications, automation triggers, and data synchronization. AWS has indicated recovery is in progress, and our team is continuing to monitor queue health and overall service recovery. We will provide another update once service health has stabilized.

2. 8 Mayıs 2026 10:07 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 8 Mayıs 2026 10:13 UTCresolved

   This incident has been resolved.

1. 27 Nisan 2026 10:35 UTCidentified

   The issue has been identified and a fix is being implemented.

2. 27 Nisan 2026 11:33 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 27 Nisan 2026 11:43 UTCresolved

   This incident has been resolved.

1. 17 Nisan 2026 07:16 UTCinvestigating

   We are currently investigating this issue.

2. 17 Nisan 2026 14:04 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 18 Nisan 2026 02:35 UTCresolved

   This incident has been resolved.

1. 14 Nisan 2026 06:19 UTCinvestigating

   We are currently investigating this issue.

2. 14 Nisan 2026 06:45 UTCresolved

   This incident has been resolved.

1. 3 Nisan 2026 15:32 UTCidentified

   We are investigating the issue. A fix is in progress, and the classification of any affected findings is expected to be corrected after the update is deployed and the next scan is completed.

2. 3 Nisan 2026 16:47 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 4 Nisan 2026 19:04 UTCresolved

   This incident has been resolved.

1. 24 Mart 2026 07:21 UTCinvestigating

   We are currently investigating this issue.

2. 24 Mart 2026 08:38 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 24 Mart 2026 19:38 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 26 Mart 2026 17:24 UTCresolved

   This incident has been resolved.

1. 23 Mart 2026 14:04 UTCinvestigating

   We are currently investigating this issue.

2. 23 Mart 2026 18:51 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 23 Mart 2026 20:37 UTCresolved

   This incident has been resolved.

1. 22 Mart 2026 18:11 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

2. 22 Mart 2026 23:22 UTCresolved

   This incident has been resolved.

1. 19 Mart 2026 15:53 UTCidentified

   The issue has been identified and a fix is being implemented.

2. 19 Mart 2026 21:51 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 20 Mart 2026 18:35 UTCresolved

   This incident has been resolved.

1. 5 Mart 2026 22:56 UTCinvestigating

   We are monitoring the ongoing AWS service disruption in the me-central-1 region. Recovery of affected Wiz services is dependent on AWS resource availability in the region, followed by validation and restoration activities on our side. AWS status: https://health.aws.amazon.com/health/status Affected Wiz DC: prod-me1

1. 5 Mart 2026 21:56 UTCinvestigating

   We are currently investigating this issue.

2. 5 Mart 2026 22:33 UTCresolved

   This incident has been resolved.