Update - Fri, 21 Aug 2026 09:03:45 UTC

We have identified the root cause for this issue and we are currently working to mitigate the issue.

Update - Fri, 21 Aug 2026 10:33:44 UTC

Zscaler has implemented preliminary mitigation measures to address the issue. The team is actively monitoring and evaluating the effectiveness of these measures.

Update - Thu, 20 Aug 2026 14:44:31 UTC

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

Update - Thu, 20 Aug 2026 15:44:43 UTC

We are seeing improvement in the previously reported degradation on ZS2 (zscalertwo.net). Our team continues to monitor the environment.

Update - Thu, 20 Aug 2026 16:35:26 UTC

The previously reported degradation on ZS2 (zscalertwo.net) is no longer being observed. Services appear to have been fully restored and the environment is stable. We will continue to monitor for a further period before issuing a final resolution notice.

Update - Thu, 20 Aug 2026 19:34:14 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 - Thu, 20 Aug 2026 17:05:48 UTC

Zscaler has identified the issue as a software regression that may leave certain user sessions in a pending connection state. Zscaler is actively working on a permanent fix. Customers experiencing this issue should contact Zscaler Support for assistance with applying the available interim mitigation. Updates will be provided as remediation progresses.

Update - Thu, 20 Aug 2026 13:27:34 UTC

We have identified the root cause of an issue affecting ZPA App Connector connectivity in the China region. 

A workaround is available: restarting the ZPA App Connector service has restored connectivity in observed cases. Please note that restarting the App Connector will temporarily interrupt active sessions, and customers should coordinate internally before proceeding.

We are currently working on mitigation options to reduce customer impact and will provide further updates as more information becomes available.

Update - Thu, 20 Aug 2026 18:42:12 UTC

Zscaler continue investigating a ZPA App Connector connectivity issue affecting customers in the China region (Shanghai and Beijing). At this time, the only confirmed remediation is to restart the ZPA App Connector service on affected connectors, which has restored connectivity in observed cases but will temporarily disrupt active sessions. Zscaler is actively working on platform-side mitigation and broker-side recovery mechanisms to reduce the need for customer action, and further updates will be provided as they become available.

Update - Fri, 21 Aug 2026 01:40:53 UTC

We are continuing to investigate the ZPA App Connector connectivity issue . At this stage, restarting the ZPA App Connector service on the affected connectors remains the only validated remediation. This action has successfully restored connectivity in observed cases to date. Please note that restarting the App Connector will temporarily disrupt active user sessions. We recommend performing this step in a controlled manner with appropriate stakeholder and end-user communication. Our team continues to work on mitigation measures. Further updates will be shared as additional information becomes available.

Update - Thu, 20 Aug 2026 05:36:57 UTC

Zscaler is investigating an issue affecting ZPA users in China who are unable to connect to China ZPA Public Service Edges (Beijing & Shanghai) and are being redirected to alternate ZPA Public Service Edges outside China. Zscaler is actively engaged and investigating the root cause. We will provide further updates as the investigation progresses.

Update - Thu, 20 Aug 2026 07:03:41 UTC

Zscaler has identified the root cause of the ZPA connectivity issue affecting users in China. The issue was traced to a recent configuration change which has been reverted. Remediation is currently in progress and we are working to confirm full service restoration. We will provide a further update shortly.

Update - Thu, 20 Aug 2026 07:34:55 UTC

Zscaler has mitigated the ZPA connectivity issue affecting users in the China region. The root cause has been identified and resolved, and customers are now connecting to China ZPA Public Service Edges as expected. Customers still experiencing issues are advised to restart the ZCC service.

Update - Wed, 19 Aug 2026 23:20:29 UTC

Zscaler has identified degradation on an external network path and is actively working with the relevant provider to address the issue. Customers currently experiencing service impact may fail over to their secondary data center or another configured alternate data center, as appropriate. We will provide further updates as additional information becomes available.

Update - Thu, 20 Aug 2026 00:40:39 UTC

Zscaler has been actively engaged with the relevant service provider. Service conditions are showing improvement, and we are continuing to monitor closely to ensure sustained stability. Further updates will be shared as they become available.

Update - Thu, 20 Aug 2026 04:42:48 UTC

Zscaler has continued to monitor service conditions for the Mexico City I and Mexico City II Data Centers. We are not observing packet loss, and traffic is flowing normally. We will mark this incident as resolved now.

Update - Wed, 19 Aug 2026 14:28:38 UTC

