We are investigating an issue affecting the security graph and dependent features in prod-US38.
Oct 18, 05:22 UTC Resolved - This incident has been resolved. Oct 18, 03:57 UTC Investigating - We are currently investigating this issue.
Oct 18, 05:22 UTC Resolved - This incident has been resolved. Oct 18, 03:57 UTC Investigating - We are currently investigating this issue.
Oct 14, 20:35 UTC Resolved - This incident has been resolved. Oct 14, 19:17 UTC Monitoring - A fix has been implemented and we are monitoring the results. Oct 14, 18:50 UTC Identified - The issue has been identified and a fix is being implemented. Oct 14, 17:06 UTC Investigating - We are currently investigating this issue.
Oct 6, 11:58 UTC Resolved - This incident has been resolved. Oct 5, 17:18 UTC Monitoring - A fix has been implemented and we are monitoring the results. Oct 5, 16:49 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.
Sep 20, 11:27 UTC Resolved - This incident has been resolved. Sep 13, 12:36 UTC Monitoring - A fix has been implemented and we are monitoring the results. Sep 12, 18:45 UTC Identified - The issue has been identified and a fix is being implemented. Sep 12, 10:21 UTC Investigating - We are currently investigating this issue.
Sep 3, 23:50 UTC Resolved - This incident has been resolved. Sep 3, 22:39 UTC Monitoring - A fix has been implemented and we are monitoring the results. Sep 3, 22:31 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
Jul 23, 22:00 UTC Resolved - This incident has been resolved. Jul 23, 20:52 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 re…
Jul 10, 18:08 UTC Resolved - This incident has been resolved. Jul 10, 17:28 UTC Monitoring - A fix has been implemented and we are monitoring the results. Jul 10, 16:55 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 impa…
Jun 22, 18:39 UTC Resolved - This incident has been resolved. Jun 22, 17:13 UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun 22, 14:08 UTC Identified - The issue has been identified and a fix is being implemented. Jun 22, 13:43 UTC Investigating - We are currently investigating this issue.
Mar 5, 22:56 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/statusAffected Wiz DC: prod-me1
Jun 21, 04:01 UTC Resolved - This incident has been resolved. Jun 20, 23:39 UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun 20, 22:00 UTC Investigating - We are currently investigating this issue.
Jun 17, 17:58 UTC Resolved - This incident has been resolved. Jun 17, 17:43 UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun 17, 17:38 UTC Identified - The issue has been identified and a fix is being implemented. Jun 17, 17:30 UTC Investigating - We are currently investigating this issue.
Jun 8, 19:33 UTC Resolved - This incident has been resolved. Jun 8, 18:15 UTC Identified - We have identified the cause and are deploying a fix.
May 21, 04:17 UTC Resolved - This incident has been resolved. May 20, 17:52 UTC Monitoring - A fix has been implemented and we are monitoring the results. May 20, 14:04 UTC Identified - The issue has been identified and a fix is being implemented.
May 11, 08:29 UTC Resolved - This incident has been resolved. May 11, 08:26 UTC Monitoring - A fix has been implemented and we are monitoring the results. May 11, 06:17 UTC Identified - The issue has been identified and a fix is being implemented. May 11, 06:17 UTC Investigating - We are currently investigating this issue.
May 8, 10:13 UTC Resolved - This incident has been resolved. May 8, 10:07 UTC Monitoring - A fix has been implemented and we are monitoring the results. May 8, 07:06 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…
Apr 27, 11:43 UTC Resolved - This incident has been resolved. Apr 27, 11:33 UTC Monitoring - A fix has been implemented and we are monitoring the results. Apr 27, 10:35 UTC Identified - The issue has been identified and a fix is being implemented.
Apr 18, 02:35 UTC Resolved - This incident has been resolved. Apr 17, 14:04 UTC Monitoring - A fix has been implemented and we are monitoring the results. Apr 17, 07:16 UTC Investigating - We are currently investigating this issue.
Apr 14, 06:45 UTC Resolved - This incident has been resolved. Apr 14, 06:19 UTC Investigating - We are currently investigating this issue.
Apr 4, 19:04 UTC Resolved - This incident has been resolved. Apr 3, 16:47 UTC Monitoring - A fix has been implemented and we are monitoring the results. Apr 3, 15:32 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.
Mar 26, 17:24 UTC Resolved - This incident has been resolved. Mar 24, 19:38 UTC Monitoring - A fix has been implemented and we are monitoring the results. Mar 24, 08:38 UTC Identified - The issue has been identified and a fix is being implemented. Mar 24, 07:21 UTC Investigating - We are currently investigating this issue.
Mar 23, 20:37 UTC Resolved - This incident has been resolved. Mar 23, 18:51 UTC Monitoring - A fix has been implemented and we are monitoring the results. Mar 23, 14:04 UTC Investigating - We are currently investigating this issue.
Mar 22, 23:22 UTC Resolved - This incident has been resolved. Mar 22, 18:11 UTC Monitoring - A fix has been implemented and we are monitoring the results.
Mar 20, 18:35 UTC Resolved - This incident has been resolved. Mar 19, 21:51 UTC Monitoring - A fix has been implemented and we are monitoring the results. Mar 19, 15:53 UTC Identified - The issue has been identified and a fix is being implemented.
Mar 5, 22:54 UTC Resolved - This incident has been resolved. Mar 5, 22:54 UTC Update - We are continuing to investigate this issue. Mar 3, 17:17 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 u…
Mar 5, 22:33 UTC Resolved - This incident has been resolved. Mar 5, 21:56 UTC Investigating - We are currently investigating this issue.
Mar 3, 16:46 UTC Resolved - This incident has been resolved. Mar 3, 16:00 UTC Identified - The issue has been identified and a fix is being implemented. Mar 3, 15:52 UTC Investigating - Some customers may experience delays in Serverless findings. We are actively working on mitigation and will share updates as we progress.
Mar 3, 09:15 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 AW…
Mar 1, 20:29 UTC Resolved - This incident has been resolved. Mar 1, 19:17 UTC Monitoring - A fix has been implemented and we are monitoring the results. Mar 1, 13:08 UTC Update - See AWS status: https://health.aws.amazon.com/health/status?path=service-history Mar 1, 13:06 UTC Investigating - We are currently investigating this issue.
Feb 15, 13:35 UTC Resolved - This incident has been resolved. Feb 15, 12:08 UTC Monitoring - A fix has been implemented and we are monitoring the results. Feb 15, 11:51 UTC Investigating - We are currently investigating this issue.
Feb 11, 17:07 UTC Resolved - This incident has been resolved. Feb 11, 17:00 UTC Monitoring - A fix has been implemented and we are monitoring the results. Feb 11, 10:00 UTC Identified - The issue has been identified and a fix is being implemented.