Zscaler favicon

Zscaler outage on 2026-11-06

zscaler.com
November 2026 6 Minor incident

Zscaler's Security component had a Sandbox Issue starting at 07:43 UTC that lasted 1h 4m. The fault sat with Zscaler's infrastructure, not with anything in your own setup.

Started

07:43 UTC

Duration

Lasted 1h 4m

Source

IsDown

Next time

Zscaler is degraded. Is your product working?

An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.

50 monitors for your own websites. No card.

Affected components: Security

What happened?

Zscaler logged a single incident on this day, titled "Sandbox Issue", affecting the Security component. It started at 07:43 UTC and ran for 1h 4m before resolving. Zscaler published no updates during that window, so there is no detail on what inside the sandbox function broke or how the fault was contained. No user reports were filed during the window, which only tells you nobody who reports into this record noticed, not that nobody was affected. Zscaler's status history shows this kind of thing is routine for them: 37 incidents in the last 90 days, with a median duration of 1 hour 48 minutes, and 380 incidents across all time at a rate of 8.8 a month. Measured against that pattern, this incident resolved faster than the typical one. UptimeRobot's own checks against Zscaler's edge component, run from EU and NA regions every 60 seconds, did not register this incident. Uptime over the past 24 hours sits at 99.927%, over 7 days at 99.858%, and over 30 days at 99.715%, all consistent with a provider that mostly holds up between incidents like this one. No post-mortem has been published, and Zscaler's own account offers nothing beyond the title and the time window.

Learning

Sandbox functions sit deeper in Zscaler's security stack than the edge routing that external probes watch, so a probe checking whether traffic reaches Zscaler's edge can stay green while a specific inspection feature like sandboxing is broken behind it. That is why this incident does not appear in UptimeRobot's own measurements: the edge was up, the sandbox analysis path was not, and those are different things to check. If your product relies on Zscaler for content inspection or threat sandboxing specifically, an edge-level uptime number will not tell you whether that particular function is working. The general shape to watch for with Zscaler is a named feature going down while the surrounding service reports healthy, which is exactly what a vendor status page with no further updates and a monitoring dashboard with no registered incident will both show you at once, correctly. Your own monitoring covers your half of this relationship, the paths your product controls. UptimeRobot now watches Zscaler's half too, so next time something like this happens you know which side broke without guessing.

4.7
stars out of 5
284+ reviews on

Start monitoring in 30 seconds.

There's nothing to install. No credit card required. 50 monitors for free.