Wiz had 47 outages in the last 2 years totaling 466h 52m of downtime — averaging 1.9 incidents per month.
There were 47 Wiz outages since September 1, 2025 totaling 466h 52m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating this issue.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are investigating service degradation in US27 that may affect access to vulnerability findings, cloud resources, CSPM, and secrets, and are working with our cloud provider to restore service.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Affected data centers: US2, US6, US10, US14, US18, US21, US24, US27, US33, US38, US41, US44, US46, US49, US52, US56, US59, and US62. We are experiencing a service degradation affecting customers hosted in multiple US data centers. Customers may encounter slow or unsuccessful loading of some pages, API errors, and delays in data ingestion and processing. This is related to an ongoing Microsoft Azure service disruption. We are actively working to restore service and will provide further updates as they become available.
The upstream Microsoft Azure service disruption has been resolved, and service availability has been restored. Data ingestion and detection are operational, but some customers may continue to experience delays while processing catches up. We are monitoring the recovery and working to ensure all services return to normal performance.
This incident has been resolved.
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.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We have identified the cause and are deploying a fix.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are monitoring an upstream AWS infrastructure issue 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.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
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.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
The issue will be fully resolved once AWS restores the affected services in the region. We are actively monitoring the situation and closely tracking AWS status updates. In parallel, our team continues working internally with impacted users to minimize disruption and restore functionality within our platform wherever possible. We will provide further updates as soon as AWS confirms full service restoration. AWS status: https://health.aws.amazon.com/health/status?path=service-history
We are continuing to investigate this issue.
This incident has been resolved.
Some customers may experience delays in Serverless findings. We are actively working on mitigation and will share updates as we progress.
The issue has been identified and a fix is being implemented.
This incident has been resolved.