Zscaler teams are actively working on remediation and validation. Recovery efforts are being carried out in a phased manner across environments to help ensure changes are applied carefully and verified as work progresses.
We will provide another update within 24 hours or sooner if additional confirmed information becomes available.

Update - Thu, 20 Aug 2026 15:30:03 UTC

Remediation is ongoing and good progress is being made. The team has completed updates across a significant portion of the affected environment and is continuing work on the remaining items. Further updates will be shared as remediation progresses.

Update - Thu, 20 Aug 2026 18:44:20 UTC

Remediation has been completed across all affected environments and accounts. All services remain stable, and the incident is now resolved. We will continue to monitor for continued stability.

Update - Mon, 17 Aug 2026 14:07:18 UTC

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

Update - Mon, 17 Aug 2026 14:17:39 UTC

Zscaler has implemented preliminary mitigation measures to address the issue. The team is actively monitoring and evaluating the effectiveness of these measures.

Update - Mon, 17 Aug 2026 14:56:18 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 - Mon, 17 Aug 2026 14:35:30 UTC

Zscaler is observing an issue affecting Audit Logs on the ZIA Admin Portal and Mobile Admin Portal across all clouds since 12:37 UTC on August 17, 2026. Users may experience slow loading pages followed by 504/500 errors. Our teams are actively investigating and working towards resolution. We will provide further updates as the investigation progresses.

Update - Mon, 17 Aug 2026 17:30:59 UTC

We identified elevated load on a legacy backend logging component that contributed to intermittent 504 errors. Mitigation actions have been implemented, service stability has improved.

Update - Tue, 18 Aug 2026 04:20:18 UTC

Zscaler has resolved the issue affecting Audit Logs on the ZIA Admin Portal and Mobile Admin Portal across all clouds. Audit Logs are now fully operational across all clouds.

Update - Fri, 14 Aug 2026 12:40:48 UTC

Zscaler has implemented preliminary mitigation measures to address the issue. The team is actively monitoring and evaluating the effectiveness of these measures.

Update - Fri, 14 Aug 2026 13:16:55 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 - Fri, 14 Aug 2026 11:04:21 UTC

The Zscaler team has identified the issue as delayed reporting and log delivery caused by weblog lag. Our teams are actively prioritizing the incident, evaluating mitigation options, and working to restore normal service.

Update - Fri, 14 Aug 2026 17:07:06 UTC

Zscaler has taken the necessary actions to restore service. Continued monitoring has confirmed that services remain stable, and the incident is now resolved.

Update - Mon, 10 Aug 2026 16:39:38 UTC

We have identified the root cause of the issue and are currently assessing mitigation options and next steps.

Update - Mon, 10 Aug 2026 17:20:15 UTC

We have identified the issue as a software-related regression affecting login access to claude.ai in certain environments. Our engineering team is actively working on a permanent fix, and interim mitigation measures remain in place while that work is underway. We are coordinating across teams and will provide further updates as we have more information on the fix timeline and deployment plan.

Update - Tue, 11 Aug 2026 16:00:44 UTC

Zscaler has completed development of the fix and the validation is currently in progress. Interim mitigations remain in place while verification continues. We will share a further updates, including verification status and next steps once available.

Update - Wed, 12 Aug 2026 03:13:05 UTC

Zscaler has completed development of the fix, and validation is currently in progress. The corrected build is being prepared for further validation and testing. Following successful validation, the fix will be submitted for production deployment. Interim mitigations remain in place while validation continues. We will provide the next update once deployment plans are available.

Update - Wed, 12 Aug 2026 06:54:30 UTC

The fix developed by Zscaler is currently undergoing validation. A corrected build has been prepared and is proceeding through the testing and validation pipeline. Once validation is successfully completed, the fix will be submitted for production deployment. Existing interim mitigations continue to remain active during this period. The next update will be provided when deployment timelines are confirmed.

Update - Wed, 19 Aug 2026 08:06:24 UTC

The fix has been successfully deployed to zscloud.net. Deployment to zscaler.net is currently being scheduled and timelines will be shared shortly. Existing interim mitigations continue to remain active. We will provide a further update once zscaler.net deployment timelines are confirmed.

Update - Wed, 19 Aug 2026 18:30:11 UTC

The fix has been successfully deployed across all data centers on the zscloud.net cloud. For the zscaler.net cloud, the fix has been deployed to all affected data centers, and full deployment will be completed as part of a build upgrade scheduled in September. All existing interim mitigations continue to remain active until full deployment is complete on the zscaler.net cloud.