Wiz Outage History

Wiz is up right now

There were 16 Wiz outages since February 4, 2026 totaling 225h 11m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.wiz.io

Major April 27, 2026

Intermittent login failures affecting prod-eu24 only

Detected by Pingoru
Apr 27, 2026, 10:35 AM UTC
Resolved
Apr 27, 2026, 11:43 AM UTC
Duration
1h 8m
Affected: AuthenticationPortal
Timeline · 3 updates
  1. identified Apr 27, 2026, 10:35 AM UTC

    The issue has been identified and a fix is being implemented.

  2. monitoring Apr 27, 2026, 11:33 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Apr 27, 2026, 11:43 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 17, 2026

The GitHub streaming integration has stopped sending events.

Detected by Pingoru
Apr 17, 2026, 07:16 AM UTC
Resolved
Apr 18, 2026, 02:35 AM UTC
Duration
19h 19m
Affected: Wiz Defend
Timeline · 3 updates
  1. investigating Apr 17, 2026, 07:16 AM UTC

    We are currently investigating this issue.

  2. monitoring Apr 17, 2026, 02:04 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Apr 18, 2026, 02:35 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 3, 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 by Pingoru
Apr 03, 2026, 03:32 PM UTC
Resolved
Apr 04, 2026, 07:04 PM UTC
Duration
1d 3h
Affected: Portal
Timeline · 3 updates
  1. identified Apr 03, 2026, 03:32 PM UTC

    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.

  2. monitoring Apr 03, 2026, 04:47 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Apr 04, 2026, 07:04 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 24, 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 by Pingoru
Mar 24, 2026, 07:21 AM UTC
Resolved
Mar 26, 2026, 05:24 PM UTC
Duration
2d 10h
Affected: Portal
Timeline · 4 updates
  1. investigating Mar 24, 2026, 07:21 AM UTC

    We are currently investigating this issue.

  2. identified Mar 24, 2026, 08:38 AM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Mar 24, 2026, 07:38 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Mar 26, 2026, 05:24 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 23, 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 by Pingoru
Mar 23, 2026, 02:04 PM UTC
Resolved
Mar 23, 2026, 08:37 PM UTC
Duration
6h 32m
Affected: Authentication
Timeline · 3 updates
  1. investigating Mar 23, 2026, 02:04 PM UTC

    We are currently investigating this issue.

  2. monitoring Mar 23, 2026, 06:51 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Mar 23, 2026, 08:37 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 22, 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 by Pingoru
Mar 22, 2026, 06:11 PM UTC
Resolved
Mar 22, 2026, 11:22 PM UTC
Duration
5h 11m
Affected: PortalIngestion
Timeline · 2 updates
  1. monitoring Mar 22, 2026, 06:11 PM UTC

    A fix has been implemented and we are monitoring the results.

  2. resolved Mar 22, 2026, 11:22 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 19, 2026

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

Detected by Pingoru
Mar 19, 2026, 03:53 PM UTC
Resolved
Mar 20, 2026, 06:35 PM UTC
Duration
1d 2h
Affected: PortalIngestion
Timeline · 3 updates
  1. identified Mar 19, 2026, 03:53 PM UTC

    The issue has been identified and a fix is being implemented.

  2. monitoring Mar 19, 2026, 09:51 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Mar 20, 2026, 06:35 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 5, 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 by Pingoru
Mar 05, 2026, 09:56 PM UTC
Resolved
Mar 05, 2026, 10:33 PM UTC
Duration
36m
Affected: Portal
Timeline · 2 updates
  1. investigating Mar 05, 2026, 09:56 PM UTC

    We are currently investigating this issue.

  2. resolved Mar 05, 2026, 10:33 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 3, 2026

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

