Live  /  Zscaler  /  Incident

Zscaler: ZPA Browser Isolation Policy Issue - private.zscaler.com, zpatwo.net, zpabeta.net

Zscaler · zscaler.comResolved2026-09-24 14:54 UTC
Public — what happened

Summary

Zscaler said that starting at 13:55 UTC on 2026-09-24, customers on its private.zscaler.com and zpatwo.net clouds might have had trouble creating or changing ZPA Browser Isolation policies, in both the legacy portal and the Experience Center. The company said it identified the root cause by 14:01 UTC and put mitigation measures in place by 14:26 UTC. Zscaler stated the cause was a recent service change that affected saving these policies. It reported the incident resolved at 14:54 UTC and said it would keep monitoring for stability.

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 40, 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.