Historial de interrupciones de Wiz

1. September 3, 2026 at 10:31 PM UTCinvestigating

   Estamos investigando un problema que afecta a algunos servicios de Wiz para inquilinos hospedados en AWS us-west-2. This appears related to an ongoing AWS service disruption https://health.aws.amazon.com/health/status

2. September 3, 2026 at 10:39 PM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

3. September 3, 2026 at 11:50 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 23, 2026 at 4:51 PM UTCinvestigating

   Centros de datos afectados: US2, US6, US10, US14, US18, US21, US24, US27, US33, US38, US41, US44, US46, US49, US52, US56, US59 y US62. Estamos experimentando una degradación del servicio que afecta a los clientes acogidos en múltiples centros de datos estadounidenses. Los clientes pueden encontrar una carga lenta o no exitosa de algunas páginas, errores de API y retrasos en la ingestión y procesamiento de datos. Esto está relacionado con una perturbación continua de la región de Microsoft Azure West US. Trabajamos activamente para restaurar el servicio y proporcionaremos nuevas actualizaciones a medida que estén disponibles.

2. July 23, 2026 at 8:52 PM UTCmonitoring

   Se ha resuelto la interrupción del servicio de Microsoft Azure, y se ha restaurado la disponibilidad de servicios. La ingestión y detección de datos son operativos, pero algunos clientes pueden seguir experimentando retrasos mientras el procesamiento alcanza. Estamos monitoreando la recuperación y trabajando para asegurar que todos los servicios regresen a un rendimiento normal.

3. July 23, 2026 at 10:00 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 10, 2026 at 4:55 PM 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. July 10, 2026 at 5:28 PM UTCmonitoring

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

3. July 10, 2026 at 6:08 PM UTCresolved

   This incident has been resolved.

1. June 22, 2026 at 1:43 PM UTCinvestigating

   We are currently investigating this issue.

2. June 22, 2026 at 2:08 PM UTCidentified

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

3. June 22, 2026 at 5:13 PM UTCmonitoring

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

4. June 22, 2026 at 6:39 PM UTCresolved

   This incident has been resolved.

1. June 20, 2026 at 10:00 PM UTCinvestigating

   We are currently investigating this issue.

2. June 20, 2026 at 11:39 PM UTCmonitoring

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

3. June 21, 2026 at 4:01 AM UTCresolved

   This incident has been resolved.

1. June 17, 2026 at 5:30 PM UTCinvestigating

   We are currently investigating this issue.

2. June 17, 2026 at 5:38 PM UTCidentified

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

3. June 17, 2026 at 5:43 PM UTCmonitoring

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

4. June 17, 2026 at 5:58 PM UTCresolved

   This incident has been resolved.

1. June 8, 2026 at 6:23 PM UTCidentified

   We have identified the cause and are deploying a fix.

2. June 8, 2026 at 7:33 PM UTCresolved

   This incident has been resolved.

1. May 20, 2026 at 2:04 PM UTCidentified

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

2. May 20, 2026 at 5:52 PM UTCmonitoring

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

3. May 21, 2026 at 4:17 AM UTCresolved

   This incident has been resolved.

1. May 11, 2026 at 6:17 AM UTCinvestigating

   We are currently investigating this issue.

2. May 11, 2026 at 6:17 AM UTCidentified

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

3. May 11, 2026 at 8:26 AM UTCmonitoring

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

4. May 11, 2026 at 8:29 AM UTCresolved

   This incident has been resolved.

1. May 8, 2026 at 7:06 AM 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. May 8, 2026 at 10:07 AM UTCmonitoring

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

3. May 8, 2026 at 10:13 AM UTCresolved

   This incident has been resolved.

1. April 27, 2026 at 10:35 AM UTCidentified

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

2. April 27, 2026 at 11:33 AM UTCmonitoring

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

3. April 27, 2026 at 11:43 AM UTCresolved

   This incident has been resolved.

1. April 17, 2026 at 7:16 AM UTCinvestigating

   We are currently investigating this issue.

2. April 17, 2026 at 2:04 PM UTCmonitoring

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

3. April 18, 2026 at 2:35 AM UTCresolved

   This incident has been resolved.

1. April 14, 2026 at 6:19 AM UTCinvestigating

   We are currently investigating this issue.

2. April 14, 2026 at 6:45 AM UTCresolved

   This incident has been resolved.

1. April 3, 2026 at 3:32 PM 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. April 3, 2026 at 4:47 PM UTCmonitoring

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

3. April 4, 2026 at 7:04 PM UTCresolved

   This incident has been resolved.

1. March 24, 2026 at 7:21 AM UTCinvestigating

   We are currently investigating this issue.

2. March 24, 2026 at 8:38 AM UTCidentified

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

3. March 24, 2026 at 7:38 PM UTCmonitoring

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

4. March 26, 2026 at 5:24 PM UTCresolved

   This incident has been resolved.

1. March 23, 2026 at 2:04 PM UTCinvestigating

   We are currently investigating this issue.

2. March 23, 2026 at 6:51 PM UTCmonitoring

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

3. March 23, 2026 at 8:37 PM UTCresolved

   This incident has been resolved.

1. March 22, 2026 at 6:11 PM UTCmonitoring

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

2. March 22, 2026 at 11:22 PM UTCresolved

   This incident has been resolved.

1. March 19, 2026 at 3:53 PM UTCidentified

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

2. March 19, 2026 at 9:51 PM UTCmonitoring

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

3. March 20, 2026 at 6:35 PM UTCresolved

   This incident has been resolved.

1. March 5, 2026 at 10:56 PM 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. March 5, 2026 at 9:56 PM UTCinvestigating

   We are currently investigating this issue.

2. March 5, 2026 at 10:33 PM UTCresolved

   This incident has been resolved.