Detected by Pingoru
Mar 03, 2026, 05:17 PM UTC
Resolved
Mar 05, 2026, 10:54 PM UTC
Duration
2d 5h
Affected: AuthenticationPortalIngestionWiz DefendSensorWiz CLIWiz Code
Timeline · 3 updates
  1. investigating Mar 03, 2026, 05:17 PM UTC

    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

  2. investigating Mar 05, 2026, 10:54 PM UTC

    We are continuing to investigate this issue.

  3. resolved Mar 05, 2026, 10:54 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 3, 2026

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.

Detected by Pingoru
Mar 03, 2026, 03:52 PM UTC
Resolved
Mar 03, 2026, 04:46 PM UTC
Duration
53m
Affected: PortalIngestion
Timeline · 3 updates
  1. investigating Mar 03, 2026, 03:52 PM UTC

    Some customers may experience delays in Serverless findings. We are actively working on mitigation and will share updates as we progress.

  2. identified Mar 03, 2026, 04:00 PM UTC

    The issue has been identified and a fix is being implemented.

  3. resolved Mar 03, 2026, 04:46 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 1, 2026

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

Detected by Pingoru
Mar 01, 2026, 01:06 PM UTC
Resolved
Mar 01, 2026, 08:29 PM UTC
Duration
7h 22m
Timeline · 4 updates
  1. investigating Mar 01, 2026, 01:06 PM UTC

    We are currently investigating this issue.

  2. investigating Mar 01, 2026, 01:08 PM UTC

    See AWS status: https://health.aws.amazon.com/health/status?path=service-history

  3. monitoring Mar 01, 2026, 07:17 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Mar 01, 2026, 08:29 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 15, 2026

Intermittent login failures affecting prod-us54 only

Detected by Pingoru
Feb 15, 2026, 11:51 AM UTC
Resolved
Feb 15, 2026, 01:35 PM UTC
Duration
1h 43m
Affected: AuthenticationPortal
Timeline · 3 updates
  1. investigating Feb 15, 2026, 11:51 AM UTC

    We are currently investigating this issue.

  2. monitoring Feb 15, 2026, 12:08 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Feb 15, 2026, 01:35 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 11, 2026

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.

Detected by Pingoru
Feb 11, 2026, 10:00 AM UTC
Resolved
Feb 11, 2026, 05:07 PM UTC
Duration
7h 6m
Affected: Wiz Code
Timeline · 3 updates
  1. identified Feb 11, 2026, 10:00 AM UTC

    The issue has been identified and a fix is being implemented.

  2. monitoring Feb 11, 2026, 05:00 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Feb 11, 2026, 05:07 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 9, 2026

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

Detected by Pingoru
Feb 09, 2026, 02:30 PM UTC
Resolved
Feb 09, 2026, 02:30 PM UTC
Duration
18s
Affected: Wiz Defend
Timeline · 2 updates
  1. investigating Feb 09, 2026, 02:30 PM UTC

    We are currently investigating this issue.

  2. resolved Feb 09, 2026, 02:30 PM UTC

    ingestion is restored and we are evaluating options to recover missing data.

Read the full incident report →

Notice February 7, 2026

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)

Detected by Pingoru
Feb 07, 2026, 06:49 PM UTC
Resolved
Feb 08, 2026, 03:45 AM UTC
Duration
8h 55m
Affected: IngestionWiz Defend
Timeline · 6 updates
  1. monitoring Feb 07, 2026, 10:44 AM UTC

    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)

  2. monitoring Feb 07, 2026, 02:17 PM UTC

    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.

  3. monitoring Feb 07, 2026, 06:03 PM UTC

    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.

  4. monitoring Feb 07, 2026, 06:49 PM UTC

    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.

  5. monitoring Feb 07, 2026, 08:18 PM UTC

    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.

  6. resolved Feb 08, 2026, 03:45 AM UTC

    This incident has been resolved.

Read the full incident report →

Looking to track Wiz downtime and outages?

Pingoru polls Wiz's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Wiz reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Wiz alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Wiz for free

5 free monitors · No credit card required