Live / Zscaler / Incident
Zscaler: Reporting and Logging Issue - zscalertwo.net
Zscaler · zscaler.comResolved2026-09-24 22:41 UTC
Public — what happened
Summary
Zscaler said that starting at 19:48 UTC on 2026-09-24 some customers on its zscalertwo.net cloud could see delays or problems with logging and reporting. The company said the cause was high resource use in its logging system, which slowed processing of web logs in the Admin Portal and in feeds sent out through NSS. Zscaler reported that it identified the cause about ten minutes later, applied a fix, and said web logs were available again by 21:18 UTC. It marked the incident resolved at 22:41 UTC and said it would keep monitoring.
Timeline
- Started — 2026-09-24 19:48 UTC
- Resolved — 2026-09-24 22:41 UTC · 2h 52m 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.