Update - Fri, 03 Jul 2026 06:03:18 UTC

Zscaler observed weblog lag across zscaler.net. The issue was identified, mitigated, and lag has fully recovered. Services are operating normally and the issue is now resolved.

Update - Thu, 02 Jul 2026 11:19:00 UTC

Zscaler has identified the cause and is actively working to mitigate the issue.

Update - Thu, 02 Jul 2026 12:51:09 UTC

Mitigation has been applied and validated on the subset of impacted nodes in the ZS2 (zscalertwo.net) cloud. Engineering teams are now completing the same corrective action on the ZS3 (zscalerthree.net) cloud and will provide a further update once the issue has been fully resolved across all environments.

Update - Thu, 02 Jul 2026 13:28:30 UTC

Mitigation has been applied and validated on the subset of impacted nodes in the ZS2 (zscalertwo.net) and ZS3 (zscalerthree.net) cloud. This incident is now resolved.

Update - Wed, 01 Jul 2026 18:39:31 UTC

We have identified the root cause of the issue and working on resolution.

Update - Wed, 01 Jul 2026 22:01:43 UTC

Zscaler teams continue working on this issue with priority. Further updates will be shared when available.

Update - Thu, 02 Jul 2026 00:27:52 UTC

Following the actions previously taken by Zscaler, the incident has been resolved. Our systems remain fully operational, and we will continue to monitor the situation closely to ensure ongoing stability.

Update - Wed, 01 Jul 2026 22:55:15 UTC

Zscaler has identified the cause of the issue as a software regression in a recent Service Edge software update. The regression may cause some DNS resolution requests to intermittently time out when users access domains that return larger-than-expected DNS responses. Zscaler is applying a validated mitigation across affected infrastructure and is expediting deployment of a corrective software update. We will provide further updates as additional progress is made.

Update - Thu, 02 Jul 2026 22:57:26 UTC

Zscaler has developed a corrective software update and is deploying it in a controlled, phased manner across affected infrastructure. Initial deployment has completed across a subset of affected infrastructure, and rollout will continue across the remaining affected infrastructure. We will provide further updates as additional progress is made.

Update - Sun, 05 Jul 2026 09:42:18 UTC

Zscaler continues the phased deployment of the corrective software update across affected infrastructure. Deployment has now completed across ZS2, Oceania, and APAC regions, with rollout continuing across the remaining affected EMEA and AMER infrastructure. We will provide further updates as additional progress is made.

Update - Thu, 02 Jul 2026 21:12:46 UTC

Zscaler has identified the contributing software condition, and a software fix has been developed. The fix is being deployed through a phased rollout. We will provide additional updates as deployment progresses.

Update - Sun, 05 Jul 2026 09:42:59 UTC

Zscaler continues the phased deployment of the corrective software update across affected infrastructure. Deployment has now completed across ZS2, Oceania, and APAC regions, with rollout continuing across the remaining affected EMEA and AMER infrastructure. We will provide further updates as additional progress is made.