Live / Zscaler / Incident
Zscaler: DLP Scanning Delays - zscalertwo.net
Zscaler · zscaler.comResolved2026-10-01 21:08 UTC
Public — what happened
Summary
Zscaler said that starting at 18:24 UTC on 2026-09-30, some customers on its zscalertwo.net cloud saw delays in data loss prevention scanning, including scans of SaaS apps and some email and endpoint checks that match specific data or documents. The company said a software defect in a recent update was the root cause. It said it identified the problem about an hour later and deployed a fix to the affected clusters by 20:14 UTC that day. Zscaler marked the incident resolved at 21:08 UTC on 2026-10-01, saying scanning was back to normal and service was stable.
Timeline
- Started — 2026-09-30 18:24 UTC
- Resolved — 2026-10-01 21:08 UTC · 26h 44m 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 41, 2026, our weekly internet health report.