Live  /  Zscaler  /  Incident

Zscaler: Risk360 Data Update and Risk Score Accuracy Issue - zscaler.net, zscalerone.net, zscalertwo.net, zscloud.net, zscalerthree.net, zscalerrisk.net

Zscaler · zscaler.comResolved2026-10-12 13:04 UTC
Public — what happened

Summary

Zscaler said a subset of its customers had a problem with Risk360, where some data connectors looked inactive and stopped receiving updates, leaving outdated information and risk scores that could be higher than they should be. The company reported the issue began on 10 October 2026 at 17:35 UTC, said it saw no impact on traffic, and advised customers not to base decisions on the affected risk reports. Zscaler said it identified the cause later that day, and attributed it to a software defect in an update process that wrongly switched off certain ZPA-related connectors. On 12 October 2026 at 13:04 UTC it reported the connectors were reactivated, a fix was deployed, and the scores were confirmed accurate.

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.