Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

Wiz Outage History

Every past Wiz outage tracked by IsDown, with detection times, duration, and resolution details.

There were 169 Wiz outages since January 2021. The 55 outages from the last 12 months are summarized below, with incident details, duration, and resolution information.

Major April 27, 2026

April 2026: Intermittent login failures affecting prod-eu24 only

Detected Apr 27, 2026 3:35 AM PDT · Resolved Apr 27, 2026 4:46 AM PDT · Duration about 1 hour

Wiz experienced intermittent login failures specifically affecting the prod-eu24 environment, impacting both authentication services and portal access for users in that region. The incident lasted 1.2 hours before being resolved with an implemented fix. The issue was identified and remediated in a staged approach, with monitoring confirming the resolution.

Minor April 17, 2026

April 2026: The GitHub streaming integration has stopped sending events.

Detected Apr 17, 2026 12:16 AM PDT · Resolved Apr 17, 2026 7:48 PM PDT · Duration about 20 hours

The GitHub streaming integration in Wiz Defend stopped sending events, preventing the service from receiving GitHub-related security data. The issue affected the Wiz Defend component for approximately 19.3 hours. A fix was implemented and monitored before the incident was fully resolved.

Minor April 13, 2026

April 2026: Intermittent Performance Issues Affecting EU4

Detected Apr 13, 2026 11:19 PM PDT · Resolved Apr 13, 2026 11:47 PM PDT · Duration 28 minutes

Wiz experienced intermittent performance issues affecting the EU4 region's Portal component for 28 minutes. The incident was resolved after investigation and monitoring confirmed normal service operations were restored.

Minor April 3, 2026

April 2026: 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

Detected Apr 3, 2026 8:32 AM PDT · Resolved Apr 4, 2026 12:05 PM PDT · Duration 1 day

Wiz incorrectly classified vulnerability findings for four specific CVEs (CVE-2026-4800, CVE-2026-33937, CVE-2026-33938, and CVE-2026-33940), causing some customers to see critical issues created from these misclassified findings in the Portal. The issue was resolved after 27.6 hours by implementing a fix and completing subsequent scans to correct the affected finding classifications.

Minor March 24, 2026

March 2026: 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.

Detected Mar 24, 2026 12:21 AM PDT · Resolved Mar 26, 2026 10:25 AM PDT · Duration 2 days

Wiz experienced an issue causing false positive alerts on five specific controls (wc-id-3088 through wc-id-3092) related to leaked cloud keys, affecting the Portal component. The false positives did not require customer investigation and could be safely ignored. The issue was identified and fixed within approximately 58 hours, with monitoring confirming the resolution.

Minor March 23, 2026

March 2026: 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.

Detected Mar 23, 2026 7:04 AM PDT · Resolved Mar 23, 2026 1:39 PM PDT · Duration about 7 hours

Wiz experienced intermittent login issues affecting single sign-on flows, where users encountered repeated redirects or delays when attempting to sign in. The authentication component was impacted for 6.6 hours. The issue was resolved after implementing a fix and monitoring the results.

Minor March 22, 2026

March 2026: 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.

Detected Mar 22, 2026 11:11 AM PDT · Resolved Mar 22, 2026 4:25 PM PDT · Duration about 5 hours

Wiz experienced delays in IAM event processing in the prod-us54 data center, causing delays in newly created or updated events for customers in that region. The incident affected the Portal and Ingestion components for 5.2 hours. A fix was implemented and the incident was resolved after monitoring confirmed the solution was effective.

Minor March 19, 2026

March 2026: Users in US72 may experience delays in updates and deletions for vulnerability findings in the graph.

Detected Mar 19, 2026 8:53 AM PDT · Resolved Mar 20, 2026 11:37 AM PDT · Duration 1 day

Users in the US72 region experienced delays in vulnerability finding updates and deletions within the Wiz graph, affecting both the Portal and Ingestion components. The incident lasted 26.7 hours before being resolved. A fix was implemented and monitored before the issue was fully resolved.

Minor March 5, 2026

March 2026: 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.

Detected Mar 5, 2026 1:56 PM PST · Resolved Mar 5, 2026 2:34 PM PST · Duration 38 minutes

Wiz experienced an email delivery issue affecting their Portal component due to temporary restrictions on their email service provider account. Verification emails were not being delivered to users during the incident. The issue was resolved after 38 minutes of investigation.

Minor March 3, 2026

March 2026: AWS service disruptions affecting the me-central-1 region, affected DCs: prod-me1

Detected Mar 3, 2026 9:17 AM PST · Resolved Mar 5, 2026 2:58 PM PST · Duration 2 days

AWS service disruptions in the me-central-1 region caused a 53.7-hour outage affecting Wiz's core components including Authentication, Portal, Ingestion, Wiz Defend, Sensor, Wiz CLI, and Wiz Code in the prod-me1 datacenter. Wiz's team worked internally with impacted users to minimize disruption while monitoring AWS status updates. The incident was resolved once AWS restored their affected services in the region.