Live / Zscaler / Incident
Zscaler: Reporting and Logging Issue - zscalerthree.net
Zscaler · zscaler.comResolved2026-11-04 19:07 UTC
Public — what happened
Summary
Zscaler said a subset of customers on its zscalerthree.net cloud could see delays or problems with logging and reporting, starting at 02:13 UTC on 2026-11-04. About two hours later, the company said it had found the cause to be a resource strain on backend nodes, which it said made them unstable and slowed log processing, and it began work to free up resources. By 09:54 UTC Zscaler reported that the delay in processing web logs had returned to normal, and at 19:07 UTC it declared the incident resolved and said its systems were fully operational.
Timeline
- Started — 2026-11-04 02:13 UTC
- Update — 2026-11-04 02:13 UTC (2 updates)
- Resolved — 2026-11-04 19:07 UTC · 16h 54m 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 46, 2026, our weekly internet health report.