Cronologia delle interruzioni di Wiz

1. 3 settembre 2026 alle ore 22:31 UTCinvestigating

   Stiamo indagando su un problema che riguarda alcuni servizi Wiz per gli inquilini ospitati in AWS us-west-2. Questo appare in relazione ad una continua interruzione del servizio AWS https://health.aws.amazon.com/health/status

2. 3 settembre 2026 alle ore 22:39 UTCmonitoring

   Una soluzione è stata implementata e stiamo monitorando i risultati.

3. 3 settembre 2026 alle ore 23:50 UTCresolved

   Questo incidente è stato risolto.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 23 luglio 2026 alle ore 16:51 UTCinvestigating

   Centri di dati interessati: US2, US6, US10, US14, US18, US21, US24, US27, US33, US38, US41, US44, US46, US49, US52, US56, US59, e US62. Stiamo vivendo un degrado di servizio che interessa i clienti ospitati in più data center statunitensi. I clienti possono incontrare carico lento o non riuscito di alcune pagine, errori API e ritardi nell'ingestione e nell'elaborazione dei dati. Questo è legato a una continua interruzione della regione di Microsoft Azure West Stati Uniti. Stiamo lavorando attivamente per ripristinare il servizio e fornirà ulteriori aggiornamenti come diventano disponibili.

2. 23 luglio 2026 alle ore 20:52 UTCmonitoring

   L'interruzione di servizio Microsoft Azure a monte è stata risolta e la disponibilità di servizio è stata ripristinata. L'ingestione e il rilevamento dei dati sono operativi, ma alcuni clienti possono continuare a sperimentare ritardi durante l'elaborazione rileva. Stiamo monitorando il recupero e il lavoro per garantire che tutti i servizi ritornino alle normali prestazioni.

3. 23 luglio 2026 alle ore 22:00 UTCresolved

   Questo incidente è stato risolto.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

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

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

3. 10 luglio 2026 alle ore 18:08 UTCresolved

   This incident has been resolved.

1. 22 giugno 2026 alle ore 13:43 UTCinvestigating

   We are currently investigating this issue.

2. 22 giugno 2026 alle ore 14:08 UTCidentified

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

3. 22 giugno 2026 alle ore 17:13 UTCmonitoring

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

4. 22 giugno 2026 alle ore 18:39 UTCresolved

   This incident has been resolved.

1. 20 giugno 2026 alle ore 22:00 UTCinvestigating

   We are currently investigating this issue.

2. 20 giugno 2026 alle ore 23:39 UTCmonitoring

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

3. 21 giugno 2026 alle ore 04:01 UTCresolved

   This incident has been resolved.

1. 17 giugno 2026 alle ore 17:30 UTCinvestigating

   We are currently investigating this issue.

2. 17 giugno 2026 alle ore 17:38 UTCidentified

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

3. 17 giugno 2026 alle ore 17:43 UTCmonitoring

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

4. 17 giugno 2026 alle ore 17:58 UTCresolved

   This incident has been resolved.

1. 8 giugno 2026 alle ore 18:23 UTCidentified

   We have identified the cause and are deploying a fix.

2. 8 giugno 2026 alle ore 19:33 UTCresolved

   This incident has been resolved.

1. 20 maggio 2026 alle ore 14:04 UTCidentified

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

2. 20 maggio 2026 alle ore 17:52 UTCmonitoring

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

3. 21 maggio 2026 alle ore 04:17 UTCresolved

   This incident has been resolved.

1. 11 maggio 2026 alle ore 06:17 UTCinvestigating

   We are currently investigating this issue.

2. 11 maggio 2026 alle ore 06:17 UTCidentified

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

3. 11 maggio 2026 alle ore 08:26 UTCmonitoring

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

4. 11 maggio 2026 alle ore 08:29 UTCresolved

   This incident has been resolved.

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

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

3. 8 maggio 2026 alle ore 10:13 UTCresolved

   This incident has been resolved.

1. 27 aprile 2026 alle ore 10:35 UTCidentified

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

2. 27 aprile 2026 alle ore 11:33 UTCmonitoring

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

3. 27 aprile 2026 alle ore 11:43 UTCresolved

   This incident has been resolved.

1. 17 aprile 2026 alle ore 07:16 UTCinvestigating

   We are currently investigating this issue.

2. 17 aprile 2026 alle ore 14:04 UTCmonitoring

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

3. 18 aprile 2026 alle ore 02:35 UTCresolved

   This incident has been resolved.

1. 14 aprile 2026 alle ore 06:19 UTCinvestigating

   We are currently investigating this issue.

2. 14 aprile 2026 alle ore 06:45 UTCresolved

   This incident has been resolved.

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

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

3. 4 aprile 2026 alle ore 19:04 UTCresolved

   This incident has been resolved.

1. 24 marzo 2026 alle ore 07:21 UTCinvestigating

   We are currently investigating this issue.

2. 24 marzo 2026 alle ore 08:38 UTCidentified

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

3. 24 marzo 2026 alle ore 19:38 UTCmonitoring

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

4. 26 marzo 2026 alle ore 17:24 UTCresolved

   This incident has been resolved.

1. 23 marzo 2026 alle ore 14:04 UTCinvestigating

   We are currently investigating this issue.

2. 23 marzo 2026 alle ore 18:51 UTCmonitoring

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

3. 23 marzo 2026 alle ore 20:37 UTCresolved

   This incident has been resolved.

1. 22 marzo 2026 alle ore 18:11 UTCmonitoring

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

2. 22 marzo 2026 alle ore 23:22 UTCresolved

   This incident has been resolved.

1. 19 marzo 2026 alle ore 15:53 UTCidentified

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

2. 19 marzo 2026 alle ore 21:51 UTCmonitoring

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

3. 20 marzo 2026 alle ore 18:35 UTCresolved

   This incident has been resolved.

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

   We are currently investigating this issue.

2. 5 marzo 2026 alle ore 22:33 UTCresolved

   This incident has been resolved.