Histórico de interrupções do Wiz

1. 3 Gwengolo 2026 da 22:31 UTCinvestigating

   Estamos investigando um problema que afeta alguns serviços Wiz para inquilinos hospedados na AWS us-west-2. Isto parece estar relacionado com uma interrupção contínua do serviço AWS https://health.aws.amazon.com/health/status

2. 3 Gwengolo 2026 da 22:39 UTCmonitoring

   Foi implementada uma correção e estamos monitorando os resultados.

3. 3 Gwengolo 2026 da 23:50 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 23 Gouere 2026 da 16:51 UTCinvestigating

   Centros de dados afetados: US2, US6, US10, US14, US18, US21, US24, US27, US33, US38, US41, US44, US46, US49, US52, US56, US59 e US62. Estamos experimentando uma degradação de serviços afetando clientes hospedados em vários data centers dos EUA. Os clientes podem encontrar carregamento lento ou sem sucesso de algumas páginas, erros de API e atrasos na ingestão e processamento de dados. Isso está relacionado com uma interrupção contínua da região da Microsoft Azure West US. Estamos trabalhando ativamente para restaurar o serviço e forneceremos novas atualizações à medida que eles se tornam disponíveis.

2. 23 Gouere 2026 da 20:52 UTCmonitoring

   A interrupção do serviço do Microsoft Azure foi resolvida e a disponibilidade do serviço foi restaurada. A ingestão e detecção de dados estão operacionais, mas alguns clientes podem continuar a ter atrasos durante o processamento. Estamos monitorando a recuperação e trabalhando para garantir que todos os serviços retornem ao desempenho normal.

3. 23 Gouere 2026 da 22:00 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

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

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

3. 10 Gouere 2026 da 18:08 UTCresolved

   This incident has been resolved.

1. 22 Mezheven 2026 da 13:43 UTCinvestigating

   We are currently investigating this issue.

2. 22 Mezheven 2026 da 14:08 UTCidentified

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

3. 22 Mezheven 2026 da 17:13 UTCmonitoring

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

4. 22 Mezheven 2026 da 18:39 UTCresolved

   This incident has been resolved.

1. 20 Mezheven 2026 da 22:00 UTCinvestigating

   We are currently investigating this issue.

2. 20 Mezheven 2026 da 23:39 UTCmonitoring

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

3. 21 Mezheven 2026 da 04:01 UTCresolved

   This incident has been resolved.

1. 17 Mezheven 2026 da 17:30 UTCinvestigating

   We are currently investigating this issue.

2. 17 Mezheven 2026 da 17:38 UTCidentified

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

3. 17 Mezheven 2026 da 17:43 UTCmonitoring

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

4. 17 Mezheven 2026 da 17:58 UTCresolved

   This incident has been resolved.

1. 8 Mezheven 2026 da 18:23 UTCidentified

   We have identified the cause and are deploying a fix.

2. 8 Mezheven 2026 da 19:33 UTCresolved

   This incident has been resolved.

1. 20 Mae 2026 da 14:04 UTCidentified

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

2. 20 Mae 2026 da 17:52 UTCmonitoring

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

3. 21 Mae 2026 da 04:17 UTCresolved

   This incident has been resolved.

1. 11 Mae 2026 da 06:17 UTCinvestigating

   We are currently investigating this issue.

2. 11 Mae 2026 da 06:17 UTCidentified

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

3. 11 Mae 2026 da 08:26 UTCmonitoring

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

4. 11 Mae 2026 da 08:29 UTCresolved

   This incident has been resolved.

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

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

3. 8 Mae 2026 da 10:13 UTCresolved

   This incident has been resolved.

1. 27 Ebrel 2026 da 10:35 UTCidentified

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

2. 27 Ebrel 2026 da 11:33 UTCmonitoring

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

3. 27 Ebrel 2026 da 11:43 UTCresolved

   This incident has been resolved.

1. 17 Ebrel 2026 da 07:16 UTCinvestigating

   We are currently investigating this issue.

2. 17 Ebrel 2026 da 14:04 UTCmonitoring

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

3. 18 Ebrel 2026 da 02:35 UTCresolved

   This incident has been resolved.

1. 14 Ebrel 2026 da 06:19 UTCinvestigating

   We are currently investigating this issue.

2. 14 Ebrel 2026 da 06:45 UTCresolved

   This incident has been resolved.

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

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

3. 4 Ebrel 2026 da 19:04 UTCresolved

   This incident has been resolved.

1. 24 Meurzh 2026 da 07:21 UTCinvestigating

   We are currently investigating this issue.

2. 24 Meurzh 2026 da 08:38 UTCidentified

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

3. 24 Meurzh 2026 da 19:38 UTCmonitoring

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

4. 26 Meurzh 2026 da 17:24 UTCresolved

   This incident has been resolved.

1. 23 Meurzh 2026 da 14:04 UTCinvestigating

   We are currently investigating this issue.

2. 23 Meurzh 2026 da 18:51 UTCmonitoring

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

3. 23 Meurzh 2026 da 20:37 UTCresolved

   This incident has been resolved.

1. 22 Meurzh 2026 da 18:11 UTCmonitoring

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

2. 22 Meurzh 2026 da 23:22 UTCresolved

   This incident has been resolved.

1. 19 Meurzh 2026 da 15:53 UTCidentified

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

2. 19 Meurzh 2026 da 21:51 UTCmonitoring

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

3. 20 Meurzh 2026 da 18:35 UTCresolved

   This incident has been resolved.

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

   We are currently investigating this issue.

2. 5 Meurzh 2026 da 22:33 UTCresolved

   This incident has been resolved.