Istoricul incidentelor Wiz

1. 3 septembrie 2026 la 22:31 UTCinvestigating

   Investigăm o problemă care afectează unele servicii Wiz pentru chiriași găzduit în AWS ne-west-2. Aceasta pare să aibă legătură cu o perturbare continuă a serviciilor AWS https://health.azon.com/health/status

2. 3 septembrie 2026 la 22:39 UTCmonitoring

   A fost implementată o soluţie şi monitorizăm rezultatele.

3. 3 septembrie 2026 la 23:50 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 23 iulie 2026 la 16:51 UTCinvestigating

   Centre de date afectate: US2, US6, US10, US14, US18, US21, US24, US27, US33, US38, US41, US44, US46, US49, US52, US56, US59 și US62. Ne confruntăm cu o degradare a serviciilor care afectează clienţii găzduiţi în mai multe centre de date americane. Clienții pot întâlni încărcare lentă sau nereușită a unor pagini, erori API, și întârzieri în ingerarea și prelucrarea datelor. Aceasta este legată de o perturbare a regiunii Microsoft Azure West SUA. Lucrăm activ pentru a restabili serviciul și va oferi actualizări suplimentare pe măsură ce acestea devin disponibile.

2. 23 iulie 2026 la 20:52 UTCmonitoring

   Perturbarea serviciului Microsoft Azure din amonte a fost rezolvată, iar disponibilitatea serviciilor a fost restabilită. Ingestia şi detectarea datelor sunt operaţionale, dar unii clienţi pot continua să experimenteze întârzieri în timpul prelucrării capturilor. Monitorizăm recuperarea și lucrăm pentru a asigura revenirea tuturor serviciilor la performanța normală.

3. 23 iulie 2026 la 22:00 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

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

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

3. 10 iulie 2026 la 18:08 UTCresolved

   This incident has been resolved.

1. 22 iunie 2026 la 13:43 UTCinvestigating

   We are currently investigating this issue.

2. 22 iunie 2026 la 14:08 UTCidentified

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

3. 22 iunie 2026 la 17:13 UTCmonitoring

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

4. 22 iunie 2026 la 18:39 UTCresolved

   This incident has been resolved.

1. 20 iunie 2026 la 22:00 UTCinvestigating

   We are currently investigating this issue.

2. 20 iunie 2026 la 23:39 UTCmonitoring

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

3. 21 iunie 2026 la 04:01 UTCresolved

   This incident has been resolved.

1. 17 iunie 2026 la 17:30 UTCinvestigating

   We are currently investigating this issue.

2. 17 iunie 2026 la 17:38 UTCidentified

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

3. 17 iunie 2026 la 17:43 UTCmonitoring

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

4. 17 iunie 2026 la 17:58 UTCresolved

   This incident has been resolved.

1. 8 iunie 2026 la 18:23 UTCidentified

   We have identified the cause and are deploying a fix.

2. 8 iunie 2026 la 19:33 UTCresolved

   This incident has been resolved.

1. 20 mai 2026 la 14:04 UTCidentified

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

2. 20 mai 2026 la 17:52 UTCmonitoring

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

3. 21 mai 2026 la 04:17 UTCresolved

   This incident has been resolved.

1. 11 mai 2026 la 06:17 UTCinvestigating

   We are currently investigating this issue.

2. 11 mai 2026 la 06:17 UTCidentified

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

3. 11 mai 2026 la 08:26 UTCmonitoring

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

4. 11 mai 2026 la 08:29 UTCresolved

   This incident has been resolved.

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

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

3. 8 mai 2026 la 10:13 UTCresolved

   This incident has been resolved.

1. 27 aprilie 2026 la 10:35 UTCidentified

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

2. 27 aprilie 2026 la 11:33 UTCmonitoring

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

3. 27 aprilie 2026 la 11:43 UTCresolved

   This incident has been resolved.

1. 17 aprilie 2026 la 07:16 UTCinvestigating

   We are currently investigating this issue.

2. 17 aprilie 2026 la 14:04 UTCmonitoring

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

3. 18 aprilie 2026 la 02:35 UTCresolved

   This incident has been resolved.

1. 14 aprilie 2026 la 06:19 UTCinvestigating

   We are currently investigating this issue.

2. 14 aprilie 2026 la 06:45 UTCresolved

   This incident has been resolved.

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

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

3. 4 aprilie 2026 la 19:04 UTCresolved

   This incident has been resolved.

1. 24 martie 2026 la 07:21 UTCinvestigating

   We are currently investigating this issue.

2. 24 martie 2026 la 08:38 UTCidentified

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

3. 24 martie 2026 la 19:38 UTCmonitoring

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

4. 26 martie 2026 la 17:24 UTCresolved

   This incident has been resolved.

1. 23 martie 2026 la 14:04 UTCinvestigating

   We are currently investigating this issue.

2. 23 martie 2026 la 18:51 UTCmonitoring

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

3. 23 martie 2026 la 20:37 UTCresolved

   This incident has been resolved.

1. 22 martie 2026 la 18:11 UTCmonitoring

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

2. 22 martie 2026 la 23:22 UTCresolved

   This incident has been resolved.

1. 19 martie 2026 la 15:53 UTCidentified

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

2. 19 martie 2026 la 21:51 UTCmonitoring

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

3. 20 martie 2026 la 18:35 UTCresolved

   This incident has been resolved.

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

   We are currently investigating this issue.

2. 5 martie 2026 la 22:33 UTCresolved

   This incident has been resolved.