Wiz
Apps and SaaS. Source: Wiz status page.
- Incidents, last 90 days
- 5
- Median duration
- 3h 28m
- p95 duration
- 8d 1h
- Naming an upstream provider
- 40%
- With a postmortem on the status page
- 0%
What failed, last 90 days
| The text does not say enough to tell | 2 |
| A provider or third-party service this vendor depends on failed | 2 |
| Data delayed, stale, lost or corrupted, or needing replay after recovery | 1 |
Tagged by claude-haiku-5-5 from each incident's updates. See the methodology.
Incidents per month
All recorded incidents
We are investigating an issue affecting the security graph and dependent features in prod-US38.
Affected: Portal, Ingestion
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are currently investigating this issue.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Wiz's status page.
We are investigating an issue causing GitHub pull request scans to remain pending, potentially blocking merges where Wiz checks are required.
Affected: Wiz Code
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
Names an upstream provider: GitHub.
-
investigating
We are currently investigating this issue.
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Wiz's status page.
Service degradation in US27
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
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.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Wiz's status page.
We are investigating an issue causing delays in processing and displaying vulnerability findings in the Security Graph for some customers.
Affected: Portal, Ingestion
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We are currently investigating this issue.
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Wiz's status page.
We are investigating an issue affecting some Wiz services for tenants hosted in the AWS us-west-2 region, related to an ongoing AWS service disruption
Affected: Portal
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
Names an upstream provider: AWS.
-
investigating
We are investigating an issue affecting some Wiz services for tenants hosted in AWS us-west-2. This appears related to an ongoing AWS service disruption https://health.aws.amazon.com/health/status
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Wiz's status page.
Portal and API Service Degradation Across Multiple US Data Centers
Affected: Portal, Ingestion, Wiz Defend
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
Names an upstream provider: Azure.
Started during Azure: Network connectivity – Issues accessing resources in West US.
-
investigating
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...
-
monitoring
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...
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Wiz's status page.
Elevated error rates due to an upstream dependency
Affected: Ingestion
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
investigating
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:...
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Wiz's status page.
We are currently investigating an issue affecting Tenable Cloud integrations, where asset fetching may not complete for some customers, and are working with the relevant teams to restore normal operation.
Affected: Portal, Ingestion
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are currently investigating this issue.
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Wiz's status page.
We are currently seeing delays and possible data loss in sensor ATM ingestion, including RED ingestion and VIR.
Affected: Sensor
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We are currently investigating this issue.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Wiz's status page.
Intermittent login failures
Affected: Authentication, Portal
Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We are currently investigating this issue.
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Wiz's status page.
Starting at 08:30 UTC, a subset of audit events may not have been recorded as expected.
Affected: Portal, Ingestion
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
identified
We have identified the cause and are deploying a fix.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Wiz's status page.
Wiz Sensor and Wiz Defend on prod-us54 may be experiencing delayed data ingestion of approximately one hour. Our team is investigating and working to restore normal processing.
Affected: Wiz Defend
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Wiz's status page.
Degraded performance of Security Graph in DC US48
Affected: Portal, Ingestion
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are currently investigating this issue.
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Wiz's status page.
AWS infrastructure issues in us-east-1 are currently impacting our backend processing and portal search functionality. Users may see delays in data updates and search results while AWS works on a resolution
Affected: Portal, Ingestion
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
Names an upstream provider: AWS.
-
investigating
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...
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Wiz's status page.
Intermittent login failures affecting prod-eu24 only
Affected: Authentication, Portal
Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Wiz's status page.
The GitHub streaming integration has stopped sending events.
Affected: Wiz Defend
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
Names an upstream provider: GitHub.
-
investigating
We are currently investigating this issue.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Wiz's status page.
Intermittent Performance Issues Affecting EU4
Affected: Portal
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are currently investigating this issue.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Wiz's status page.
Some customers may see critical issues created from incorrectly classified vulnerability findings for CVE-2026-4800, CVE-2026-33937, CVE-2026-33938, and CVE-2026-33940
Affected: Portal
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
identified
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.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Wiz's status page.
We are investigating an issue causing false positive issues on controls wc-id-3088, wc-id-3089, wc-id-3090, wc-id-3091, and wc-id-3092 related to leaked cloud keys. These issues can be ignored and do not require investigation at this time.
Affected: Portal
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We are currently investigating this issue.
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Wiz's status page.
We are investigating intermittent login issues affecting some single sign-on flows, where a subset of users may experience repeated redirects or delays when signing in.
Affected: Authentication
Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We are currently investigating this issue.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Wiz's status page.
We are experiencing delays in IAM event processing in prod-us54, which may cause delays in newly created or updated events for customers in this data center.
Affected: Portal, Ingestion
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Wiz's status page.
Users in US72 may experience delays in updates and deletions for vulnerability findings in the graph.
Affected: Portal, Ingestion
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Wiz's status page.
AWS me-central-1 Service Disruption
Affected: Authentication, Portal, Ingestion, Wiz Defend, Sensor, Wiz CLI, Wiz Code
Names an upstream provider: AWS.
-
investigating
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:...
Excerpts are shortened. Read the full incident on Wiz's status page.
We are currently investigating an issue affecting email delivery from our production environment. Due to a temporary restriction on our email service provider account, some verification emails may not be delivered.
Affected: Portal
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We are currently investigating this issue.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Wiz's status page.
AWS service disruptions affecting the me-central-1 region, affected DCs: prod-me1
Affected: Authentication, Portal, Ingestion, Wiz Defend, Sensor, Wiz CLI, Wiz Code
Failure mode: A zone, region or data center became unavailable. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
Names an upstream provider: AWS.
-
investigating
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...
-
investigating
We are continuing to investigate this issue.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Wiz's status page.
We are investigating increased processing latency affecting Serverless scan results in several data centers - prod-us38, prod-us24, prod-us43, prod-us8, and prod-eu16.
Affected: Portal, Ingestion
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
Some customers may experience delays in Serverless findings. We are actively working on mitigation and will share updates as we progress.
-
identified
The issue has been identified and a fix is being implemented.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Wiz's status page.
AWS service disruptions affecting the me-central-1 region, affected DCs: prod-me1
Affected: Authentication, Portal, Ingestion, Wiz Defend, Sensor, Wiz CLI, Wiz Code
Failure mode: A zone, region or data center became unavailable. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
Names an upstream provider: AWS.
Started during AWS: Multiple services (UAE): Region Availability.
-
monitoring
See AWS status: https://health.aws.amazon.com/health/status?path=service-history
-
investigating
AWS Impact has expanded to include additional availability zones and core services within the ME-CENTRAL-1 region. Affected DCs: prod-me1 Additional information can be found on the AWS status page - https://health.aws.amazon.com/health/status
-
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...
Excerpts are shortened. Read the full incident on Wiz's status page.
AWS service disruptions affecting the me-central-1 region, effected DC's: prod-me1
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
Names an upstream provider: AWS.
Started during AWS: Multiple services (UAE): Region Availability.
-
investigating
We are currently investigating this issue.
-
investigating
See AWS status: https://health.aws.amazon.com/health/status?path=service-history
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Wiz's status page.
Intermittent login failures affecting prod-us54 only
Affected: Authentication, Portal
Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We are currently investigating this issue.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Wiz's status page.
Terraform Run Task scans may fail for some customers due to a recent update. Code/TF scan results might not be produced during this time. We are actively working on a hotfix to restore normal service.
Affected: Wiz Code
Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Wiz's status page.
Investigating a gap in cloud storage log events (AWS S3, Azure Storage, GCP Cloud Storage) from Feb 4–Feb 9
Affected: Wiz Defend
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
Names an upstream provider: AWS, Azure, Google Cloud.
-
investigating
We are currently investigating this issue.
-
resolved
ingestion is restored and we are evaluating options to recover missing data.
Excerpts are shortened. Read the full incident on Wiz's status page.
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)
Affected: Ingestion, Wiz Defend
Failure mode: A zone, region or data center became unavailable. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
Names an upstream provider: Azure.
Started during Azure: Power event impacting multiple services – West US.
-
monitoring
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)
-
monitoring
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...
-
monitoring
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...
-
monitoring
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...
-
monitoring
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...
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Wiz's status page.
Intermittent login failures affecting prod-eu24 only
Affected: Authentication, Portal
Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We are currently investigating this issue.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Wiz's status page.
Intermittent login failures affecting prod-us3 only
Affected: Authentication, Portal
Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We are currently investigating this issue.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Wiz's status page.
Investigating Issue with IP-ASO Based Threat Rules
Affected: Wiz Defend
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
Names an upstream provider: AWS, Azure, Google Cloud.
-
monitoring
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...
-
monitoring
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...
-
resolved
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...
Excerpts are shortened. Read the full incident on Wiz's status page.
Degraded performance of Security Graph in DC US10 + US19
Affected: Portal, Ingestion
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Wiz's status page.
Policy updates were skipped due to a technical issue, causing a possible spike in opened issues for control wc-id-140 after a controls logic change
Affected: Portal
Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
Rollback hotfix in progress, all issues should be resolved by tomorrow.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Wiz's status page.
Threats Page and Cloud Events Explorer Intermittent Loading Failures
Affected: Portal
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are currently investigating this issue.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Wiz's status page.
Intermittent login failures for some users due to email verification issues, sign ins via the IdP are not impacted.
Affected: Authentication
Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We are currently investigating this issue.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Wiz's status page.
Potential impact to Wiz Code pull request scanning
Affected: Wiz Code
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are currently investigating this issue.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Wiz's status page.
Potential AWS Outage Impacting Multiple Wiz Services
Affected: Portal
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
Names an upstream provider: AWS.
-
investigating
We are currently investigating this issue.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Wiz's status page.
Ingestion Delay across multiple datacenters - Wiz Defend, Sensor
Affected: Wiz Defend, Sensor
Failure mode: A zone, region or data center became unavailable. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
monitoring
We’re currently experiencing delays in a limited number of data centers due to an issue in the underlying infrastructure. The affected regions are being transitioned to backup infrastructure in their respective backup regions.
-
monitoring
We are continuing to monitor for any further issues.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Wiz's status page.
Intermittent login failures across multiple datacenters, with additional service degradations, linked to an ongoing AWS us-east-1 incident.
Affected: Authentication, Portal, Ingestion, Wiz Defend, Sensor, Wiz CLI, Wiz Code
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
Names an upstream provider: AWS.
-
investigating
We are currently investigating this issue.
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Wiz's status page.
AWS Outage in US-East-1 Impacting Multiple Wiz Services
Affected: Authentication, Portal, Ingestion, Wiz Defend, Sensor, Wiz CLI, Wiz Code
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
Names an upstream provider: AWS.
-
investigating
We are currently experiencing a login outage affecting all data centers hosted in the US-East-1 region. This issue is caused by an ongoing AWS incident, where multiple AWS services in the region are reporting increased error rates and latency.
-
investigating
We are continuing to investigate this issue.
-
investigating
We are continuing to investigate this issue.
-
investigating
We are continuing to investigate this issue.
-
identified
We are continuing to monitor the ongoing AWS incident affecting services in the US-East-1 region. For more information and the latest updates from AWS, please visit AWS Service Health Dashboard (https://health.aws.amazon.com).
-
identified
Last update from AWS: [02:01 AM PDT] We have identified a potential root cause for error rates for the DynamoDB APIs in the US-EAST-1 Region. Based on our investigation, the issue appears to be related to DNS resolution of the DynamoDB API endpoint in US-EAST-1. We are working...
-
monitoring
We are seeing signs of recovery from the ongoing AWS incident impacting the US-East-1 region. We will continue to monitor the situation closely and provide an update once full recovery is confirmed. For more details from AWS, visit https://health.aws.amazon.com/.
-
monitoring
We are continuing to monitor for any further issues.
-
monitoring
We are continuing to monitor for any further issues.
-
monitoring
We continue to see improvements across our services as AWS recovers from the US-East-1 incident. Our systems are steadily returning to normal operation, though some residual impact may remain. We are continuing to monitor closely and will provide another update once full...
-
monitoring
We are continuing to monitor closely and will provide another update once full recovery is confirmed.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Wiz's status page.
Intermittent Performance Issues Affecting EU4
Affected: Portal
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are currently investigating this issue.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Wiz's status page.
Isolated Data Ingestion Delay in the US
Affected: Ingestion
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
identified
We are currently investigating an issue causing a data ingestion delay. This is impacting data ingestion for several object types in the following US data centers: US24, US45, and US65.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
monitoring
We are continuing to monitor for any further issues.
-
monitoring
We are continuing to monitor for any further issues.
-
monitoring
The data ingestion delay has been mitigated for all impacted data centers except US45.
-
monitoring
We are continuing to monitor for any further issues.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Wiz's status page.
GitHub Threat Detections
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
Names an upstream provider: GitHub.
-
resolved
Today, some Wiz Defend customers saw Threats generated by two GitHub threat-detection rules due to a false-positive condition. We identified the root cause and fixed both rules. You can safely ignore these Threats and bulk-resolve them as false positives in the Wiz portal....
Excerpts are shortened. Read the full incident on Wiz's status page.
JWT validation errors are impacting multiple Wiz deployments, including the Wiz Sensor, Wiz Admission Controller, and Wiz Outpost.
Affected: Authentication
Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
investigating
We are currently investigating this issue.
-
identified
The issue has been identified and a fix is being implemented.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Wiz's status page.
Login Issues – Impacting Certain SSO and Wiz Accounts
Affected: Authentication
Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
identified
The issue has been identified and a fix is being implemented.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Wiz's status page.
Login Issues Affecting US8
Affected: Authentication
Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We are currently investigating this issue.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Wiz's status page.