Live / Zscaler / Incident
Zscaler: Reporting and Logging Issue - zscloud.net
Zscaler · zscaler.comResolved2026-10-30 12:15 UTC
Public — what happened
Summary
Zscaler said it detected a reporting and logging problem on its zscloud.net cloud at 08:02 UTC on 30 October 2026. By 09:11 UTC the company said it had put preliminary mitigation steps in place and was watching to see whether they worked. At 12:15 UTC Zscaler marked the incident resolved, listing the root cause as weblog lag having recovered, and said its systems were fully operational and would continue to be monitored.
Timeline
- Started — 2026-10-30 08:02 UTC
- Update — 2026-10-30 08:02 UTC (2 updates)
- Resolved — 2026-10-30 12:15 UTC · 4h 13m 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 45, 2026, our weekly internet health report.