Is Wiz Down?

No — Wiz is up

Reachable from all 8 checked regions

Average response time: 252ms

Last checked 2 hours ago · checks run every 6 hours

Official status page: https://status.wiz.io

Wiz uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

275ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 56 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

56-day clean streak

Sep 14 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams

240ms

DNS 125ms TCP 11ms TLS 26ms TTFB 205ms

arn

252ms

DNS 190ms TCP 2ms TLS 9ms TTFB 242ms

cdg

174ms

DNS 56ms TCP 8ms TLS 15ms TTFB 137ms

dfw

384ms

DNS 220ms TCP 0ms TLS 52ms TTFB 334ms

ewr

353ms

DNS 257ms TCP 1ms TLS 21ms TTFB 336ms

sjc

172ms

DNS 125ms TCP 2ms TLS 8ms TTFB 163ms

syd

252ms

DNS 204ms TCP 0ms TLS 7ms TTFB 243ms

yyz

190ms

DNS 51ms TCP 12ms TLS 33ms TTFB 139ms

What Wiz does

Wiz connects to AWS, Azure, GCP and Kubernetes accounts, builds a graph of what is running and where risk concentrates, and surfaces the paths an attacker could take across code, cloud and runtime. Security teams use it for posture management and vulnerability triage, with Wiz Defend and the Sensor covering runtime detection and Wiz Code covering pipelines.

What an outage looks like

The Wiz portal fails to load, or authentication loops without signing you in. Ingestion stalls, so the graph goes stale and newly created cloud resources never appear. Findings stop refreshing, which reads as an improvement in posture when nothing has changed. Wiz CLI and Wiz Code calls in CI pipelines time out, and scanning gates block builds.

What to do about it

status.wiz.io lists Authentication, Portal, Ingestion, Wiz Defend, Sensor, Wiz CLI and Wiz Code separately, so a CI gate failure is easy to tell from a portal one. If Wiz CLI is degraded, decide explicitly whether builds proceed without the scan rather than leaving pipelines to time out. Treat a falling findings count during an incident as missing data, not progress.

Is it down for everyone, or just you?

If this page says Wiz is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Snyk

Okta

AWS

Datadog

Wiz outage FAQ

Our findings count dropped. Did we actually fix things?

Check Ingestion before celebrating. Wiz builds its picture from data it pulls out of your cloud accounts, and when ingestion is degraded the graph stops updating. Existing findings can age out of view while new ones never arrive, so the dashboard improves without anything changing in your environment. Compare against the previous day's export before reporting the drop.

Our CI builds are failing on the Wiz scan. What now?

Wiz CLI and Wiz Code are their own components, so confirm one of them is degraded rather than assuming a policy change broke the build. During a confirmed incident, most teams either pause the gate or let builds through and re-scan afterwards. Make that call deliberately, because a security gate switched off quietly is easy to forget to switch back on.

Is Wiz Defend affected when the portal is down?

Not necessarily. Portal and Wiz Defend are separate components. The portal is the interface you log into, while Defend handles runtime threat detection, so detection can continue while the console is unavailable, or the reverse. Read the component list rather than the overall banner, and check your alert destinations to confirm notifications are still arriving.

Does Wiz depend on the cloud it is monitoring?

In part. Wiz runs its own infrastructure in cloud regions, and its status page has reported a disruption in an AWS region holding back recovery of affected Wiz services. A large provider incident can therefore degrade both your environment and the tool watching it at the same time. Keep a second signal for cloud health rather than relying on one platform for both.

How we measure this

We request Wiz's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Wiz publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Wiz goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required