Jun <var data-var='date'>22</var>, <var data-var='time'>18:39</var> UTC Resolved - This incident has been resolved. Jun <var data-var='date'>22</var>, <var data-var='time'>17:13</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun <var data-var='date'>22</var>, <var data-var='time'>14:08</var> UTC Identified - The issue has been identified and a fix is being implemented. Jun <var data-var='date'>22</var>, <var data-var='time'>13:43</var> UTC Investigating - We are currently investigating this issue.

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.

Jun <var data-var='date'>21</var>, <var data-var='time'>04:01</var> UTC Resolved - This incident has been resolved. Jun <var data-var='date'>20</var>, <var data-var='time'>23:39</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun <var data-var='date'>20</var>, <var data-var='time'>22:00</var> UTC Investigating - We are currently investigating this issue.

We are currently seeing delays and possible data loss in sensor ATM ingestion, including RED ingestion and VIR.

Jun <var data-var='date'>17</var>, <var data-var='time'>17:58</var> UTC Resolved - This incident has been resolved. Jun <var data-var='date'>17</var>, <var data-var='time'>17:43</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun <var data-var='date'>17</var>, <var data-var='time'>17:38</var> UTC Identified - The issue has been identified and a fix is being implemented. Jun <var data-var='date'>17</var>, <var data-var='time'>17:30</var> UTC Investigating - We are currently investigating this issue.

Intermittent login failures

Jun <var data-var='date'> 8</var>, <var data-var='time'>19:33</var> UTC Resolved - This incident has been resolved. Jun <var data-var='date'> 8</var>, <var data-var='time'>18:15</var> UTC Identified - We have identified the cause and are deploying a fix.

Starting at 08:30 UTC, a subset of audit events may not have been recorded as expected.

May <var data-var='date'>21</var>, <var data-var='time'>04:17</var> UTC Resolved - This incident has been resolved. May <var data-var='date'>20</var>, <var data-var='time'>17:52</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. May <var data-var='date'>20</var>, <var data-var='time'>14:04</var> UTC Identified - The issue has been identified and a fix is being implemented.

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.

May <var data-var='date'>11</var>, <var data-var='time'>08:29</var> UTC Resolved - This incident has been resolved. May <var data-var='date'>11</var>, <var data-var='time'>08:26</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. May <var data-var='date'>11</var>, <var data-var='time'>06:17</var> UTC Identified - The issue has been identified and a fix is being implemented. May <var data-var='date'>11</var>, <var data-var='time'>06:17</var> UTC Investigating - We are currently investigating this issue.

Degraded performance of Security Graph in DC US48

May <var data-var='date'> 8</var>, <var data-var='time'>10:13</var> UTC Resolved - This incident has been resolved. May <var data-var='date'> 8</var>, <var data-var='time'>10:07</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. May <var data-var='date'> 8</var>, <var data-var='time'>07:06</var> UTC 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 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.

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

Apr <var data-var='date'>27</var>, <var data-var='time'>11:43</var> UTC Resolved - This incident has been resolved. Apr <var data-var='date'>27</var>, <var data-var='time'>11:33</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Apr <var data-var='date'>27</var>, <var data-var='time'>10:35</var> UTC Identified - The issue has been identified and a fix is being implemented.

Intermittent login failures affecting prod-eu24 only

Apr <var data-var='date'>18</var>, <var data-var='time'>02:35</var> UTC Resolved - This incident has been resolved. Apr <var data-var='date'>17</var>, <var data-var='time'>14:04</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Apr <var data-var='date'>17</var>, <var data-var='time'>07:16</var> UTC Investigating - We are currently investigating this issue.

The GitHub streaming integration has stopped sending events.

Apr <var data-var='date'>14</var>, <var data-var='time'>06:45</var> UTC Resolved - This incident has been resolved. Apr <var data-var='date'>14</var>, <var data-var='time'>06:19</var> UTC Investigating - We are currently investigating this issue.

Intermittent Performance Issues Affecting EU4

Apr <var data-var='date'> 4</var>, <var data-var='time'>19:04</var> UTC Resolved - This incident has been resolved. Apr <var data-var='date'> 3</var>, <var data-var='time'>16:47</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Apr <var data-var='date'> 3</var>, <var data-var='time'>15:32</var> UTC 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.

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

Mar <var data-var='date'>26</var>, <var data-var='time'>17:24</var> UTC Resolved - This incident has been resolved. Mar <var data-var='date'>24</var>, <var data-var='time'>19:38</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Mar <var data-var='date'>24</var>, <var data-var='time'>08:38</var> UTC Identified - The issue has been identified and a fix is being implemented. Mar <var data-var='date'>24</var>, <var data-var='time'>07:21</var> UTC Investigating - We are currently investigating this issue.

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.

Mar <var data-var='date'>23</var>, <var data-var='time'>20:37</var> UTC Resolved - This incident has been resolved. Mar <var data-var='date'>23</var>, <var data-var='time'>18:51</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Mar <var data-var='date'>23</var>, <var data-var='time'>14:04</var> UTC Investigating - We are currently investigating this issue.

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.

Mar <var data-var='date'>22</var>, <var data-var='time'>23:22</var> UTC Resolved - This incident has been resolved. Mar <var data-var='date'>22</var>, <var data-var='time'>18:11</var> UTC Monitoring - A fix has been implemented and we are monitoring the results.

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.

