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 172 Wiz outages since January 2021. The 56 outages from the last 12 months are summarized below, with incident details, duration, and resolution information.

Minor May 20, 2026

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

Detected May 20, 2026 10:04 AM EDT · Resolved May 21, 2026 12:20 AM EDT · Duration about 14 hours

Wiz Sensor and Wiz Defend on prod-us54 experienced delayed data ingestion of approximately one hour, affecting the Wiz Defend component for 14.3 hours. The team identified the root cause and implemented a fix. The incident was resolved after a monitoring period to ensure the fix was effective.

Minor May 11, 2026

May 2026: Degraded performance of Security Graph in DC US48

Detected May 11, 2026 2:17 AM EDT · Resolved May 11, 2026 4:29 AM EDT · Duration about 2 hours

Wiz experienced degraded performance of their Security Graph in datacenter US48, affecting the Portal and Ingestion components. The issue was identified and resolved within 2.2 hours through implementation of a fix.

Minor May 8, 2026

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

Detected May 8, 2026 3:06 AM EDT · Resolved May 8, 2026 6:13 AM EDT · Duration about 3 hours

An upstream AWS EC2 API issue in the us-east-1 region caused delays in Wiz's backend processing and portal search functionality for 3.1 hours. Users experienced delays in data updates, search results, notifications, automation triggers, and data synchronization due to impacted asynchronous queue processing. The incident was resolved after AWS fixed the infrastructure issue and Wiz confirmed service recovery.

Major April 27, 2026

April 2026: Intermittent login failures affecting prod-eu24 only

Detected Apr 27, 2026 6:35 AM EDT · Resolved Apr 27, 2026 7:46 AM EDT · 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 3:16 AM EDT · Resolved Apr 17, 2026 10:48 PM EDT · 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 14, 2026

April 2026: Intermittent Performance Issues Affecting EU4

Detected Apr 14, 2026 2:19 AM EDT · Resolved Apr 14, 2026 2:47 AM EDT · 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 11:32 AM EDT · Resolved Apr 4, 2026 3:05 PM EDT · 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 3:21 AM EDT · Resolved Mar 26, 2026 1:25 PM EDT · 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 10:04 AM EDT · Resolved Mar 23, 2026 4:39 PM EDT · 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 2:11 PM EDT · Resolved Mar 22, 2026 7:25 PM EDT · 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.