Historique des pannes de Wiz

1. 3 septembre 2026 à 22:31 UTCinvestigating

   Nous enquêtons sur un problème touchant certains services Wiz pour les locataires hébergés dans AWS us-west-2. Cela semble lié à une interruption continue des services de SSFE https://health.aws.amazon.com/health/status

2. 3 septembre 2026 à 22:39 UTCmonitoring

   Un correctif a été mis en place et nous suivons les résultats.

3. 3 septembre 2026 à 23:50 UTCresolved

   Cet incident a été résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 23 juillet 2026 à 16:51 UTCinvestigating

   Centres de données touchés: US2, US6, US10, US14, US18, US21, US24, US27, US33, US38, US41, US44, US46, US49, US52, US56, US59 et US62. Nous vivons une dégradation du service affectant les clients hébergés dans plusieurs centres de données américains. Les clients peuvent rencontrer un chargement lent ou infructueux de certaines pages, des erreurs d'API et des retards dans l'ingestion et le traitement des données. Ceci est lié à une perturbation de Microsoft Azure Ouest des États-Unis. Nous travaillons activement à restaurer le service et fournirons d'autres mises à jour au fur et à mesure qu'elles seront disponibles.

2. 23 juillet 2026 à 20:52 UTCmonitoring

   La perturbation du service en amont de Microsoft Azure a été résolue et la disponibilité du service a été rétablie. L'ingestion et la détection des données sont opérationnelles, mais certains clients peuvent continuer à subir des retards pendant le rattrapage du traitement. Nous surveillons la récupération et travaillons pour assurer que tous les services reviennent à une performance normale.

3. 23 juillet 2026 à 22:00 UTCresolved

   Cet incident a été résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

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

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

3. 10 juillet 2026 à 18:08 UTCresolved

   This incident has been resolved.

1. 22 juin 2026 à 13:43 UTCinvestigating

   We are currently investigating this issue.

2. 22 juin 2026 à 14:08 UTCidentified

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

3. 22 juin 2026 à 17:13 UTCmonitoring

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

4. 22 juin 2026 à 18:39 UTCresolved

   This incident has been resolved.

1. 20 juin 2026 à 22:00 UTCinvestigating

   We are currently investigating this issue.

2. 20 juin 2026 à 23:39 UTCmonitoring

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

3. 21 juin 2026 à 04:01 UTCresolved

   This incident has been resolved.

1. 17 juin 2026 à 17:30 UTCinvestigating

   We are currently investigating this issue.

2. 17 juin 2026 à 17:38 UTCidentified

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

3. 17 juin 2026 à 17:43 UTCmonitoring

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

4. 17 juin 2026 à 17:58 UTCresolved

   This incident has been resolved.

1. 8 juin 2026 à 18:23 UTCidentified

   We have identified the cause and are deploying a fix.

2. 8 juin 2026 à 19:33 UTCresolved

   This incident has been resolved.

1. 20 mai 2026 à 14:04 UTCidentified

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

2. 20 mai 2026 à 17:52 UTCmonitoring

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

3. 21 mai 2026 à 04:17 UTCresolved

   This incident has been resolved.

1. 11 mai 2026 à 06:17 UTCinvestigating

   We are currently investigating this issue.

2. 11 mai 2026 à 06:17 UTCidentified

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

3. 11 mai 2026 à 08:26 UTCmonitoring

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

4. 11 mai 2026 à 08:29 UTCresolved

   This incident has been resolved.

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

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

3. 8 mai 2026 à 10:13 UTCresolved

   This incident has been resolved.

1. 27 avril 2026 à 10:35 UTCidentified

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

2. 27 avril 2026 à 11:33 UTCmonitoring

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

3. 27 avril 2026 à 11:43 UTCresolved

   This incident has been resolved.

1. 17 avril 2026 à 07:16 UTCinvestigating

   We are currently investigating this issue.

2. 17 avril 2026 à 14:04 UTCmonitoring

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

3. 18 avril 2026 à 02:35 UTCresolved

   This incident has been resolved.

1. 14 avril 2026 à 06:19 UTCinvestigating

   We are currently investigating this issue.

2. 14 avril 2026 à 06:45 UTCresolved

   This incident has been resolved.

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

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

3. 4 avril 2026 à 19:04 UTCresolved

   This incident has been resolved.

1. 24 mars 2026 à 07:21 UTCinvestigating

   We are currently investigating this issue.

2. 24 mars 2026 à 08:38 UTCidentified

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

3. 24 mars 2026 à 19:38 UTCmonitoring

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

4. 26 mars 2026 à 17:24 UTCresolved

   This incident has been resolved.

1. 23 mars 2026 à 14:04 UTCinvestigating

   We are currently investigating this issue.

2. 23 mars 2026 à 18:51 UTCmonitoring

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

3. 23 mars 2026 à 20:37 UTCresolved

   This incident has been resolved.

1. 22 mars 2026 à 18:11 UTCmonitoring

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

2. 22 mars 2026 à 23:22 UTCresolved

   This incident has been resolved.

1. 19 mars 2026 à 15:53 UTCidentified

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

2. 19 mars 2026 à 21:51 UTCmonitoring

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

3. 20 mars 2026 à 18:35 UTCresolved

   This incident has been resolved.

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

   We are currently investigating this issue.

2. 5 mars 2026 à 22:33 UTCresolved

   This incident has been resolved.