Wiz driftsforstyrrelser

1. 3. september 2026 kl. 22.31 UTCinvestigating

   Vi undersøger et problem, der påvirker nogle Wiz tjenester for lejere hostet i AWS us-west-2. Dette synes at være relateret til en igangværende AWS service afbrydelse https: / / healt.aws.amazon.com / health / status

2. 3. september 2026 kl. 22.39 UTCmonitoring

   Et fix er blevet gennemført, og vi overvåger resultaterne.

3. 3. september 2026 kl. 23.50 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 23. juli 2026 kl. 16.51 UTCinvestigating

   Berørte datacentre: US2, US6, US10, US14, US18, US21, US24, US27, US33, US38, US41, US44, US46, US49, US52, US56, US59 og US62. Vi oplever en forringelse af service påvirker kunder hostet i flere amerikanske datacentre. Kunder kan støde på langsom eller mislykket indlæsning af nogle sider, API fejl, og forsinkelser i data indtagelse og behandling. Dette er relateret til en igangværende Microsoft Azure West US region forstyrrelse. Vi arbejder aktivt på at genoprette tjenesten og vil levere yderligere opdateringer, efterhånden som de bliver tilgængelige.

2. 23. juli 2026 kl. 20.52 UTCmonitoring

   Opstrøms Microsoft Azure service afbrydelse er blevet løst, og service tilgængelighed er blevet genoprettet. Data indtagelse og detektion er operationelle, men nogle kunder kan fortsætte med at opleve forsinkelser, mens behandling indhente. Vi overvåger opsvinget og arbejder på at sikre, at alle tjenester vender tilbage til normale præstationer.

3. 23. juli 2026 kl. 22.00 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 10. juli 2026 kl. 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. juli 2026 kl. 17.28 UTCmonitoring

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

3. 10. juli 2026 kl. 18.08 UTCresolved

   This incident has been resolved.

1. 22. juni 2026 kl. 13.43 UTCinvestigating

   We are currently investigating this issue.

2. 22. juni 2026 kl. 14.08 UTCidentified

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

3. 22. juni 2026 kl. 17.13 UTCmonitoring

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

4. 22. juni 2026 kl. 18.39 UTCresolved

   This incident has been resolved.

1. 20. juni 2026 kl. 22.00 UTCinvestigating

   We are currently investigating this issue.

2. 20. juni 2026 kl. 23.39 UTCmonitoring

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

3. 21. juni 2026 kl. 04.01 UTCresolved

   This incident has been resolved.

1. 17. juni 2026 kl. 17.30 UTCinvestigating

   We are currently investigating this issue.

2. 17. juni 2026 kl. 17.38 UTCidentified

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

3. 17. juni 2026 kl. 17.43 UTCmonitoring

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

4. 17. juni 2026 kl. 17.58 UTCresolved

   This incident has been resolved.

1. 8. juni 2026 kl. 18.23 UTCidentified

   We have identified the cause and are deploying a fix.

2. 8. juni 2026 kl. 19.33 UTCresolved

   This incident has been resolved.

1. 20. maj 2026 kl. 14.04 UTCidentified

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

2. 20. maj 2026 kl. 17.52 UTCmonitoring

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

3. 21. maj 2026 kl. 04.17 UTCresolved

   This incident has been resolved.

1. 11. maj 2026 kl. 06.17 UTCinvestigating

   We are currently investigating this issue.

2. 11. maj 2026 kl. 06.17 UTCidentified

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

3. 11. maj 2026 kl. 08.26 UTCmonitoring

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

4. 11. maj 2026 kl. 08.29 UTCresolved

   This incident has been resolved.

1. 8. maj 2026 kl. 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. maj 2026 kl. 10.07 UTCmonitoring

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

3. 8. maj 2026 kl. 10.13 UTCresolved

   This incident has been resolved.

1. 27. april 2026 kl. 10.35 UTCidentified

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

2. 27. april 2026 kl. 11.33 UTCmonitoring

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

3. 27. april 2026 kl. 11.43 UTCresolved

   This incident has been resolved.

1. 17. april 2026 kl. 07.16 UTCinvestigating

   We are currently investigating this issue.

2. 17. april 2026 kl. 14.04 UTCmonitoring

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

3. 18. april 2026 kl. 02.35 UTCresolved

   This incident has been resolved.

1. 14. april 2026 kl. 06.19 UTCinvestigating

   We are currently investigating this issue.

2. 14. april 2026 kl. 06.45 UTCresolved

   This incident has been resolved.

1. 3. april 2026 kl. 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. april 2026 kl. 16.47 UTCmonitoring

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

3. 4. april 2026 kl. 19.04 UTCresolved

   This incident has been resolved.

1. 24. marts 2026 kl. 07.21 UTCinvestigating

   We are currently investigating this issue.

2. 24. marts 2026 kl. 08.38 UTCidentified

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

3. 24. marts 2026 kl. 19.38 UTCmonitoring

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

4. 26. marts 2026 kl. 17.24 UTCresolved

   This incident has been resolved.

1. 23. marts 2026 kl. 14.04 UTCinvestigating

   We are currently investigating this issue.

2. 23. marts 2026 kl. 18.51 UTCmonitoring

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

3. 23. marts 2026 kl. 20.37 UTCresolved

   This incident has been resolved.

1. 22. marts 2026 kl. 18.11 UTCmonitoring

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

2. 22. marts 2026 kl. 23.22 UTCresolved

   This incident has been resolved.

1. 19. marts 2026 kl. 15.53 UTCidentified

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

2. 19. marts 2026 kl. 21.51 UTCmonitoring

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

3. 20. marts 2026 kl. 18.35 UTCresolved

   This incident has been resolved.

1. 5. marts 2026 kl. 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. marts 2026 kl. 21.56 UTCinvestigating

   We are currently investigating this issue.

2. 5. marts 2026 kl. 22.33 UTCresolved

   This incident has been resolved.