Historia awarii Wiz

1. 3 września 2026 22:31 UTCinvestigating

   Badamy problem dotyczący niektórych usług Wiz dla najemców w AWS us- west- 2. Wydaje się to związane z trwającym zakłóceniem usługi AWS https: / / health.aws.amazon.com / health / status

2. 3 września 2026 22:39 UTCmonitoring

   Wprowadzono rozwiązanie i monitorujemy wyniki.

3. 3 września 2026 23:50 UTCresolved

   Ten incydent został rozwiązany.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 23 lipca 2026 16:51 UTCinvestigating

   Dotknięte centra danych: US2, US6, US10, US14, US18, US21, US24, US27, US33, US38, US41, US44, US46, US49, US52, US56, US59 i US62. Doświadczamy degradacji usług wpływającej na klientów w wielu amerykańskich centrach danych. Klienci mogą napotkać powolny lub nieudany załadunek niektórych stron, błędy API i opóźnienia w przyjmowaniu i przetwarzaniu danych. Jest to związane z trwającym zakłóceniem w regionie Microsoft Azure West USA. Aktywnie pracujemy nad przywróceniem usług i dostarczymy dalsze aktualizacje w miarę ich dostępności.

2. 23 lipca 2026 20:52 UTCmonitoring

   Zakłócenie usługi Microsoft Azure zostało rozwiązane, a dostępność usługi została przywrócona. Zażywanie i wykrywanie danych jest skuteczne, ale niektórzy klienci mogą nadal doświadczać opóźnień podczas przetwarzania połowów. Monitorujemy ożywienie gospodarcze i pracujemy nad zapewnieniem powrotu wszystkich usług do normalnych wyników.

3. 23 lipca 2026 22:00 UTCresolved

   Ten incydent został rozwiązany.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 10 lipca 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 lipca 2026 17:28 UTCmonitoring

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

3. 10 lipca 2026 18:08 UTCresolved

   This incident has been resolved.

1. 22 czerwca 2026 13:43 UTCinvestigating

   We are currently investigating this issue.

2. 22 czerwca 2026 14:08 UTCidentified

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

3. 22 czerwca 2026 17:13 UTCmonitoring

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

4. 22 czerwca 2026 18:39 UTCresolved

   This incident has been resolved.

1. 20 czerwca 2026 22:00 UTCinvestigating

   We are currently investigating this issue.

2. 20 czerwca 2026 23:39 UTCmonitoring

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

3. 21 czerwca 2026 04:01 UTCresolved

   This incident has been resolved.

1. 17 czerwca 2026 17:30 UTCinvestigating

   We are currently investigating this issue.

2. 17 czerwca 2026 17:38 UTCidentified

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

3. 17 czerwca 2026 17:43 UTCmonitoring

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

4. 17 czerwca 2026 17:58 UTCresolved

   This incident has been resolved.

1. 8 czerwca 2026 18:23 UTCidentified

   We have identified the cause and are deploying a fix.

2. 8 czerwca 2026 19:33 UTCresolved

   This incident has been resolved.

1. 20 maja 2026 14:04 UTCidentified

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

2. 20 maja 2026 17:52 UTCmonitoring

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

3. 21 maja 2026 04:17 UTCresolved

   This incident has been resolved.

1. 11 maja 2026 06:17 UTCinvestigating

   We are currently investigating this issue.

2. 11 maja 2026 06:17 UTCidentified

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

3. 11 maja 2026 08:26 UTCmonitoring

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

4. 11 maja 2026 08:29 UTCresolved

   This incident has been resolved.

1. 8 maja 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 maja 2026 10:07 UTCmonitoring

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

3. 8 maja 2026 10:13 UTCresolved

   This incident has been resolved.

1. 27 kwietnia 2026 10:35 UTCidentified

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

2. 27 kwietnia 2026 11:33 UTCmonitoring

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

3. 27 kwietnia 2026 11:43 UTCresolved

   This incident has been resolved.

1. 17 kwietnia 2026 07:16 UTCinvestigating

   We are currently investigating this issue.

2. 17 kwietnia 2026 14:04 UTCmonitoring

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

3. 18 kwietnia 2026 02:35 UTCresolved

   This incident has been resolved.

1. 14 kwietnia 2026 06:19 UTCinvestigating

   We are currently investigating this issue.

2. 14 kwietnia 2026 06:45 UTCresolved

   This incident has been resolved.

1. 3 kwietnia 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 kwietnia 2026 16:47 UTCmonitoring

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

3. 4 kwietnia 2026 19:04 UTCresolved

   This incident has been resolved.

1. 24 marca 2026 07:21 UTCinvestigating

   We are currently investigating this issue.

2. 24 marca 2026 08:38 UTCidentified

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

3. 24 marca 2026 19:38 UTCmonitoring

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

4. 26 marca 2026 17:24 UTCresolved

   This incident has been resolved.

1. 23 marca 2026 14:04 UTCinvestigating

   We are currently investigating this issue.

2. 23 marca 2026 18:51 UTCmonitoring

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

3. 23 marca 2026 20:37 UTCresolved

   This incident has been resolved.

1. 22 marca 2026 18:11 UTCmonitoring

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

2. 22 marca 2026 23:22 UTCresolved

   This incident has been resolved.

1. 19 marca 2026 15:53 UTCidentified

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

2. 19 marca 2026 21:51 UTCmonitoring

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

3. 20 marca 2026 18:35 UTCresolved

   This incident has been resolved.

1. 5 marca 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 marca 2026 21:56 UTCinvestigating

   We are currently investigating this issue.

2. 5 marca 2026 22:33 UTCresolved

   This incident has been resolved.