Mar <var data-var='date'>20</var>, <var data-var='time'>18:35</var> UTC Resolved - This incident has been resolved. Mar <var data-var='date'>19</var>, <var data-var='time'>21:51</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Mar <var data-var='date'>19</var>, <var data-var='time'>15:53</var> UTC Identified - The issue has been identified and a fix is being implemented.

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

Mar <var data-var='date'> 5</var>, <var data-var='time'>22:56</var> UTC 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: https://health.aws.amazon.com/health/status Affected Wiz DC: prod-me1

AWS me-central-1 Service Disruption

Mar <var data-var='date'> 5</var>, <var data-var='time'>22:54</var> UTC Resolved - This incident has been resolved. Mar <var data-var='date'> 5</var>, <var data-var='time'>22:54</var> UTC Update - We are continuing to investigate this issue. Mar <var data-var='date'> 3</var>, <var data-var='time'>17:17</var> UTC 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 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

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

Mar <var data-var='date'> 5</var>, <var data-var='time'>22:33</var> UTC Resolved - This incident has been resolved. Mar <var data-var='date'> 5</var>, <var data-var='time'>21:56</var> UTC Investigating - We are currently investigating this issue.

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.

Mar <var data-var='date'> 3</var>, <var data-var='time'>16:46</var> UTC Resolved - This incident has been resolved. Mar <var data-var='date'> 3</var>, <var data-var='time'>16:00</var> UTC Identified - The issue has been identified and a fix is being implemented. Mar <var data-var='date'> 3</var>, <var data-var='time'>15:52</var> UTC Investigating - Some customers may experience delays in Serverless findings. We are actively working on mitigation and will share updates as we progress.

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.

Mar <var data-var='date'> 3</var>, <var data-var='time'>09:15</var> UTC 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 Mar <var data-var='date'> 2</var>, <var data-var='time'>07:12</var> UTC 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 Mar <var data-var='date'> 1</var>, <var data-var='time'>20:42</var> UTC Monitoring - See AWS status: https://health.aws.amazon.com/health/status?path=service-history

Mar <var data-var='date'> 1</var>, <var data-var='time'>20:29</var> UTC Resolved - This incident has been resolved. Mar <var data-var='date'> 1</var>, <var data-var='time'>19:17</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Mar <var data-var='date'> 1</var>, <var data-var='time'>13:08</var> UTC Update - See AWS status: https://health.aws.amazon.com/health/status?path=service-history Mar <var data-var='date'> 1</var>, <var data-var='time'>13:06</var> UTC Investigating - We are currently investigating this issue.

AWS service disruptions affecting the me-central-1 region, effected DC's: prod-me1

Feb <var data-var='date'>15</var>, <var data-var='time'>13:35</var> UTC Resolved - This incident has been resolved. Feb <var data-var='date'>15</var>, <var data-var='time'>12:08</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Feb <var data-var='date'>15</var>, <var data-var='time'>11:51</var> UTC Investigating - We are currently investigating this issue.

Intermittent login failures affecting prod-us54 only

Feb <var data-var='date'>11</var>, <var data-var='time'>17:07</var> UTC Resolved - This incident has been resolved. Feb <var data-var='date'>11</var>, <var data-var='time'>17:00</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Feb <var data-var='date'>11</var>, <var data-var='time'>10:00</var> UTC Identified - The issue has been identified and a fix is being implemented.

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.

Feb <var data-var='date'> 9</var>, <var data-var='time'>14:30</var> UTC Resolved - ingestion is restored and we are evaluating options to recover missing data. Feb <var data-var='date'> 9</var>, <var data-var='time'>14:30</var> UTC Investigating - We are currently investigating this issue.

Investigating a gap in cloud storage log events (AWS S3, Azure Storage, GCP Cloud Storage) from Feb 4–Feb 9

Feb <var data-var='date'> 8</var>, <var data-var='time'>03:45</var> UTC Resolved - This incident has been resolved. Feb <var data-var='date'> 7</var>, <var data-var='time'>20:18</var> UTC Update - 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. Feb <var data-var='date'> 7</var>, <var data-var='time'>18:49</var> UTC Update - 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. Feb <var data-var='date'> 7</var>, <var data-var='time'>18:03</var> UTC Update - 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. Feb <var data-var='date'> 7</var>, <var data-var='time'>14:17</var> UTC Update - 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. Feb <var data-var='date'> 7</var>, <var data-var='time'>10:44</var> UTC 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)

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)

Is Wiz down?

Wiz status is UP

Lastest published events

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.

We are currently seeing delays and possible data loss in sensor ATM ingestion, including RED ingestion and VIR.

Intermittent login failures

Wiz Services, Components and Regions

Recent Wiz events

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.

We are currently seeing delays and possible data loss in sensor ATM ingestion, including RED ingestion and VIR.

Intermittent login failures

Starting at 08:30 UTC, a subset of audit events may not have been recorded as expected.

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.

Degraded performance of Security Graph in DC US48

Get your FREE account now,
5 monitors included!

Is Wiz down?

Wiz status is UP

Lastest published events

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.

We are currently seeing delays and possible data loss in sensor ATM ingestion, including RED ingestion and VIR.

Intermittent login failures

Wiz Services, Components and Regions

Recent Wiz events

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.

We are currently seeing delays and possible data loss in sensor ATM ingestion, including RED ingestion and VIR.

Intermittent login failures

Starting at 08:30 UTC, a subset of audit events may not have been recorded as expected.

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.

Degraded performance of Security Graph in DC US48

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!