Wiz Status

All Systems Operational

About This Site

This is Wiz's status page, where you can get updates on how our systems are doing. If there are interruptions to service, we will post a note here.

As always, if you are experiencing any issues with Wiz, don't hesitate to get in touch with us at support@wiz.io and we'll get back to you as soon as we can.

Uptime over the past 90 days. View historical uptime.
Authentication Operational
90 days ago
100.0 % uptime
Today
Portal Operational
Ingestion Operational
Wiz Defend Operational
Sensor Operational
Wiz CLI Operational
Wiz Code Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Jan 29, 2026

No incidents reported today.

Jan 28, 2026

No incidents reported.

Jan 27, 2026

No incidents reported.

Jan 26, 2026

No incidents reported.

Jan 25, 2026

No incidents reported.

Jan 24, 2026
Investigating Issue with IP-ASO Based Threat Rules
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 affected detections are operating normally again.
Jan 24, 01:15 UTC
Update - 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.
Jan 23, 19:48 UTC
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 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.
Jan 23, 18:35 UTC
Jan 23, 2026
Jan 22, 2026

No incidents reported.

Jan 21, 2026

No incidents reported.

Jan 20, 2026

No incidents reported.

Jan 19, 2026

No incidents reported.

Jan 18, 2026

No incidents reported.

Jan 17, 2026

No incidents reported.

Jan 16, 2026

No incidents reported.

Jan 15, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage