Wiz Status
Investigating - 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

Mar 05, 2026 - 22:56 UTC

About This Site

This is Wiz's status page, where you can get updates on how our systems are doing. If there are interruptions to service, we will post a note here.

As always, if you are experiencing any issues with Wiz, don't hesitate to get in touch with us at support@wiz.io and we'll get back to you as soon as we can.

Authentication Operational
90 days ago
99.63 % uptime
Today
Portal Operational
Ingestion Operational
Wiz Defend Operational
Sensor Operational
Wiz CLI Operational
Wiz Code Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Mar 15, 2026

No incidents reported today.

Mar 14, 2026

No incidents reported.

Mar 13, 2026

No incidents reported.

Mar 12, 2026

No incidents reported.

Mar 11, 2026

No incidents reported.

Mar 10, 2026

No incidents reported.

Mar 9, 2026

No incidents reported.

Mar 8, 2026

No incidents reported.

Mar 7, 2026

No incidents reported.

Mar 6, 2026

No incidents reported.

Mar 5, 2026
Resolved - This incident has been resolved.
Mar 5, 22:54 UTC
Update - We are continuing to investigate this issue.
Mar 5, 22:54 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

Mar 3, 17:17 UTC
Mar 4, 2026

No incidents reported.

Mar 3, 2026
Resolved - This incident has been resolved.
Mar 3, 16:46 UTC
Identified - The issue has been identified and a fix is being implemented.
Mar 3, 16:00 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, 15:52 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 3, 09:15 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 2, 07:12 UTC
Monitoring - See AWS status: https://health.aws.amazon.com/health/status?path=service-history
Mar 1, 20:42 UTC
Mar 2, 2026
Mar 1, 2026
Resolved - This incident has been resolved.
Mar 1, 20:29 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Mar 1, 19:17 UTC
Update - See AWS status: https://health.aws.amazon.com/health/status?path=service-history
Mar 1, 13:08 UTC
Investigating - We are currently investigating this issue.
Mar 1, 13:06 UTC