Live / Zscaler / Incident
Zscaler: ZCC Flow Logging Issue - zscaler.net, zscalerone.net, zscalertwo.net, zscloud.net, zscalerthree.net
Zscaler · zscaler.comResolved2026-10-26 19:52 UTC
Public — what happened
Summary
Zscaler said some customers on its zscaler.net, zscalerone.net, zscalertwo.net, zscloud.net and zscalerthree.net clouds could be missing Zscaler Client Connector flow logs for traffic that bypasses Zscaler, as seen in Web Insight. The company said customer data and network traffic were not affected. The issue began on 6 October 2026, and Zscaler said it identified the root cause the next day, then validated a fix by 8 October. On 26 October 2026 Zscaler reported the fix was deployed across all affected clouds and the issue was resolved, saying a software update had added an authentication check that wrongly rejected these logs.
Timeline
- Started — 2026-10-06 22:06 UTC
- Resolved — 2026-10-26 19:52 UTC · 20 days 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 42, 2026, our weekly internet health report.