Zscaler's Authentication component failed for 14 minutes on 10 November 2026, blocking device registration and portal access for Zscaler Client Connector. The fault sat on Zscaler's side, not yours.
Started
10:04 UTC
Duration
Lasted 14m
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: Authentication
What happened?
Zscaler logged one incident on this day, starting at 10:04 UTC and lasting 14 minutes. The affected component is listed as Authentication, and the incident title specifically names device registration and portal failure for Zscaler Client Connector. That is a narrow failure: if your users were already authenticated and connected, this incident would not have touched them. If they were trying to register a new device or load the portal during that 14 minute window, they would have hit a wall. Zscaler published no updates on this incident. There is no timeline of detection, mitigation and resolution, just a start time and a duration. That means you cannot see whether Zscaler caught this themselves or whether it was closed out after the fact with no further explanation. No cause is on the record. No user reports were filed during the window. UptimeRobot's own probes watch the edge component across EU and NA regions, and this incident is not registered against those probes. Uptime over the last 24 hours sits at 99.858%, over 7 days at 99.822%, over 30 days at 99.678%. Those numbers are consistent with normal edge performance and do not reflect a drop tied to this authentication issue. Zscaler's 90 day history shows 36 incidents with a median duration of 1 hour 48 minutes, and across its full history the company averages 8.9 incidents a month. A 14 minute incident is short against that backdrop.
Learning
This incident shows why checking your own login flow from the outside does not always catch a provider side authentication fault. UptimeRobot's edge probes measure a different layer, the edge component itself, which stayed healthy across EU and NA throughout this window, while the specific failure was in device registration and the portal, a narrower path that a general edge probe would not necessarily cross. This is the shape to watch for in your own product: a vendor can have a real, if brief, authentication or registration failure that never shows up as a drop in broader uptime metrics, because the broader service kept answering. Zscaler published no updates and no cause, so you are left with a start time and a duration and nothing else to explain it. The lesson is not to doubt either reading, the edge was up and the registration path was broken at the same time, both true. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.