Störungsverlauf von Wiz

1. 3. September 2026 um 22:31 UTCinvestigating

   Wir untersuchen ein Problem, das einige Wiz-Dienste für Mieter betrifft, die in AWS us-west-2 gehostet werden. Dies scheint mit einer anhaltenden Unterbrechung der AWS-Dienste zu tun zu haben https://health.aws.amazon.com/health/status

2. 3. September 2026 um 22:39 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

3. 3. September 2026 um 23:50 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 23. Juli 2026 um 16:51 UTCinvestigating

   Betroffene Rechenzentren: US2, US6, US10, US14, US18, US21, US24, US27, US33, US38, US41, US44, US46, US49, US52, US56, US59 und US62. Wir erleben eine Service-Degradation, die Kunden betrifft, die in mehreren US-Rechenzentren gehostet werden. Kunden können auf ein langsames oder erfolgloses Laden einiger Seiten, API-Fehler und Verzögerungen bei der Datenaufnahme und -verarbeitung stoßen. Dies hängt mit einer anhaltenden Störung der Microsoft Azure West US-Region zusammen. Wir arbeiten aktiv daran, den Service wiederherzustellen und werden weitere Updates bereitstellen, sobald sie verfügbar sind.

2. 23. Juli 2026 um 20:52 UTCmonitoring

   Die Störung des vorgelagerten Microsoft Azure-Dienstes wurde behoben und die Dienstverfügbarkeit wurde wiederhergestellt. Die Datenaufnahme und -erkennung ist betriebsbereit, aber einige Kunden können weiterhin Verzögerungen erleben, während die Verarbeitung aufholt. Wir überwachen die Wiederherstellung und arbeiten daran, dass alle Dienste zur normalen Leistung zurückkehren.

3. 23. Juli 2026 um 22:00 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

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

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

3. 10. Juli 2026 um 18:08 UTCresolved

   This incident has been resolved.

1. 22. Juni 2026 um 13:43 UTCinvestigating

   We are currently investigating this issue.

2. 22. Juni 2026 um 14:08 UTCidentified

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

3. 22. Juni 2026 um 17:13 UTCmonitoring

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

4. 22. Juni 2026 um 18:39 UTCresolved

   This incident has been resolved.

1. 20. Juni 2026 um 22:00 UTCinvestigating

   We are currently investigating this issue.

2. 20. Juni 2026 um 23:39 UTCmonitoring

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

3. 21. Juni 2026 um 04:01 UTCresolved

   This incident has been resolved.

1. 17. Juni 2026 um 17:30 UTCinvestigating

   We are currently investigating this issue.

2. 17. Juni 2026 um 17:38 UTCidentified

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

3. 17. Juni 2026 um 17:43 UTCmonitoring

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

4. 17. Juni 2026 um 17:58 UTCresolved

   This incident has been resolved.

1. 8. Juni 2026 um 18:23 UTCidentified

   We have identified the cause and are deploying a fix.

2. 8. Juni 2026 um 19:33 UTCresolved

   This incident has been resolved.

1. 20. Mai 2026 um 14:04 UTCidentified

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

2. 20. Mai 2026 um 17:52 UTCmonitoring

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

3. 21. Mai 2026 um 04:17 UTCresolved

   This incident has been resolved.

1. 11. Mai 2026 um 06:17 UTCinvestigating

   We are currently investigating this issue.

2. 11. Mai 2026 um 06:17 UTCidentified

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

3. 11. Mai 2026 um 08:26 UTCmonitoring

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

4. 11. Mai 2026 um 08:29 UTCresolved

   This incident has been resolved.

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

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

3. 8. Mai 2026 um 10:13 UTCresolved

   This incident has been resolved.

1. 27. April 2026 um 10:35 UTCidentified

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

2. 27. April 2026 um 11:33 UTCmonitoring

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

3. 27. April 2026 um 11:43 UTCresolved

   This incident has been resolved.

1. 17. April 2026 um 07:16 UTCinvestigating

   We are currently investigating this issue.

2. 17. April 2026 um 14:04 UTCmonitoring

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

3. 18. April 2026 um 02:35 UTCresolved

   This incident has been resolved.

1. 14. April 2026 um 06:19 UTCinvestigating

   We are currently investigating this issue.

2. 14. April 2026 um 06:45 UTCresolved

   This incident has been resolved.

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

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

3. 4. April 2026 um 19:04 UTCresolved

   This incident has been resolved.

1. 24. März 2026 um 07:21 UTCinvestigating

   We are currently investigating this issue.

2. 24. März 2026 um 08:38 UTCidentified

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

3. 24. März 2026 um 19:38 UTCmonitoring

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

4. 26. März 2026 um 17:24 UTCresolved

   This incident has been resolved.

1. 23. März 2026 um 14:04 UTCinvestigating

   We are currently investigating this issue.

2. 23. März 2026 um 18:51 UTCmonitoring

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

3. 23. März 2026 um 20:37 UTCresolved

   This incident has been resolved.

1. 22. März 2026 um 18:11 UTCmonitoring

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

2. 22. März 2026 um 23:22 UTCresolved

   This incident has been resolved.

1. 19. März 2026 um 15:53 UTCidentified

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

2. 19. März 2026 um 21:51 UTCmonitoring

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

3. 20. März 2026 um 18:35 UTCresolved

   This incident has been resolved.

1. 5. März 2026 um 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. März 2026 um 21:56 UTCinvestigating

   We are currently investigating this issue.

2. 5. März 2026 um 22:33 UTCresolved

   This incident has been resolved.