Zscaler's Client Connector Portal had a problem starting at 05:14 UTC that lasted 49 minutes, touching the Admin UI, Zscaler Client Connector Admin, and Authentication. This was a fault on Zscaler's side, not yours.
Started
05:14 UTC
Duration
Lasted 49m
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, Zscaler Client Connector Admin, Authentication
What happened?
Zscaler logged one incident on 26 September 2026, titled "Zscaler Client Connector Portal Issue", starting at 05:14 UTC and running for 49 minutes. Three components appear on the affected list: Admin UI, Zscaler Client Connector Admin, and Authentication. Zscaler published no updates at all during this incident, so there is no written account of what actually failed inside those components or how the fix was applied. No user reports were filed during the window, which on its own tells you little given how little else is on record. For comparison, Zscaler's last 90 days show 34 incidents with a median duration of 1 hour 48 minutes, so a 49 minute incident sits on the shorter side of their recent pattern. Across all time Zscaler has logged 370 incidents, averaging 8.8 a month, which puts this one inside a fairly routine cadence for them. UptimeRobot's own probes, watching the edge from both EU and NA regions, did not register this particular incident. That is not a contradiction: an admin portal and authentication fault can sit entirely behind Zscaler's own infrastructure, never touching the edge paths that external checks poll. Our 30 day stats for Zscaler show 13 incidents, all resolved, with a median duration of 4h 41m, well above today's 49 minutes. Uptime over the past 24 hours sat at 95.749%, over 7 days at 91.963%, and over 30 days at 96.467%, figures that reflect broader probe activity rather than this single event. No post-mortem has been published for this incident, and Zscaler's status page gives no cause.
Learning
This incident shows the shape of a provider-side fault that your own monitoring would never catch, because it lived in Zscaler's admin and authentication layer rather than on the edge paths your traffic actually runs through. UptimeRobot's probes watch the edge from the EU and NA, and they stayed green through this entire 49 minute window, which is the correct reading from where those probes sit, not a missed alert. Meanwhile Zscaler's own status page logged a real, separate fault in its Client Connector Admin and Authentication components, and that is also the correct reading from where Zscaler sits. Both readings being true at once is the point: your checks and the provider's checks are looking at different halves of the same system. Zscaler published zero updates on this incident, so if you were trying to diagnose a login or portal issue during that window using only their status page, you had nothing to go on beyond the bare fact that something was wrong. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.
