Zscaler favicon

Zscaler outage on 2026-10-06

zscaler.com
October 2026 6 Minor incident

Zscaler's Admin UI has been affected since 22:01 UTC by an incident Zscaler labelled "ZCC Flow Logging Issue". It is still open with no resolution time given, and the fault sits on Zscaler's side, not yours.

Started

22:01 UTC

Duration

Lasted 19d 21h

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: Admin UI

What happened?

Zscaler opened one incident on 6 October 2026, starting at 22:01 UTC, affecting the Admin UI component. The title given is "ZCC Flow Logging Issue", which points at flow logging within Zscaler Client Connector rather than the data path itself. Zscaler has filed no updates on this incident since opening it, so there is no word on scope, root cause or an expected fix time. No user reports came in during this window, which is unsurprising given the affected component is an administrative surface rather than the traffic-handling edge most people would notice first. Over the last 90 days Zscaler has logged 34 incidents with a median duration of 1 hour 48 minutes, and across its full history it averages 8.9 incidents a month, so this is a provider with a steady background rate of issues. This particular incident is still open at the time Zscaler last touched it, with no further filing to say otherwise. UptimeRobot's own checks against Zscaler's edge component, run from EU and NA regions every 60 seconds, show 99.789% uptime over 24 hours and 99.897% over 7 days, which reads as largely healthy. That 30 day figure drops to 96.444%, and this incident has been registered against that window. The gap between a healthy-looking edge probe and an open Admin UI incident is not a contradiction: they are checking different parts of Zscaler's stack.

Learning

When a provider's status page names an incident against "Admin UI" or a logging feature, that is a different layer from the edge that actually routes your traffic, and an external check watching the edge can stay green the entire time without being wrong. That is the shape of this outage: Zscaler's own filing names a logging component, UptimeRobot's probes are watching the edge, and both readings are accurate for what they measure. Over 30 days UptimeRobot recorded 14 incidents against Zscaler with a median duration of 4h 41m, 13 of them resolved, which gives you a working sense of how often and how long these things tend to run even when Zscaler's own status page stays quiet. If your product depends on Zscaler's admin or logging surfaces rather than raw traffic flow, your own uptime checks on your endpoints won't catch this kind of failure, because the fault lives entirely on Zscaler's side of the boundary. Watching only your own endpoints tells you your half is fine, not that the service behind it is fine. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time 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.