Oct <var data-var='date'> 5</var>, <var data-var='time'>17:18</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Oct <var data-var='date'> 5</var>, <var data-var='time'>16:49</var> UTC 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.

Service degradation in US27

Sep <var data-var='date'>20</var>, <var data-var='time'>11:27</var> UTC Resolved - This incident has been resolved. Sep <var data-var='date'>13</var>, <var data-var='time'>12:36</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Sep <var data-var='date'>12</var>, <var data-var='time'>18:45</var> UTC Identified - The issue has been identified and a fix is being implemented. Sep <var data-var='date'>12</var>, <var data-var='time'>10:21</var> UTC Investigating - We are currently investigating this issue.

We are investigating an issue causing delays in processing and displaying vulnerability findings in the Security Graph for some customers.

Sep <var data-var='date'> 3</var>, <var data-var='time'>23:50</var> UTC Resolved - This incident has been resolved. Sep <var data-var='date'> 3</var>, <var data-var='time'>22:39</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Sep <var data-var='date'> 3</var>, <var data-var='time'>22:31</var> UTC 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

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

Jul <var data-var='date'>23</var>, <var data-var='time'>22:00</var> UTC Resolved - This incident has been resolved. Jul <var data-var='date'>23</var>, <var data-var='time'>20:52</var> UTC 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 working to ensure all services return to normal performance. Jul <var data-var='date'>23</var>, <var data-var='time'>16:51</var> UTC 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 loading of some pages, API errors, and delays in data ingestion and processing. This is related to an ongoing Microsoft Azure West US region disruption. We are actively working to restore service and will provide further updates as they become available.

Portal and API Service Degradation Across Multiple US Data Centers

Jul <var data-var='date'>10</var>, <var data-var='time'>18:08</var> UTC Resolved - This incident has been resolved. Jul <var data-var='date'>10</var>, <var data-var='time'>17:28</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Jul <var data-var='date'>10</var>, <var data-var='time'>16:55</var> UTC 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: https://status.launchdarkly.com/ We will share additional information as it becomes available.

Elevated error rates due to an upstream dependency

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

Is Wiz down?

Wiz status is UP

Lastest published events

Service degradation in US27

We are investigating an issue causing delays in processing and displaying vulnerability findings in the Security Graph for some customers.

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

Wiz Services, Components and Regions

Recent Wiz events

Service degradation in US27

We are investigating an issue causing delays in processing and displaying vulnerability findings in the Security Graph for some customers.

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

Portal and API Service Degradation Across Multiple US Data Centers

Elevated error rates due to an upstream dependency

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.