Live / Zscaler / Incident
Zscaler: Zscaler Client Connector Portal Issue - zscaler.net, zscalerone.net, zscalertwo.net, zscloud.net, zscalerthree.net
Zscaler · zscaler.comResolved2026-09-26 07:07 UTC
Public — what happened
Summary
Zscaler said it began investigating reports of problems with the Client Connector Portal across several of its cloud environments (zscaler.net, zscalerone.net, zscalertwo.net, zscloud.net and zscalerthree.net) starting at 05:21 UTC on 26 September 2026. The company said it found the cause by 05:51 UTC and attributed it to a recent service update. It said a mitigation was in place by 06:02 UTC and was being checked through internal testing and customer feedback. Zscaler reported the incident resolved at 07:07 UTC and said it would keep monitoring for stability.
Timeline
- Started — 2026-09-26 05:21 UTC
- Resolved — 2026-09-26 07:07 UTC · 1h 45m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Zscaler against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Zscaler: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Zscaler report →
More from Zscaler
Covered in The Squid’s Ink, Week 40, 2026, our weekly internet health report.