Live  /  Zscaler  /  Incident

Zscaler: Reporting and Logging Issue - zscalertwo.net

Zscaler · zscaler.comResolved2026-10-08 00:46 UTC
Public — what happened

Summary

Zscaler said customers on its zscalertwo.net cloud had trouble viewing Web Insights logs starting at 16:15 UTC on 2026-10-07, with some seeing a lost-connection message or 503 errors. The company said the cause was heavy load on part of its infrastructure, which slowed the processing of those logs. It reported finding the cause by 17:04 UTC and, by 21:31 UTC, said fixes were in place and recovery was underway. Zscaler said the incident was resolved at 00:46 UTC on 2026-10-08 and that it would keep monitoring.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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.

The full archive is on the Zscaler status & history page.

Related: Zscaler status & history. SquidGrid is not affiliated with Zscaler.