Zscaler favicon

Zscaler outage on 2026-10-20

zscaler.com
October 2026 20 Minor incident

Zscaler's Admin UI had two separate problems on 20 October 2026, an Audit Logs issue starting at 01:06 UTC and an Experience Center issue starting at 10:51 UTC that ran for 4h 9m. Both were logged by Zscaler itself as affecting the Admin UI component, with the fault sitting on Zscaler's side.

Started

01:06 UTC

Duration

Lasted 1h 48m

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's status history shows two incidents on 20 October 2026, both scoped to the Admin UI component. The first, titled "Audit Logs Issue", started at 01:06 UTC and lasted 1h 48m. The second, "Experience Center Issue", started at 10:51 UTC and ran for 4h 9m, the longer of the two. Zscaler published no updates on either incident beyond the initial listing, so there is no account of what broke inside the Admin UI or why it took over four hours to clear the second one. No user reports were filed during the window on either incident. That absence doesn't mean nobody was affected, it means nobody logged a report against this specific window. Zscaler's own 90 day history lists 36 incidents with a median duration of 1 hour 49 minutes, so neither of these two was unusually short or long against that pattern. Across all time Zscaler has logged 375 incidents at a rate of roughly 8.9 a month, which gives useful context for how often this provider's status page gets an entry at all. UptimeRobot's own checks against Zscaler's edge, run from both EU and North America every 60 seconds, held 100% uptime over the preceding 24 hours and this incident was not registered on our side. That is expected: Admin UI and Audit Logs sit behind the main login and administration path, not the edge traffic path that external probes against Zscaler's edge are built to watch.

Learning

Admin UI and edge traffic are different layers of the same product, and an incident confined to the Admin UI, as both of these were, will not necessarily show up in a check built to watch edge availability. UptimeRobot's probes against Zscaler's edge from EU and North America stayed at 100% uptime over 24 hours through this window, and that reading is accurate for what it measures, it just isn't measuring the Admin UI. Over 30 days the same probes logged 96.355% uptime, with 9 incidents recorded on our side and a median duration of 1h 48m, which tells you edge issues do happen even when a given day's Admin UI problem is unrelated. The general shape to recognise in your own product: a control plane or administration interface can fail while the data plane keeps routing traffic normally, so a green dashboard on the traffic side is not proof that admin tooling, logging or reporting is working. Zscaler filed no updates explaining either incident, so there is nothing more specific to go on than component and duration. Your own monitoring covers your half of this relationship, UptimeRobot now watches the provider's half too, so next time something looks wrong 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.