Wiz had 50 outages in the last 2 years totaling 271h 21m of downtime — averaging 2.1 incidents per month.
There were 50 Wiz outages since July 24, 2025 totaling 271h 21m of downtime. Each is summarised below — incident details, duration, and resolution information.
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.
We are currently investigating this issue.
See AWS status: https://health.aws.amazon.com/health/status?path=service-history
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.
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.
ingestion is restored and we are evaluating options to recover missing data.
We are monitoring an ongoing Microsoft Azure service degradation in West US. Some operations may be delayed or intermittently impacted. (Azure Status: https://azure.status.microsoft/en-us/status)
We are continuing to monitor and investigate an ongoing Microsoft Azure degradation in West US. Current impact is limited to a subset of DCs. Wiz Defend: Data exploration and Raw Events may be unavailable in prod-us24, prod-us27, prod-us38, prod-us46. Dashboards and detections remain functional; correlation-based detections may be delayed. Wiz Backend: Potential impact in prod-us14, prod-us41, prod-us56. Issues in prod-us2, prod-us6, prod-us18 were mitigated. We are still assessing the exact impact and continue to investigate, updates will follow.
Current status, Wiz Defend: We are seeing additional clusters in a degraded state, including us2 and us41. To maintain stability, we are shifting traffic and workloads to our DR/backup environment, including BE. us10 is currently fluctuating, we are planning to shift it to DR as well as a precaution. There is no customer impact to report at this time. BE is currently mitigated via two DR clusters, us41 and us52. We will continue to investigate and monitor closely, and we will share further updates as they become available.
Current Status: Some customers may experience portal pages failing to load in the following data centers: prod-us24, prod-us27, prod-us38, prod-us46. The issue is related to metadata retrieval when failover is enabled. Correlation-based detections may be delayed. A hotfix is currently being deployed to restore full functionality.
Status Update: The portal is operating normally across all data centers. Some correlation results may still be delayed; the backlog is actively catching up. Wiz Defend: We are currently operating on a backup region, so event visibility is limited to the last 12 hours. Some correlation results may still be delayed; the backlog is actively catching up. Once the primary environment completes backfill and closes the remaining gap, we will transition back to the primary region. Impacted data centers: us2, us10, us24, us27, us38, us41, us46.
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 addressing a surge in detections related to IP-ASO rules (for example, activity outside AWS, Azure, or GCP). This was triggered by changes in ASO naming conventions. Actions Taken: • 16:30 UTC (Completed): Impacted detection rules have been suspended to prevent further false positive alerts. • 17:15 UTC (In Progress): Our team is currently investigating the root cause of the ASO name changes and identifying all affected variations. • Ongoing (In Progress): We are developing a logic update to account for the new ASO names. The rules will be resumed once the update is validated and released.
Fix Deployment in Progress Actions Taken: • 17:30 UTC (Completed): Suspended the impacted detection rules to prevent additional false positive alerts. • 20:00 UTC (Completed): Confirmed the root cause as an upstream ASN data update that changed ASO naming and triggered detections. • Ongoing (In Progress): Deploying a hotfix to update detection logic and align with the updated naming.
We identified an issue that caused an increase in false alerts from a subset of Threat Detection Rules. To prevent additional noise, we temporarily paused the affected alerting while we confirmed the cause and deployed a fix. The hotfix has now been fully deployed, and the affected detections are operating normally again.
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.
Rollback hotfix in progress, all issues should be resolved by tomorrow.
This incident has been resolved.