Trust

Zscaler Client Connector for Virtual Desktop Infrastructure (VDI) Deployment Issue - zscaler.net, zscalerone.net, zscalertwo.net, zscloud.net, zscalerthree.net

Mon, 20 Apr 2026 18:09:46 GMT

Zscaler detected an issue where the existing access token that was generated before April 11, 2026 can not be used to deploy Zscaler Client Connector for VDI. As a workaround customers can create a new access token while the Zscaler team investigates and fixes the issue.

We will continue to provide updates here as the investigation progresses. Status changes and additional details will be posted there as they become available.

Customer Impact:

Customers won’t be able to deploy Zscaler Client Connector for VDI using existing access tokens that were created before April 11 (administrators generate access tokens in the Cloud and Branch Connector portal under Administration > VDI Templates). Administrators will receive "Init Config error" once they try to deploy Zscaler Client Connector for VDI with an existing access token.
Customers running non-persistent VDI deployments and do not have a backup restore mechanism implemented to restore user profiles and config files stored in %programdata%/ZCCVDI. In this case, the agent must re-enroll on every boot using the access token from the golden image. If the golden image contains an access token generated before April 11, every boot will fail with "Init Config error" until the golden image is updated with a new token. Already-enrolled agents in persistent environments are not affected, as they do not need to re-enroll.

Workaround:

Generate a new access token from the Cloud and Branch Connector portal (Administration > VDI Templates) and use the new token for any new deployments
For non-persistent VDI where no user backup/restore was implemented: Update the golden/master image with the new access token, this is critical since the agent re-enrolls on every boot.

ZDX Call Quality Monitoring Issue - zdxcloud.net

Mon, 20 Apr 2026 02:45:53 GMT

Zscaler has identified an issue affecting the Call Quality Monitoring (CQM) feature on the zdxcloud.net cloud. While customers can still access the ZDX portal, they may find Zoom CQM data unavailable or observe missing call quality information. This is a temporary condition, and data is expected to be available later. We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root Cause: Preliminary root cause of the issue is attributed to a recent build upgrade on the CQM feature.

Latest Update - Tue, 21 Apr 2026 03:06:29 UTC

Following the actions previously taken by Zscaler, the incident has been resolved.

Update - Mon, 20 Apr 2026 03:19:31 UTC

Zscaler teams have successfully identified the root cause of the current issue. We have now transitioned to the remediation phase and are working urgently to implement a resolution. We will continue to provide updates as we move toward full service restoration.

Update - Mon, 20 Apr 2026 07:16:11 UTC

Zscaler engineering teams are actively working on a permanent resolution and continue to monitor the environment closely to ensure sustained service stability.

Update - Mon, 20 Apr 2026 08:40:22 UTC

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

Update - Tue, 21 Apr 2026 00:36:15 UTC

Following the applied mitigations, service stability has been maintained with no additional issues observed. Zscaler continues to closely monitor the environment to ensure sustained performance and reliability.

Update - Tue, 21 Apr 2026 03:06:29 UTC

Following the actions previously taken by Zscaler, the incident has been resolved.

Kuala Lumpur I Datacenter Issue - zscaler.net

Sun, 19 Apr 2026 10:28:07 GMT

Zscaler has detected an issue with our Kuala Lumpur I datacenter and is currently investigating the matter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC or any other alternate DC. For more information, please refer to the following support article. We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root Cause- The issue originated with an upstream transit provider.

Latest Update - Mon, 20 Apr 2026 08:01:13 UTC

Based on our continuous monitoring Zscaler is no longer seeing an issue at the Kuala Lumpur I data center, and all services are operating normally. This incident is now marked as resolved

Update - Sun, 19 Apr 2026 10:59:45 UTC

Zscaler is prioritizing the issue and is actively working to isolate the problem and identify the root cause. We appreciate your patience and understanding during this investigation. Additional updates will be provided as more information becomes available.

Update - Sun, 19 Apr 2026 11:42:48 UTC

Zscaler is no longer seeing an issue and all services are operating normally. We will continue to monitor the site to ensure stability.

Update - Mon, 20 Apr 2026 08:01:13 UTC

Based on our continuous monitoring Zscaler is no longer seeing an issue at the Kuala Lumpur I data center, and all services are operating normally. This incident is now marked as resolved

Mumbai VI Data Center Issue - zscaler.net

Sat, 18 Apr 2026 10:23:01 GMT

Zscaler has detected an issue with its Mumbai VI datacenter and is currently investigating the matter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC or any other alternate DC. For more information, please refer to the following support article. We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root Cause: Increased demand on systems in the Mumbai (BOM6) data center caused intermittent performance degradation for a subset of customers; built-in resilience mechanisms mitigated the issue and service has been fully restored.

Latest Update - Mon, 20 Apr 2026 11:57:24 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 - Sat, 18 Apr 2026 11:00:04 UTC

Update - Sat, 18 Apr 2026 13:34:40 UTC

Zscaler observed a period of elevated resource utilization in the Mumbai (BOM6) data center, which may have resulted in intermittent performance degradation for a subset of customers. The condition has been mitigated through built-in platform resilience mechanisms, and service performance has been fully restored. The platform is operating within normal parameters. Zscaler continues to monitor the environment to ensure ongoing stability and will provide additional updates if necessary.

Update - Mon, 20 Apr 2026 11:57:24 UTC

Risk360 – Data Loading issue - zscaler.net, zscalerone.net, zscalertwo.net, zscloud.net, zscalerthree.net, zscalerrisk.net

Thu, 16 Apr 2026 17:38:57 GMT

Zscaler is currently investigating an issue causing computation delays. Latest risk scores and insights may be outdated or unavailable at this time. During this time, your dashboard may reflect historical data; however, your actual security posture and traffic protection are unaffected. We are currently validating a performance optimization and will restore real-time scoring. We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root Cause: A defect in a connector processing workflow caused intermittent run failures, resulting in delayed data updates.

Latest Update - Tue, 21 Apr 2026 04:35:45 UTC

Update - Thu, 16 Apr 2026 18:31:45 UTC

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

Update - Thu, 16 Apr 2026 22:16:02 UTC

Zscaler continues to work toward full resolution of the issue while actively validating mitigation measures. Further updates will be provided as progress continues.

Update - Fri, 17 Apr 2026 12:43:57 UTC

Zscaler continues to work toward full resolution of the issue while actively validating mitigation measures. Further updates will be provided as progress continues.

Update - Sat, 18 Apr 2026 14:20:47 UTC

Zscaler continues to execute mitigation actions to restore full Risk360 functionality. Resolution is taking longer than initially anticipated as teams work through multiple dependencies required to fully restore normal data updates. Zscaler teams remain fully engaged, with continued progress in stabilizing data processing and improving data update timeliness. Further updates will be provided as progress continues. Further updates will be provided as progress continues.

Update - Tue, 21 Apr 2026 04:35:45 UTC

Zscaler identified and corrected an issue affecting a backend workflow. Following a monitored, phased re-enablement across all environments, normal processing has resumed and the incident is now resolved.

Administration UI and User Authentication Issues - zscalerthree.net

Thu, 16 Apr 2026 03:49:20 GMT

Zscaler has detected an issue with the administration UI and user authentication on its zscalerthree.net Cloud. We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root Cause- The preliminary root cause of this issue is attributed to a fault in the control plane.

Latest Update - Thu, 16 Apr 2026 04:33:48 UTC

Following a period of monitoring, the cloud environment has remained stable after the control plane recovered via built-in self-healing mechanisms. The incident is now resolved.

Update - Thu, 16 Apr 2026 04:06:56 UTC

Zscaler observed an issue affecting the control plane. The service recovered automatically via built-in self-healing mechanisms. The issue is now mitigated, and we are actively monitoring the cloud to ensure continued stability.

Update - Thu, 16 Apr 2026 04:33:48 UTC

Following a period of monitoring, the cloud environment has remained stable after the control plane recovered via built-in self-healing mechanisms. The incident is now resolved.

Administration UI and Mobile Admin Portal Issue - zscaler.net, zscalertwo.net, zscloud.net, zscalerthree.net

Wed, 15 Apr 2026 08:37:02 GMT

Zscaler is currently investigating reported issues impacting the Administration UI and Mobile Admin Portal on the zscaler.net, zscalertwo.net, and zscalerthree.net clouds. Customers may experience intermittent slowness, timeouts, and/or increased latency when accessing the Admin UI and/or Mobile Admin Portal.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root Cause- Configuration processing led to resource constraints on Admin UI.

Latest Update - Thu, 16 Apr 2026 16:36:41 UTC

Update - Wed, 15 Apr 2026 09:23:44 UTC

Update - Wed, 15 Apr 2026 10:18:07 UTC

Zscaler is working to isolate the issue and identify the root cause. We have confirmed the issue is also occurring on other clouds, and we have updated the impact cloud accordingly.

Update - Wed, 15 Apr 2026 12:38:45 UTC

The Zscaler team has identified the root cause and is now applying a mitigation. The mitigation has been deployed to the zscaler.net cloud, and our testing indicates improved service performance; the zscaler.net cloud is now in a mitigated state. We are continuing to deploy the mitigation to the remaining clouds, with expected completion within 60 mins.

Update - Wed, 15 Apr 2026 13:37:18 UTC

The mitigation has been successfully deployed to zscalerthree.net, in addition to zscaler.net, and our testing indicates improved service performance. We are continuing to deploy the mitigation to the remaining clouds, with expected completion within 45 minutes.

Update - Wed, 15 Apr 2026 14:14:10 UTC

The mitigation has been successfully deployed to zscloud.net and zscalertwo.net, in addition to zscalerthree.net and zscaler.net. This concludes the mitigation rollout, and we are now moving the incident into a monitoring period to evaluate the effectiveness of these measures.

Update - Thu, 16 Apr 2026 16:36:41 UTC

Certificate Signing Request (CSR) Issue - zscaler.net, zscloud.net, zscalerthree.net

Tue, 14 Apr 2026 14:21:15 GMT

Zscaler is currently investigating reports of issues with the Administration UI on its Cloud. Some customers may be unable to create a new Certificate Signing Request (CSR) because the option is greyed out.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root cause: A software defect in the Administration UI affected the visibility of controls required to add or renew custom intermediate SSL certificates; this was resolved through a platform update.

Latest Update - Wed, 15 Apr 2026 21:58:53 UTC

Zscaler has successfully deployed the fix across the affected cloud environment, and services have been fully restored. The platform is operating normally, and stability has been confirmed. Zscaler will continue to closely monitor the environment to ensure ongoing reliability.

Update - Tue, 14 Apr 2026 14:45:36 UTC

The Zscaler team has identified the issue as a software defect. Zscaler teams are actively prioritizing the incident, implementing the fix, and working to restore services.

Update - Wed, 15 Apr 2026 17:43:17 UTC

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

Update - Wed, 15 Apr 2026 21:58:53 UTC

Administration UI Issue - zscloud.net

Tue, 14 Apr 2026 13:57:42 GMT

Zscaler has detected an issue with the administration UI on its zscloud.net Cloud. Customers may encounter slowness issues logging into Administration UI and Zscaler Client Connector portal.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root Cause- A surge in authentication traffic to a specific Admin UI node caused performance degradation.

Latest Update - Tue, 14 Apr 2026 16:33:30 UTC

Update - Tue, 14 Apr 2026 14:15:45 UTC

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

Update - Tue, 14 Apr 2026 15:13:50 UTC

While we have implemented initial mitigation steps, including a node restart, currently verifying the performance. We are continuing to investigate the issue to restore full service stability.

Update - Tue, 14 Apr 2026 15:27:46 UTC

The Zscaler teams have successfully mitigated the issue, supported by positive feedback from customers. Zscaler continues to monitor the situation closely to ensure ongoing stability and to promptly address any potential reoccurrences or new issues that may arise.

Update - Tue, 14 Apr 2026 16:33:30 UTC

ZDX Admin Portal – Reporting and Logging Delay - zdxcloud.net

Mon, 13 Apr 2026 21:16:56 GMT

Zscaler has detected an issue with Reporting and Logging on its zdxcloud.net Cloud. Customers may experience a temporary delay in reporting data.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root cause- The incident was caused by a performance bottleneck within our backend systems that temporarily delayed data processing

Latest Update - Tue, 14 Apr 2026 00:51:43 UTC

Update - Mon, 13 Apr 2026 21:37:08 UTC

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

Update - Mon, 13 Apr 2026 22:40:02 UTC

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

Update - Tue, 14 Apr 2026 00:51:43 UTC

User Authentication Issues - zscalerthree.net

Sun, 12 Apr 2026 23:26:53 GMT

Zscaler has detected an user authentication issue on its zscalerthree.net Cloud. Customer might experience issues with user authentication services, impacting Zscaler Client Connector (ZCC) login, web traffic authentication and Zscaler Client Connector portal.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root cause- Issue occurred due to service certificate issue.

Latest Update - Mon, 13 Apr 2026 07:08:34 UTC

Zscaler monitored the issue for a period of time and confirmed—based on internal checks and ongoing monitoring—that all systems are operating normally and the issue is resolved.

Update - Sun, 12 Apr 2026 23:32:52 UTC

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

Update - Mon, 13 Apr 2026 00:42:27 UTC

The Zscaler team has identified the issue as being related to service certificate issue. Zscaler teams are actively working to rolling back to a known stable configuration.

Update - Mon, 13 Apr 2026 01:10:59 UTC

We are actively rolling back to a known stable configuration, and services are recovering. We will provide the next update as recovery progresses.

Update - Mon, 13 Apr 2026 02:17:50 UTC

Zscaler has reverted the change and restored the previously valid certificate to address reports of SSL certificate verification failures affecting customers on the ZS3 cloud. The issue is now mitigated, and we are monitoring to ensure stability.

Update - Mon, 13 Apr 2026 07:08:34 UTC

Zscaler monitored the issue for a period of time and confirmed—based on internal checks and ongoing monitoring—that all systems are operating normally and the issue is resolved.

Administration UI and User Authentication Issues - zscalerthree.net

Sat, 11 Apr 2026 02:33:18 GMT

Zscaler has detected an issue with its zscalerthree.net Cloud. We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root Cause: The preliminary root cause of this issue is attributed to a fault in the control plane.

Update - Sat, 11 Apr 2026 02:37:12 UTC

Zscaler observed an issue affecting the control plane. The service recovered automatically via built-in self-healing mechanisms. The issue is now resolved, and we are actively monitoring the cloud to ensure continued stability.

IdP-initiated Authentication Issue - zscaler.net, zscloud.net

Wed, 08 Apr 2026 09:35:18 GMT

Zscaler is currently investigating reports of issues with its zscaler.net, zscloud.net Cloud. Customers using IdP-initiated authentication may experience login failures.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root Cause: The issue occurred due to a recently enabled feature change.

Latest Update - Thu, 09 Apr 2026 12:51:26 UTC

Update - Wed, 08 Apr 2026 10:18:06 UTC

The Zscaler team has identified the issue: previous mitigation efforts did not propagate to a subset of Service Edges. Our teams are actively prioritizing this incident, have identified the fix, and are working to restore services.

Update - Wed, 08 Apr 2026 11:44:42 UTC

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

Update - Wed, 08 Apr 2026 15:21:17 UTC

The issue remains stable and the mitigation continues to hold. We will continue monitoring until 12:00 UTC tomorrow; if stability persists, we will then resolve the incident.

Update - Thu, 09 Apr 2026 12:51:26 UTC

IdP-initiated Authentication Issue - zscaler.net, zscloud.net

Tue, 07 Apr 2026 15:13:26 GMT

Root Cause - The issue occurred due to a recently enabled feature change.

Latest Update - Tue, 07 Apr 2026 20:43:29 UTC

Update - Tue, 07 Apr 2026 15:20: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 - Tue, 07 Apr 2026 20:43:29 UTC

ZDX Admin Portal – Reporting and Logging Delay - zdxcloud.net

Sun, 05 Apr 2026 04:40:08 GMT

Zscaler has detected an issue with the ZDX cloud. Customers may experience a temporary delay in reporting data.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root cause- Issue occurred due to a recent service update.

Latest Update - Fri, 10 Apr 2026 12:26:28 UTC

Update - Sun, 05 Apr 2026 06:39:23 UTC

Zscaler has identified the cause of the issue and implemented mitigation actions. Service has been restored and we continue to closely monitor the environment to ensure stability.

Update - Sun, 05 Apr 2026 18:24:07 UTC

No further issues were observed during the monitoring period. We continue to work toward a permanent resolution.

Update - Mon, 06 Apr 2026 03:31:53 UTC

No issues have been observed during the monitoring period. We have applied mitigations as needed and continue to monitor service health. We are actively working on a permanent resolution to prevent recurrence.

Update - Fri, 10 Apr 2026 12:26:28 UTC

ZDX Admin Portal – Reporting and Logging Delay - zdxcloud.net

Sat, 04 Apr 2026 17:31:16 GMT

Zscaler has detected an issue impacting connectivity between client connector and ZDX cloud. Customers may experience a temporary delay in reporting data.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root cause: A service component within the ZDX cloud was unable to process user authentication information correctly following a recent maintenance activity, resulting in degradation of reporting and data visibility in the ZDX Admin Portal.

Latest Update - Sat, 04 Apr 2026 19:52:00 UTC

Zscaler has confirmed that the issue has been fully resolved, and services have been restored to normal operation. Reporting and data availability within the ZDX Admin Portal are fully functional. Zscaler will continue to monitor the environment to ensure sustained stability.

Update - Sat, 04 Apr 2026 18:24:26 UTC

Zscaler has identified the cause of the issue and implemented mitigation actions. Service restoration is in progress, and improvements are being observed in reporting and data availability within the ZDX Admin Portal. Zscaler continues to closely monitor the environment to ensure stability and full recovery of services.

Update - Sat, 04 Apr 2026 19:52:00 UTC

Private Service Edge (PSE) – Intermittent Traffic Blocking for Explicit Proxy Traffic - zscaler.net, zscalertwo.net, zscloud.net, zscalerthree.net

Sat, 04 Apr 2026 17:10:13 GMT

Zscaler is aware of and actively investigating an issue impacting a subset of customers using Private Service Edge (PSE). Some customers are experiencing intermittent traffic blocking when accessing websites through PSE. Affected requests may return the error: "Web Application Blocked by Firewall Rule."

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root Cause: The root cause of this issue was related to a recently implemented change, which was reverted to restore the services.

Latest Update - Sun, 05 Apr 2026 07:14:32 UTC

Zscaler identified the issue and took necessary actions to resolve it across all clouds.

Update - Sat, 04 Apr 2026 18:32:37 UTC

Zscaler has identified the issue and is actively working on mitigation steps to restore expected traffic handling behavior within the data plane.

Update - Sun, 05 Apr 2026 07:14:32 UTC

Zscaler identified the issue and took necessary actions to resolve it across all clouds.

User Authentication Issue on Kingdom of Saudi Arabia I datacenter - zscaler.net, zscalertwo.net, zscloud.net, zscalerthree.net

Thu, 02 Apr 2026 11:15:33 GMT

Zscaler has detected an issue with its Kingdom of Saudi Arabia I datacenter and is currently investigating the matter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC or any other alternate DC. For more information, please refer to the following support article. We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root Cause - Third-party transit provider issue.

Latest Update - Thu, 02 Apr 2026 18:53:59 UTC

Update - Thu, 02 Apr 2026 11:47:44 UTC

Zscaler has implemented the necessary mitigation measures to address the issue impacting the KSA1 datacenter and services have stabilized. We will continue to closely monitor the environment to ensure sustained stability and will provide further updates if there are any changes.

Update - Thu, 02 Apr 2026 18:53:59 UTC

Chennai II, Hyderabad I, Mumbai VI, Mumbai VII, New Delhi I Datacenter Issue - zscalerthree.net

Wed, 01 Apr 2026 10:36:08 GMT

Zscaler has detected an issue with its Chennai II, Hyderabad I, Mumbai VI, Mumbai VII, New Delhi I datacenter and is currently investigating the matter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC or any other alternate DC. We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root cause- The issue occurred due to a software defect introduced by a recent change.

Latest Update - Thu, 02 Apr 2026 06:02:40 UTC

Zscaler has continued monitoring the environment and confirmed all services are operating normally and as expected. The previously observed impact has cleared, This issue is now resolved.

Update - Wed, 01 Apr 2026 11:23:36 UTC

Zscaler has identified the root cause as a software defect introduced by a recent change, and we will be reverting the change during the change window between 8–10 PM UTC to restore normal service. We will provide the next update as soon as it is available.

Update - Wed, 01 Apr 2026 23:25:53 UTC

We have successfully reverted the change that caused the issue in the affected data centers. We are continuing to monitor the environment for stability.

Update - Thu, 02 Apr 2026 06:02:40 UTC

Zscaler has continued monitoring the environment and confirmed all services are operating normally and as expected. The previously observed impact has cleared, This issue is now resolved.

Administration UI and User Authentication Issues - zscalertwo.net

Tue, 31 Mar 2026 04:56:27 GMT

Zscaler has detected an issue with the administration UI and user authentication on its zscalertwo.net Cloud.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root Cause: The preliminary root cause of this issue is attributed to a fault in the control plane.

Latest Update - Tue, 31 Mar 2026 06:31:18 UTC

Following continued monitoring of the control plane, Zscaler now considers the issue resolved.

Update - Tue, 31 Mar 2026 05:17:49 UTC

Update - Tue, 31 Mar 2026 06:31:18 UTC

Following continued monitoring of the control plane, Zscaler now considers the issue resolved.

Customer Support Portal (CSP) Login Issues - zscaler.net, zscalerone.net, zscalertwo.net, zscloud.net, zscalerthree.net, private.zscaler.com, zdxcloud.net, zpatwo.net

Mon, 30 Mar 2026 21:03:10 GMT

Zscaler is currently investigating an issue impacting Customer Support Portal (CSP) access for a subset of customers. Affected customers may encounter the error message: “Can’t connect to Zscaler Support” when attempting to log in to the CSP.

Workaround: While a fix is being implemented, customers may use the following alternative methods:

If you have Administrative access to another Zscaler product (such as ZIA, ZPA, or ZDX), you can access the Support Portal through that product’s Admin interface and manage or create support cases as needed.
Customers without access to an alternative product Admin portal are advised to contact Zscaler Support via phone for assistance.

Zscaler is actively working to resolve the issue and restore normal access. Further updates will be provided as progress is made.

Latest Update - Tue, 07 Apr 2026 21:17:48 UTC

Update - Thu, 02 Apr 2026 22:02:24 UTC

Zscaler has completed remediation for the majority of impacted customers, and access to the Customer Support Portal (CSP) has been restored. We are performing final validation checks to ensure consistent access across all customers. Further updates will be provided as needed.

Update - Tue, 07 Apr 2026 21:17:48 UTC

ZIA Platform Alerts – Email Notifications Not Being Delivered - zscaler.net, zscalertwo.net, zscloud.net, zscalerthree.net

Fri, 27 Mar 2026 21:26:01 GMT

Zscaler is investigating an issue impacting email notifications for Platform Alerts configured within the ZIA Admin Portal (Under Administration > Define Alerts Page > Alerts). Customers may not be receiving email notifications for alert-triggering events.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root cause- The issue occurred due to resource contention on core notification

Latest Update - Thu, 02 Apr 2026 09:32:00 UTC

Zscaler has implemented the fix to restore normal email notification delivery for configured ZIA Platform Alerts. Services are now working as expected; therefore, we are marking this incident as Resolved.

Update - Sat, 28 Mar 2026 01:01:30 UTC

Zscaler continues to investigate the root cause of the issue and is actively working on a fix to restore normal email notification delivery. Further updates will be provided as progress is made.

Update - Thu, 02 Apr 2026 07:43:22 UTC

Zscaler is in the final phase of implementing a fix to restore normal email notification delivery. Checks and validation are in progress, and we will provide an update shortly once the fix is deployed.

Update - Thu, 02 Apr 2026 09:32:00 UTC

Cloud Browser Isolation issue for Frankfurt Region - zscaler.net, zscalerone.net, zscalertwo.net, zscloud.net, zscalerthree.net, private.zscaler.com

Wed, 25 Mar 2026 14:27:03 GMT

Zscaler has identified an issue with Cloud Browser Isolation (CBI) impacting customers in Frankfurt Region. Affected customers may experience issue with new isolation session for Frankfurt region.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Update - Wed, 25 Mar 2026 14:36:16 UTC

Zscaler took necessary steps to mitigated the issue. Customer are now able to create new new isolation session for Frankfurt region. We are considering this incident as resolved.

Update - Wed, 25 Mar 2026 14:36:28 UTC

This incident has been resolved. Please contact Zscaler Support if you have additional questions.

Oslo III Datacenter Issue - zscaler.net, zscalertwo.net, zscloud.net, zscalerthree.net

Wed, 25 Mar 2026 13:06:29 GMT

Zscaler has detected an issue with its Oslo III datacenter and is currently investigating the matter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC or any other alternate DC. For more information, please refer to the following support article.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root Cause- Issue was related to Hardware Maintenance.

Latest Update - Wed, 25 Mar 2026 14:47:15 UTC

Update - Wed, 25 Mar 2026 13:29:50 UTC

Following further investigation, it was confirmed that the alerts were caused by Urgent Hardware Maintenance (https://trust.zscaler.com/zscaler.net/posts/28671). The hardware replacement is now complete, and all associated alerts have been cleared

Update - Wed, 25 Mar 2026 14:47:15 UTC

Abu Dhabi I and Dubai II Data Center Issue - zscloud.net

Mon, 23 Mar 2026 06:31:53 GMT

Zscaler has detected an issue with its Abu Dhabi I and Dubai II datacenter on the zcloud.net cloud and is currently investigating the matter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC or any other alternate DC. For more information, please refer to the following support article.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root cause- The issue occurred due to a routing error that impacted a limited subset of customers.

Latest Update - Mon, 23 Mar 2026 11:28:17 UTC

Based on continuous monitoring and positive customer feedback, we have confirmed that the issues have subsided and the mitigation remains stable. Consequently, we are marking this incident as resolved.

Update - Mon, 23 Mar 2026 07:05:38 UTC

We are making progress in isolating the cause of the issue and further updates will be shared as available.

Update - Mon, 23 Mar 2026 08:14:41 UTC

We have identified the issue as an incorrect routing configuration and are actively implementing corrective changes. Service has been restored on a portion of the affected infrastructure. We are continuing remediation on the remaining components while monitoring stability and validating full restoration of BGP sessions and route advertisements. Additional updates will be provided once validation is complete.

Update - Mon, 23 Mar 2026 08:28:51 UTC

Zscaler team has resolved the routing issue that impacted a limited subset of customers. The issue was caused by a routing configuration problem that affected BGP route advertisements, which prevented some customer traffic from being routed normally. Corrective changes have been applied across the affected infrastructure and service has stabilized. We are continuing to monitor to ensure ongoing routing health and will provide additional updates if conditions change.

Update - Mon, 23 Mar 2026 11:28:17 UTC

Dubai I Data Center Issue - zscloud.net

Mon, 23 Mar 2026 05:50:02 GMT

Zscaler has detected an issue with its Dubai I datacenter on zscloud.net and is currently investigating the matter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC or any other alternate DC. For more information, please refer to the following support article.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root cause- The issue occurred due to a routing error that impacted a limited subset of customers.

Latest Update - Mon, 23 Mar 2026 11:27:14 UTC

Update - Mon, 23 Mar 2026 06:17:40 UTC

We are investigating the issue and have expanded the scope of impact to include the Abu Dhabi I and Dubai II data center as well. A separate trust is posted for the same.

Update - Mon, 23 Mar 2026 07:03:25 UTC

We are making progress in isolating the cause of the issue and further updates will be shared as available.

Update - Mon, 23 Mar 2026 08:13:53 UTC

Update - Mon, 23 Mar 2026 08:29:49 UTC

Update - Mon, 23 Mar 2026 11:27:14 UTC

Canberra I Data Center Issue - zscalerthree.net

Mon, 23 Mar 2026 04:47:00 GMT

Zscaler has detected an issue with its Canberra I datacenter on the zscalerthree.net cloud and is currently investigating the matter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC or any other alternate DC. For more information, please refer to the following support article.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root Cause: A software issue caused a subset of our DLP scanning nodes to become unstable, resulting in brief interruptions and elevated errors for DLP inspection for some customers.

Latest Update - Tue, 24 Mar 2026 05:00:15 UTC

Following the actions previously taken by Zscaler, our systems remain fully operational and the incident has been resolved.

Update - Mon, 23 Mar 2026 06:00:46 UTC

Zscaler is prioritizing this issue and is actively working to mitigate the problem. We appreciate your patience and understanding during this investigation. Additional updates will be provided as more information becomes available.

Update - Mon, 23 Mar 2026 07:52:24 UTC

Zscaler has implemented mitigation measures to resolve the recent service disruption. Service stability has been restored, and we will continue to monitor the environment for an extended period to ensure continued performance. We appreciate your patience during this time.

Update - Mon, 23 Mar 2026 19:18:21 UTC

Services have remained stable following mitigation, and Zscaler continues to monitor to ensure sustained service stability.

Update - Tue, 24 Mar 2026 05:00:15 UTC

Following the actions previously taken by Zscaler, our systems remain fully operational and the incident has been resolved.

ZIdentity Portal Issue - zslogin.net

Sat, 21 Mar 2026 11:35:23 GMT

Zscaler is investigating an issue with the ZIdentity Portal on the zslogin.net Cloud. We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root cause- The issue occurred due to a recent service update.

Update - Sat, 21 Mar 2026 12:10:56 UTC

The Zscaler team has identified the root cause and implemented the necessary measures to resolve the issue; this incident is now resolved.

Capetown IV Datacenter Issue - zscaler.net, zscalertwo.net, zscloud.net, zscalerthree.net

Sat, 21 Mar 2026 11:12:21 GMT

Zscaler has detected an issue with our Capetown IV datacenter and is currently investigating the matter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC or any other alternate DC. For more information, please refer to the following support article.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root Cause - Issue was related to fiber in third party network provider infrastructure.

Latest Update - Mon, 23 Mar 2026 16:26:20 UTC

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

Update - Sat, 21 Mar 2026 11:34:01 UTC

Update - Sat, 21 Mar 2026 15:02:04 UTC

Zscaler has identified intermittent packet loss on a network path impacting connectivity between the Cape Town (CPT4) data center and backend services. This resulted in intermittent service degradation for a subset of customers. As part of mitigation, traffic has been rerouted to alternate infrastructure paths, which are demonstrating improved stability and performance. Zscaler is working with the network provider, who has confirmed a fiber outage as the underlying cause. Repair activities are expected to begin shortly. Zscaler continues to apply mitigation measures and closely monitor the situation. Further updates will be provided as more information becomes available.

Update - Sat, 21 Mar 2026 16:42:25 UTC

The network provider has confirmed that the issue within their infrastructure has been resolved. Zscaler has validated that services are restored and operating normally, with stability observed following the mitigation measures implemented earlier. We will continue to monitor closely to ensure ongoing service stability.

Update - Mon, 23 Mar 2026 16:26:20 UTC

User Authentication Issue on Sao Paulo II - zscaler.net, zscalertwo.net, zscloud.net

Thu, 19 Mar 2026 04:47:59 GMT

Zscaler has detected an issue with its Sao Paulo II datacenter and is currently investigating the matter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC or any other alternate DC. For more information, please refer to the following support article.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root cause- The issue occurred due to resource contention on some nodes

Latest Update - Tue, 07 Apr 2026 04:29:36 UTC

Zscaler has been monitoring the Sao Paulo II (SAO2) datacenter following the previously reported recurring issue. We have not observed any further impact, and services are operating as expected. The issue is now resolved. We will continue to monitor closely to ensure ongoing stability.

Update - Thu, 19 Mar 2026 05:51:21 UTC

We have confirmed that services are now working as expected and the issue stands as mitigated. While performance has stabilized, our teams remain in a state of high vigilance and will continue to monitor the infrastructure closely to ensure a seamless experience for all users.

Update - Fri, 20 Mar 2026 04:45:03 UTC

The previously mitigated issue at the Sao Paulo II datacenter has resurfaced. Our teams are investigating the recurrence further and checking for the root cause.

Update - Fri, 20 Mar 2026 06:24:22 UTC

Zscaler has successfully mitigated the impact. While a permanent fix remains under investigation, the team will continue to monitor the environment closely for extended period of time. Should the issue recur, we will perform targeted restarts of the impacted instances as a temporary corrective measure.

Update - Tue, 07 Apr 2026 04:29:36 UTC

Zscaler Client Connector (ZCC) Authentication Issues - zscalerone.net

Wed, 18 Mar 2026 19:32:45 GMT

Zscaler is aware and investigating reports on an issue with ZCC Network errors on its zscalerone.net Cloud. Affected users may experience 'network connection failed' errors when attempting to log into Zscaler Client Connector (ZCC). Users who are already logged in can access services normally.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root cause: The issue was caused by an unresponsive authentication component, resulting in intermittent authentication failures for a subset of users. A detailed Root Cause Analysis (RCA) will be shared separately.

Latest Update - Wed, 18 Mar 2026 22:39:23 UTC

Update - Wed, 18 Mar 2026 20:27:45 UTC

Zscaler has taken necessary actions to mitigate the issue. We are monitoring the environment for continued stability.

Update - Wed, 18 Mar 2026 22:39:23 UTC

Zscaler Microsegmentation Log Forwarding Issue - private.zscaler.com

Mon, 16 Mar 2026 17:24:15 GMT

Zscaler is investigating an issue with the Zscaler Microegmentation's log forwarding service via Log Streaming Service (LSS) on its private.zscaler.com cloud. The logs forwarding via LSS is temporarily disabled. This does not impact the core Microsegmentation functionality and all the logs will continue to be visible in the Administration UI.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root cause: The issue was caused by a software defect in the service responsible for processing and forwarding logs for Zscaler Microsegmentation.

Latest Update - Thu, 19 Mar 2026 22:38:01 UTC

Zscaler has implemented the necessary fix, and log forwarding via LSS has been fully restored. Post-deployment monitoring confirms the service is operating as expected, and services have returned to normal.

Update - Mon, 16 Mar 2026 23:07:42 UTC

To further mitigate potential impact, log forwarding via LSS has been temporarily disabled while Zscaler teams actively investigate the root cause and implement the necessary fix.

Update - Wed, 18 Mar 2026 01:02:33 UTC

Zscaler has identified a mitigation and are currently validating the fix. Upon successful validation, the change will be deployed to the production, following which log forwarding via LSS will be restored. Zscaler will continue to provide updates as progress is made.

Update - Thu, 19 Mar 2026 22:38:01 UTC

Zscaler Client Connector Portal Issue - zscaler.net, zscloud.net, zscalerthree.net

Mon, 16 Mar 2026 07:23:53 GMT

Zscaler has detected an issue with Zscaler Client Connector Portal Issue on its zscalerthree.net Cloud. We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root cause- The issue was caused by a software defect introduced during a recent system update.

Latest Update - Mon, 16 Mar 2026 11:24:10 UTC

Based on our continuous monitoring, we have confirmed that all services are working as expected and performing within normal parameters. Consequently, we are now marking this incident as Resolved.

Update - Mon, 16 Mar 2026 07:55:31 UTC

Zscaler has identified the root cause and is actively working on a fix. We appreciate your patience and understanding as we resolve this issue. Additional updates will be provided as more information becomes available.

Update - Mon, 16 Mar 2026 09:08:24 UTC

Zscaler has successfully deployed the software fix to address the ongoing service disruption. The Incident is now resolved, and all portal features have been restored to normal operation.

Update - Mon, 16 Mar 2026 09:36:42 UTC

The issue previously identified on the ZS3 cloud has resurfaced on the ZSN cloud. Although initial reports were limited to ZS3, we are now extending the fix to both the ZSN and ZSC clouds to ensure a full resolution across all impacted environments.

Update - Mon, 16 Mar 2026 09:58:56 UTC

The fix has now been extended to the ZSN cloud, and service should be restored for all affected customers. Deployment of the fix for the ZSC cloud is currently in progress and is expected to be completed shortly as a proactive measure to ensure stability. While the deployment is ongoing, internal monitoring indicates that the ZSC cloud remains stable with no active issues reported.

Update - Mon, 16 Mar 2026 10:33:41 UTC

The fix has now been extended to the ZSC cloud, and service should be restored for all affected customers. The issue is now mitigated; however, we will continue monitoring the environment for some time to ensure ongoing stability.

Update - Mon, 16 Mar 2026 11:24:10 UTC

Based on our continuous monitoring, we have confirmed that all services are working as expected and performing within normal parameters. Consequently, we are now marking this incident as Resolved.

Zscaler Client Connector-Based End User Notifications Issue - zscaler.net

Sat, 14 Mar 2026 05:59:41 GMT

Zscaler has detected an issue with Zscaler Client Connector-Based End User Notifications on its zscaler.net Cloud.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root Cause- Issue was related to node.

Update - Sat, 14 Mar 2026 06:52:20 UTC

Zscaler has implemented mitigation measures, and the incident is now resolved. Our systems remain fully operational, and we will continue to monitor the situation closely to ensure ongoing stability.

Oslo III Datacenter Issue - zscaler.net, zscalertwo.net, zscloud.net, zscalerthree.net

Fri, 13 Mar 2026 12:36:08 GMT

Zscaler has detected an issue with our Oslo III datacenter and is currently investigating the matter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC or any other alternate DC. For more information, please refer to the following support article.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root cause- Issue was related to faulty hardware.

Latest Update - Fri, 13 Mar 2026 13:53:24 UTC

Zscaler infrastructure team identified a faulty network switch through proactive monitoring. The issue was resolved by bypassing the defective hardware and rerouting traffic through a redundant backup switch. Connectivity has been fully restored and remains stable.

Update - Fri, 13 Mar 2026 12:52:33 UTC

Service has stabilized and alerts have cleared. We remain in a period of active monitoring while we investigate the root cause of the disruption.

Update - Fri, 13 Mar 2026 13:53:24 UTC

Zscaler Client Connector-Based End User Notifications Issue - zscaler.net

Fri, 13 Mar 2026 11:44:55 GMT

Root cause- Issue was related to node.

Update - Fri, 13 Mar 2026 12:16:51 UTC

Administration UI and User Authentication Issues - zscaler.net

Thu, 12 Mar 2026 09:12:53 GMT

Zscaler has detected an issue with the administration UI and user authentication on its zscaler.net Cloud.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root Cause: A Central Authority (CA) issue triggered a CA re-election.

Latest Update - Thu, 12 Mar 2026 12:22:02 UTC

Update - Thu, 12 Mar 2026 09:29:52 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, 12 Mar 2026 12:22:02 UTC

Reporting and Logging Issue - zscaler.net, zscalerone.net, zscalertwo.net, zscloud.net, zscalerthree.net

Wed, 11 Mar 2026 11:09:23 GMT

Zscaler is currently investigating reports of issues with Reporting and Logging on its zscaler.net, zscalerone.net, zscalertwo.net, zscloud.net, zscalerthree.net Cloud. Your organization's policies are being enforced. All user logs are being collected and will be available at the resolution of this incident.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root Cause: Zscaler has applied a mitigation to address the issue affecting report retrieval in the ZIA portal. Reports and data are now accessible again.

Latest Update - Wed, 11 Mar 2026 13:09:13 UTC

Update - Wed, 11 Mar 2026 12:05:41 UTC

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

Update - Wed, 11 Mar 2026 13:09:13 UTC

Washington DC Issue - zscalertwo.net

Tue, 10 Mar 2026 14:32:17 GMT

Zscaler has detected an issue with its Washington DC datacenter and is currently investigating the matter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC or any other alternate DC. For more information, please refer to the following support article.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root cause- The issue occurred due to irregular traffic forwarding behavior.

Latest Update - Tue, 10 Mar 2026 18:06:03 UTC

Update - Tue, 10 Mar 2026 15:17:51 UTC

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

Update - Tue, 10 Mar 2026 18:06:03 UTC

Tianjin Datacenter Issue - zscaler.net

Tue, 10 Mar 2026 13:31:07 GMT

Zscaler has detected an issue with its Tianjin datacenter and is currently investigating the matter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC or any other alternate DC. For more information, please refer to the following support article.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root cause- Service was restored following a targeted node restart to address a localized resource contention issue.

Update - Tue, 10 Mar 2026 13:31:07 UTC

Degradation in DLP functionality - zscalertwo.net

Fri, 06 Mar 2026 05:22:57 GMT

Zscaler has detected an issue with its DLP - EDM and IDM functionality on the zscalertwo.net Cloud. A subset of customers in the AMER region may experience partial disruption of DLP - EDM and IDM functionality, along with performance degradation due to increased latency in the DLP inspection flow.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root cause: A software defect affecting components of the Data Loss Prevention (DLP) EDM and IDM inspection services caused intermittent disruption and increased processing latency for a subset of customers in the AMER region.

Latest Update - Sat, 07 Mar 2026 00:24:23 UTC

The fix has been implemented and the service has remained stable during monitoring. We are proceeding to resolve this incident.

Update - Fri, 06 Mar 2026 12:52:57 UTC

The Zscaler team has identified the issue as being related to specific software build . Zscaler teams are actively prioritizing the incident, exploring various mitigation options, and working to restore service for all affected traffic.

Update - Fri, 06 Mar 2026 18:14:02 UTC

Zscaler has developed and validated a fix for the issue. Deployment of the update is currently being scheduled, after which the service will be validated to confirm stability. Further updates will be provided once deployment is complete or if there are any significant changes.

Update - Sat, 07 Mar 2026 00:24:23 UTC

The fix has been implemented and the service has remained stable during monitoring. We are proceeding to resolve this incident.

Washington DC IV Datacenter Issue - zscaler.net, zscalertwo.net, zscloud.net, zscalerthree.net

Thu, 05 Mar 2026 16:14:34 GMT

Zscaler has detected an issue with its Washington DC IV datacenter and is currently investigating the matter. Some customers may encounter difficulties with DNS resolution. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC or any other alternate DC. For more information, please refer to the following support article.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root cause- The incident occurred due to a synchronization issue on a subset of Zscaler's DNS resolvers.

Latest Update - Thu, 05 Mar 2026 19:41:11 UTC

Following successful remediation, DNS services have returned to normal. Our teams continue to monitor all systems to ongoing stability.

Update - Thu, 05 Mar 2026 16:44:12 UTC

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

Update - Thu, 05 Mar 2026 18:17:25 UTC

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

Update - Thu, 05 Mar 2026 19:41:11 UTC

Following successful remediation, DNS services have returned to normal. Our teams continue to monitor all systems to ongoing stability.

Brussels II Datacenter Issue - zscaler.net, zscloud.net

Mon, 02 Mar 2026 06:25:38 GMT

Zscaler has detected an issue with our Brussels II datacenter on the zscaler.net and the zscloud.net clouds, and is currently investigating the matter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC or any other alternate DC. For more information, please refer to the following support article.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root cause: The issue was caused by a hardware fault impacting a network device within the infrastructure.

Latest Update - Mon, 16 Mar 2026 22:50:13 UTC

The impacted network hardware has been replaced. Validation checks confirmed that the infrastructure is operating normally and service health has been restored. The incident has been resolved, and normal service operations have resumed.

Update - Mon, 02 Mar 2026 10:55:35 UTC

The Zscaler team has identified the issue as being related to faulty hardware. Zscaler teams are actively prioritizing the incident, exploring various mitigation options, and working to restore service for all affected traffic.

Update - Mon, 02 Mar 2026 14:28:32 UTC

Zscaler is coordinating closely with the data center team to replace the faulty hardware. We expect shipment and deployment to be completed within 2–3 days and will provide a follow-up once the replacement is completed.

Update - Fri, 06 Mar 2026 02:44:22 UTC

As per the latest confirmation from the data center team, the replacement hardware is expected to arrive by 10th March, 2026. We will share more updates as available.

Update - Tue, 10 Mar 2026 04:16:42 UTC

As per the latest confirmation from the data center team, the replacement hardware is now expected to arrive by 13th March,2026. We will continue to monitor the situation closely and will share further updates as they become available.

Update - Fri, 13 Mar 2026 09:20:16 UTC

Zscaler has received an update from the courier confirming that the replacement hardware has cleared customs and is pending arrival at the delivery destination. We will continue to monitor the situation closely and will provide further updates as they become available.

Update - Mon, 16 Mar 2026 04:31:48 UTC

Zscaler is following up with the data center team to check the latest status of the shipment and further updates will be shared when available.

Update - Mon, 16 Mar 2026 13:08:40 UTC

The replacement hardware has arrived onsite, Zscaler teams are currently working on the swap. We’ll share a further update once the switch replacement is complete.

Update - Mon, 16 Mar 2026 22:50:13 UTC

Cloud Browser Isolation service impacted in Middle East (UAE) - zscaler.net, zscalerone.net, zscalertwo.net, zscloud.net, zscalerthree.net

Sun, 01 Mar 2026 17:16:11 GMT

Zscaler has identified an issue with Cloud Browser Isolation (CBI) impacting customers in Middle East (UAE). Affected customers may experience difficulties when attempting to create new sessions.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root cause: A disruption to AWS infrastructure services in the UAE region temporarily impacted the availability of the Cloud Browser Isolation (CBI) service hosted in that region.

Latest Update - Thu, 05 Mar 2026 23:05:47 UTC

Zscaler has redirected Cloud Browser Isolation (CBI) traffic to alternate operational regions, and the service is currently operating normally. Users configured to use the UAE isolation region may temporarily be served from a secondary configured region. Once infrastructure services in the UAE region are fully restored, traffic will automatically and seamlessly transition back.

Update - Sun, 01 Mar 2026 18:41:26 UTC

Initial findings indicate that this issue is related to an AWS service issue within Availability Zone mec1-az2 in the ME-CENTRAL-1 region. Until their services are restored the customers can chose to change the regions selection in Admin Portal within each Isolation profile. Please refer the help guide

Update - Sun, 01 Mar 2026 23:35:43 UTC

Zscaler is seeing positive signs of recovery for Cloud Browser Isolation (CBI) following AWS mitigation of underlying EC2 API issues. Success rates for session creation have significantly improved, and customers can now successfully initiate new CBI sessions. We continue to monitor the environment to ensure full stability.

Update - Mon, 02 Mar 2026 04:53:33 UTC

Following the actions taken by AWS to mitigate the issue, this incident is now resolved.

Update - Mon, 02 Mar 2026 07:33:54 UTC

The issue is still ongoing and we are investigating the same. Further updates will be shared as available.

Update - Mon, 02 Mar 2026 12:42:24 UTC

AWS continues to report a service health issue in Availability Zone mec1-az2 within the ME-CENTRAL-1 region. Until services are restored, customers can change the region selection in the Admin Portal for each Isolation profile. Please refer to the help guide shared in the workaround field.

Update - Mon, 02 Mar 2026 15:06:16 UTC

Zscaler has proactively disabled the ME-CENTRAL-1 region following significant infrastructure impairments within AWS Availability Zones mec1-az2 and mec1-az3. While traffic is automatically rerouting to secondary regions, AWS reports that facility recovery including repairs to power and cooling systems will take at least 24 hours.

Update - Tue, 03 Mar 2026 14:08:04 UTC

Zscaler has redirected traffic from the ME-CENTRAL-1 (UAE) region to users' secondary isolation regions due to AWS issues. We will restore normal routing to the UAE region once AWS resolves the underlying incident at their facility.

Update - Wed, 04 Mar 2026 19:11:35 UTC

Following the successful redirection of traffic, no further issues related to the Cloud Browser Isolation (CBI) service have been identified. We remain in a monitoring period to ensure continued service stability and performance.

Update - Thu, 05 Mar 2026 23:05:47 UTC

Beijing III, Shanghai Datacenter Issue - zscaler.net

Sat, 28 Feb 2026 13:41:22 GMT

Zscaler has detected an issue with our Beijing III, Shanghai datacenter and is currently investigating the matter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC or any other alternate DC. For more information, please refer to the following support article.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root cause: An external network connectivity issue affecting international internet paths caused certain services in our China data centers to be temporarily identified as unavailable.

Latest Update - Sat, 28 Feb 2026 16:29:11 UTC

Based on telemetry and ongoing monitoring, services have remained stable following the corrective actions implemented. As a result, this incident is now being resolved.

Update - Sat, 28 Feb 2026 14:14:41 UTC

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

Update - Sat, 28 Feb 2026 14:29:25 UTC

Zscaler has identified the cause of the issue and implemented corrective actions to mitigate the impact. Services have stabilized, and monitoring remains in place to ensure continued stability.

Update - Sat, 28 Feb 2026 16:29:11 UTC

Based on telemetry and ongoing monitoring, services have remained stable following the corrective actions implemented. As a result, this incident is now being resolved.

Connectivity Issues Affecting India Data Centers - zscaler.net, zscalertwo.net, zscloud.net, zscalerthree.net, private.zscaler.com, zpatwo.net

Sat, 28 Feb 2026 10:17:14 GMT

Zscaler has detected an issue with its Chennai II, Hyderabad I, Kolkata I, Mumbai VI, Mumbai VII, New Delhi I datacenter and is currently investigating the matter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC or any other alternate DC. For more information, please refer to the following support article.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root Cause: The incident was caused by upstream international network congestion correlated with ongoing remediation activities on the Europe India Gateway (EIG) submarine cable system, external to Zscaler infrastructure.

Latest Update - Mon, 02 Mar 2026 18:16:29 UTC

Over the past 48 hours, upstream network conditions have remained stable, and continued monitoring and validation confirm that Zscaler services are operating normally with performance within expected levels across affected regions. Based on sustained service stability, this incident is now considered resolved.

Update - Sat, 28 Feb 2026 12:23:37 UTC

Zscaler has identified a connectivity disruption affecting multiple India data centers. The issue is due to upstream international network congestion linked to transcontinental fiber impairments. Customers may experience increased latency, slowness, and degraded performance when accessing US- and Europe-hosted destinations via ZIA and ZPA. For immediate resolution we suggest to divert traffic to an alternate DC.

Update - Sat, 28 Feb 2026 15:07:40 UTC

Zscaler has observed that network connectivity has stabilized and services are fully reachable. Continued validation and monitoring confirm that performance is operating within expected levels. The disruption was associated with prolonged subsea cable issues impacting international network paths, resulting in transient connectivity loss between regions. Zscaler teams will continue investigating upstream network paths and may engage with relevant partners as needed to further isolate contributing factors. At this time, services remain stable, and enhanced monitoring is in place to ensure continued reliability.

Update - Sat, 28 Feb 2026 19:27:38 UTC

Zscaler conducted further investigation and collaborated with a telecom partner to review upstream international network conditions affecting connectivity. Based on this analysis, the observed disruption was correlated with ongoing remediation activities associated with the Europe India Gateway (EIG) submarine cable system, which contributed to periodic congestion, increased latency, and packet loss between India and regions including the US and Europe.

If you continue to observe periodic congestion, latency, or packet loss affecting specific services or applications, please contact Zscaler Support and reference the impacted service or application along with relevant details. Zscaler teams will evaluate traffic paths and perform path optimization where applicable. Services remain stable, and monitoring continues to ensure ongoing reliability.

Update - Sun, 01 Mar 2026 19:40:53 UTC

Zscaler continues to monitor international network conditions impacting connectivity between India data centers and destinations hosted in the US and Europe. Services remain stable and reachable, and current performance is operating within expected levels. Our investigation and partner engagement indicate the prior intermittent congestion, elevated latency, and packet loss were associated with upstream remediation activities on the Europe India Gateway (EIG) submarine cable system. Zscaler has implemented enhanced monitoring and is continuing to evaluate routing and traffic paths for additional optimization opportunities where applicable. Customers who continue to observe periodic latency, slowness, or packet loss for specific applications should contact Zscaler Support and provide the affected application/service, the impacted source/destination regions, timestamps, and any traceroute/packet-loss evidence to assist with path analysis.

Update - Mon, 02 Mar 2026 18:16:29 UTC

Connectivity Issues Affecting India Data Centers - zscaler.net, zscalertwo.net, zscloud.net, zscalerthree.net, private.zscaler.com, zpatwo.net

Fri, 27 Feb 2026 21:11:33 GMT

Zscaler has detected an issue with our Chennai II, Hyderabad I, Kolkata I, Mumbai VI, Mumbai VII, New Delhi I datacenter and is currently investigating the matter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC or any other alternate DC. For more information, please refer to the following support article.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root Cause: The incident was caused by upstream international network congestion related to transcontinental fiber issues external to Zscaler infrastructure.

Latest Update - Sat, 28 Feb 2026 00:52:38 UTC

Continued monitoring and validation confirm that services are operating at expected levels. We are proceeding to resolve this incident.

Update - Fri, 27 Feb 2026 21:41:08 UTC

Zscaler investigated the connectivity disruption and determined the issue was caused by upstream international network congestion associated with transcontinental fiber issues. The impact occurred between 19:50 and 21:00 UTC. Services have since recovered, and Zscaler is currently operating normally. We will continue to monitor service stability to ensure ongoing performance.

Update - Sat, 28 Feb 2026 00:52:38 UTC

Continued monitoring and validation confirm that services are operating at expected levels. We are proceeding to resolve this incident.

Tianjin Datacenter Issue - zscalertwo.net

Fri, 27 Feb 2026 05:40:43 GMT

Root Cause: The issue was caused by a brief interruption to an IPSec traffic processing component within the data center.

Update - Fri, 27 Feb 2026 05:40:43 UTC

The issue recovered without any manual intervention from Zscaler, and the incident has been resolved.

Sao Paulo II Datacenter Issue - zscloud.net

Fri, 27 Feb 2026 03:44:52 GMT

Root Cause: Root cause of the issue is attributed to a IPSEC traffic processing component being down in the data center.

Update - Fri, 27 Feb 2026 04:03:24 UTC

Following the actions taken by Zscaler, the incident has been resolved.

Chicago II (CHI2), San Francisco IV (SJC4) and Los Angeles II (QLA2) Datacenter Issue - zscaler.net, zscalertwo.net

Thu, 26 Feb 2026 17:23:57 GMT

Zscaler is aware of a issue with its Chicago II datacenter and is currently investigating the matter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC or any other alternate DC. For more information, please refer to the following support article.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root Cause: The issue was caused by a configuration error introduced during a recent infrastructure optimization change, which impacted traffic processing on a limited subset of service nodes and resulted in increased latency for affected customers.

Latest Update - Fri, 27 Feb 2026 23:46:18 UTC

Based on our telemetry and monitoring, service performance has remained stable. Following the corrective actions implemented by Zscaler, the incident has been resolved. All systems are operating normally.

Update - Thu, 26 Feb 2026 18:16:11 UTC

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

Update - Thu, 26 Feb 2026 18:35:58 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, 26 Feb 2026 23:33:37 UTC

Mitigation measures implemented in the Chicago II (CHI2) data center within the zscalertwo.net cloud continue to remain effective, and we have received positive customer feedback confirming service stability. During continued analysis, a similar anomaly was identified in the San Francisco IV (SJC4) data center within the zscalertwo.net cloud and the Los Angeles II (QLA2) data center within the zscaler.net cloud. Zscaler has applied the necessary fix in these locations, and the service is operating normally. We continue to monitor closely to ensure sustained stability and will provide further updates based on ongoing system observations and customer feedback.

Update - Fri, 27 Feb 2026 23:46:18 UTC

Zscaler Client Connector Enrollment Failures - zscalertwo.net

Tue, 24 Feb 2026 22:28:57 GMT

Zscaler is aware of an issue impacting Zscaler Client Connector (ZCC) enrollment, where some users may encounter the error: "Zscaler Client Connector was unable to enroll at this time."

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root cause: A temporary service condition within the Zscaler control plane enrollment service resulted in intermittent delays for Zscaler Client Connector (ZCC) new device enrollment and sign-in requests during the impact window. A detailed Root Cause Analysis (RCA) will be shared once the review is complete.

Latest Update - Wed, 25 Feb 2026 00:35:41 UTC

Further monitoring has confirmed stable service performance, and the incident is now resolved.

Update - Tue, 24 Feb 2026 23:19:41 UTC

During the course of our investigation, the issue self-resolved without manual intervention. Zscaler teams have continued to monitor the environment and have observed stable system performance. Further analysis is ongoing to validate the underlying cause and preventative measures. We will provide additional updates as appropriate.

Update - Wed, 25 Feb 2026 00:35:41 UTC

Further monitoring has confirmed stable service performance, and the incident is now resolved.

Endpoint Data Loss Prevention (DLP) Service Issues - zscaler.net, zscloud.net, zscalerthree.net

Tue, 24 Feb 2026 13:42:57 GMT

Zscaler has identified an issue with the Endpoint Data Loss Prevention (DLP) and incident logging services on the zscaler.net, zscloud.net, zscalerthree.net Cloud. As a result, some customers may experience issues with enforcing new policies. However, please note that existing policies are still being enforced as expected. The impact is limited to some customers.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root Cause: A known software defect caused the Endpoint DLP Gateway (EDPG) process to repeatedly crash and be restarted across multiple clouds.

Latest Update - Thu, 26 Feb 2026 03:36:14 UTC

Zscaler has completed the cloud-wide deployment of the fix across all remaining EDPG instances as of 01:00 UTC, 26 Feb. The issue is resolved and services are operating normally.

Update - Tue, 24 Feb 2026 16:00:46 UTC

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

Update - Tue, 24 Feb 2026 19:34:20 UTC

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

Update - Wed, 25 Feb 2026 05:44:12 UTC

Zscaler has developed a fix and is deploying it cloud-wide in a phased manner, and it is expected to be complete by 01:00 UTC, 26 Feb.

Update - Thu, 26 Feb 2026 03:36:14 UTC

Zscaler has completed the cloud-wide deployment of the fix across all remaining EDPG instances as of 01:00 UTC, 26 Feb. The issue is resolved and services are operating normally.

Beijing IV, Beijing V, Shanghai VI Datacenter Issue - zscaler.net, zscalertwo.net, zscloud.net, zscalerthree.net

Fri, 20 Feb 2026 13:31:15 GMT

Zscaler has detected an issue with our Beijing IV, Beijing V, Shanghai VI datacenter and is currently investigating the matter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC or any other alternate DC. For more information, please refer to the following support article.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root Cause: Upstream provider experienced an congestion.

Latest Update - Fri, 20 Feb 2026 19:01:21 UTC

Update - Fri, 20 Feb 2026 13:55:07 UTC

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

Update - Fri, 20 Feb 2026 15:13:12 UTC

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

Update - Fri, 20 Feb 2026 19:01:21 UTC

Beijing Datacenter Issue - zscaler.net, zscloud.net, zscalerthree.net

Fri, 20 Feb 2026 13:20:30 GMT

Zscaler has detected an issue with its Beijing datacenter and is currently investigating the matter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC or any other alternate DC. For more information, please refer to the following support article.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root cause- The incident occurred due to congestion on a third-party carrier’s international backbone.

Latest Update - Fri, 20 Feb 2026 20:30:07 UTC

Update - Fri, 20 Feb 2026 13:57:39 UTC

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

Update - Fri, 20 Feb 2026 15:12:32 UTC

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

Update - Fri, 20 Feb 2026 20:30:07 UTC

Administration UI Issue - zscalertwo.net

Wed, 18 Feb 2026 09:16:27 GMT

Zscaler has detected an issue with the administration UI on its zscalertwo.net Cloud. To assist with recovery, the Admin UI has been placed into Read-Only Mode. Your organization's policies are currently being enforced.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Latest Update - Wed, 18 Feb 2026 14:56:50 UTC

Update - Wed, 18 Feb 2026 10:42:50 UTC

Update - Wed, 18 Feb 2026 12:01:45 UTC

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

Update - Wed, 18 Feb 2026 13:16:34 UTC

Mitigation efforts are ongoing and are in the final stages. Once mitigation is complete, read-only mode will be removed from the Admin UI.

Update - Wed, 18 Feb 2026 13:53:20 UTC

Mitigation actions have been completed, and read-only mode has been removed. The Admin UI is now fully available.

Update - Wed, 18 Feb 2026 14:56:50 UTC

Device registration issues for Zscaler Client Connector - zscalertwo.net, zscalerthree.net

Tue, 17 Feb 2026 19:16:32 GMT

Zscaler has detected an issue with the Zscaler Client Connector Portal and device registration failure on its zscalertwo.net, zscalerthree.net Cloud.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root cause: The issue was caused by a configuration issue on a limited set of Mobile Admin nodes that temporarily disrupted their connectivity with the Central Authority (CA), resulting in brief Zscaler Client Connector registration failures.

Latest Update - Wed, 18 Feb 2026 00:40:48 UTC

Update - Tue, 17 Feb 2026 19:51:17 UTC

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

Update - Wed, 18 Feb 2026 00:40:48 UTC

Washington DC Issue - zscalertwo.net

Tue, 17 Feb 2026 05:03:51 GMT

Zscaler has detected an issue with our Washington DC datacenter and is currently investigating the matter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC or any other alternate DC. For more information, please refer to the following support article. We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root cause- The issue occurred due to irregular traffic forwarding behavior.

Latest Update - Wed, 18 Feb 2026 07:09:45 UTC

Zscaler has already implemented preliminary mitigation measures to address the issue, and no further issues have been reported. Therefore, we are marking this incident as resolved.

Update - Tue, 17 Feb 2026 06:37:51 UTC

Zscaler team has identified the root cause and is actively prioritizing the incident, exploring mitigation options, and working to restore service for all affected traffic.

Update - Tue, 17 Feb 2026 07:33:33 UTC

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

Update - Wed, 18 Feb 2026 07:09:45 UTC

Zscaler has already implemented preliminary mitigation measures to address the issue, and no further issues have been reported. Therefore, we are marking this incident as resolved.

User Authentication Issues - zscalertwo.net

Mon, 16 Feb 2026 17:11:54 GMT

Zscaler has detected an issue with the user authentication on its zscalertwo.net Cloud. We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root cause: Preliminary findings indicate that a temporary service routing issue delayed the distribution of updated security and access policies. Traffic continued to flow during this period, and policy propagation returned to normal once routing stabilized.

Latest Update - Mon, 16 Feb 2026 22:40:22 UTC

Update - Mon, 16 Feb 2026 18:14:09 UTC

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

Update - Mon, 16 Feb 2026 22:40:22 UTC

Zscaler Client Connector-Based End User Notifications Issue - zscloud.net, zscalerthree.net

Mon, 16 Feb 2026 06:43:24 GMT

Zscaler has detected an issue with Zscaler Client Connector-Based End User Notifications on its zscloud.net, zscalerthree.net Cloud. We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Resolved- Issue was related to node.

Update - Mon, 16 Feb 2026 06:57:02 UTC

Zscaler has implemented mitigation measures to address the issue. This incident is now resolved

Munich I Datacenter Issue - zscaler.net, zscalertwo.net, zscloud.net, zscalerthree.net

Mon, 16 Feb 2026 04:03:34 GMT

Zscaler has detected an issue with its Munich I datacenter and is currently investigating the matter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC or any other alternate DC. For more information, please refer to the following support article.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root Cause- A hardware failure occurred within an upstream transit provider's network.

Update - Mon, 16 Feb 2026 04:03:34 UTC

The incident has been resolved without any intervention from Zscaler and we are investigating the root cause of the issue.

Capetown IV Datacenter Issue - zscaler.net, zscalertwo.net, zscloud.net, zscalerthree.net

Fri, 13 Feb 2026 10:58:39 GMT

Zscaler has detected an issue with its Capetown IV datacenter and is currently investigating the matter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC or any other alternate DC. For more information, please refer to the following support article.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root cause: An upstream provider experienced an issue impacting international connectivity in Europe.

Latest Update - Sat, 14 Feb 2026 12:16:39 UTC

Based on continuous monitoring and health checks, the issue is no longer present; therefore, we are marking this incident as resolved.

Update - Fri, 13 Feb 2026 11:14:22 UTC

Our preliminary analysis points toward an issue external to Zscaler’s infrastructure. We have engaged the relevant third-party providers and are simultaneously evaluating rerouting options to circumvent the impacted network path and minimize customer impact.

Update - Fri, 13 Feb 2026 12:23:34 UTC

Our upstream provider is experiencing an issue impacting international connectivity in Europe. This is not related to the CPT4 data center or our circuits. The provider has rerouted traffic via alternate paths; however, they are currently seeing congestion, and there is no ETA for full restoration at this time. We are actively implementing additional mitigations to restore connectivity and will provide updates as more information becomes available.

Update - Fri, 13 Feb 2026 13:39:06 UTC

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

Update - Sat, 14 Feb 2026 04:32:49 UTC

We continue to monitor the situation to ensure stability. While mitigation is in progress, updates will be shared as they become available.

Update - Sat, 14 Feb 2026 12:16:39 UTC

Based on continuous monitoring and health checks, the issue is no longer present; therefore, we are marking this incident as resolved.

Update - Sat, 14 Feb 2026 12:16:57 UTC

This incident has been resolved. Please contact Zscaler Support if you have additional questions.

User Authentication Issue on Mumbai VI, Chennai II, and Hyderabad I Datacenters. - zscaler.net

Thu, 12 Feb 2026 08:13:26 GMT

Zscaler has detected an issue with its Mumbai VI, Chennai II, and Hyderabad I datacenter and is currently investigating the matter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC or any other alternate DC. For more information, please refer to the following support article.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root Cause: A subset of PSEs experienced connectivity issues reaching the Cache CA.

Latest Update - Thu, 12 Feb 2026 12:31:54 UTC

Update - Thu, 12 Feb 2026 11:17:19 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, 12 Feb 2026 12:31:54 UTC

Sandbox and Site Review Issue - zscaler.net, zscalerone.net, zscalertwo.net, zscloud.net, zscalerthree.net

Thu, 12 Feb 2026 07:56:36 GMT

Zscaler has detected an issue with its zscaler.net, zscalerone.net, zscalertwo.net, zscloud.net, zscalerthree.net Cloud.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root cause- Issue occurred due to a recent upgrade that caused a configuration issue.

Latest Update - Thu, 12 Feb 2026 12:02:05 UTC

Based on our continuous monitoring and health checks, the issue is no longer present and services are working as expected. This incident is now resolved.

Update - Thu, 12 Feb 2026 08:26:24 UTC

Zscaler is actively working on isolating and mitigating the issue and further updates will be shared at the earliest.

Update - Thu, 12 Feb 2026 10:02:37 UTC

Zscaler has implemented the necessary measures, and the issue is now mitigated. Services are operating normally and will continue to be monitor to ensure stability.

Update - Thu, 12 Feb 2026 12:02:05 UTC

Based on our continuous monitoring and health checks, the issue is no longer present and services are working as expected. This incident is now resolved.

Update - Thu, 12 Feb 2026 12:05:56 UTC

This incident has been resolved. Please contact Zscaler Support if you have additional questions.

Reporting and Logging Issue - zscloud.net

Thu, 12 Feb 2026 06:38:43 GMT

Zscaler has detected an issue with Reporting and Logging on its zscloud.net Cloud. We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root cause- The issue occurred due to a configuration issue, causing delays in log processing and log availability.

Latest Update - Mon, 16 Feb 2026 08:35:39 UTC

Zscaler deployed a permanent fix during the weekend maintenance window to address the issue. Based on continuous monitoring and health checks, the issue is no longer present. We are marking this incident as resolved.

Update - Thu, 12 Feb 2026 07:12:45 UTC

The Zscaler team has identified the root cause and is prioritizing the incident, exploring various mitigation options, and working to restore services.

Update - Thu, 12 Feb 2026 08:47:18 UTC

The earlier issue has recovered, and services are currently operating as expected. Our teams are actively monitoring the environment to ensure it remains stable and to quickly respond if any issues recur. In parallel, Zscaler is working on a permanent fix to prevent this from happening again, which is planned to be applied during the upcoming weekly maintenance window. The incident is currently mitigated and under monitoring.

Update - Thu, 12 Feb 2026 10:20:52 UTC

The issue has resurfaced, and we are currently working to isolate and resolve it.

Update - Thu, 12 Feb 2026 12:29:06 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, 16 Feb 2026 08:35:39 UTC

Update - Mon, 16 Feb 2026 08:40:02 UTC

This incident has been resolved. Please contact Zscaler Support if you have additional questions.

Reporting and Logging Issue - zscaler.net, zscalertwo.net, zscloud.net, zscalerthree.net

Thu, 12 Feb 2026 02:42:31 GMT

Zscaler has detected an issue with Reporting and Logging on its zscaler.net, zscalertwo.net, zscloud.net, zscalerthree.net Cloud.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root Cause: Network routing packet loss on certain paths caused web log performance degradation for some traffic patterns.

Latest Update - Thu, 12 Feb 2026 04:41:50 UTC

Zscaler is observing service recovery following a network routing issue that impacted performance for some traffic patterns. The underlying network path issue has been addressed, and validation testing indicates no ongoing packet loss on the previously affected routes. We are now observing that the previously reported web performance degradation has been resolved and services have returned to normal. Our teams implemented mitigations and verified recovery through monitoring and post-change validation.

Update - Thu, 12 Feb 2026 03:35:48 UTC

We have identified packet loss affecting specific network paths and are actively implementing mitigations, including routing changes to steer traffic around the affected segment.

Update - Thu, 12 Feb 2026 04:41:50 UTC

Website Accessibility and Email Delivery Degradation in the US and EMEA Data Centers for a Public IP Subnet - zscaler.net, zscalertwo.net, zscloud.net, zscalerthree.net

Wed, 11 Feb 2026 23:54:47 GMT

Zscaler is aware of and currently investigating website accessibility and email delivery degradation associated with an external reputation-based filtering service affecting a public IP subnet range. The impacted IP subnet has been flagged by a third-party reputation provider, which is preventing access to certain websites and causing email delivery failures to some destinations. Zscaler is actively engaged with the third-party reputation provider to expedite removal of the impacted subnet. At this time, there is no estimated time to resolution; however, mitigation actions are being evaluated to reduce customer impact.

Zscaler continues to closely monitor the situation and will provide updates as more information becomes available. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root cause- The incident occurred due to a configuration change to a public IP subnet that triggered an automated third-party blocklist entry, resulting in outbound traffic and email delivery failures.

Latest Update - Sun, 15 Feb 2026 00:28:06 UTC

Following the actions previously taken, 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, 12 Feb 2026 18:05:05 UTC

Zscaler has coordinated with the external reputation provider, and the reputation-related restriction affecting the impacted public IP range has now been removed. Remediation actions associated with this condition have been completed. Customers who previously experienced impact are requested to validate that normal website access and email delivery have been restored. Zscaler will continue to monitor the environment to ensure sustained service stability.

Update - Sun, 15 Feb 2026 00:28:06 UTC

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

Outbound DLP Email Delivery Failures via Zscaler SMTP IPs - zscaler.net, zscalertwo.net, zscloud.net, zscalerthree.net

Sun, 08 Feb 2026 21:15:24 GMT

Zscaler is currently investigating an issue where certain outbound email notifications are failing due to Zscaler SMTP IP addresses being flagged by an external third-party reputation service. This is resulting in email delivery disruptions for some customers. We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root cause- The incident occurred due to a configuration gap in reverse DNS and SMTP identity alignment, which triggered delivery rejections by recipient systems enforcing third-party reputation policies.

Latest Update - Sun, 15 Feb 2026 18:09:18 UTC

All planned mitigation actions have been completed, including adding the Secure Mail entries for ZSN, ZSC, ZS2, and ZS3. We are no longer observing any abnormalities, and the incident is now considered resolved.

Update - Sun, 08 Feb 2026 21:52:11 UTC

Update - Sun, 08 Feb 2026 23:04:13 UTC

We are continuing to investigate an issue impacting outbound email delivery for some customers. Our teams are actively working to determine the cause and restore normal service. Further updates will be provided as more information becomes available.

Update - Mon, 09 Feb 2026 00:22:21 UTC

We are continuing to investigate an issue impacting outbound email delivery. A potential fix has shown positive results in internal testing; however, validation is still ongoing and will require additional time. Zscaler teams remain fully engaged. Further updates will be provided as progress is made.

Update - Mon, 09 Feb 2026 02:25:30 UTC

Zscaler has engaged the email service provider’s support team, and the teams have confirmed that automated anti-spam controls are enforcing a third-party blocklist, which is causing some emails from affected Zscaler SMTP egress IPs to be rejected. Zscaler is working in parallel with the provider and the blocklist operator to expedite delisting of the impacted IPs; escalations are in progress and all impacted IPs have been submitted for review while remediation efforts continue to restore full service stability.

Update - Mon, 09 Feb 2026 04:18:41 UTC

Zscaler has identified a mitigation strategy to reduce impact from this issue and is actively implementing it to restore full service stability as quickly as possible.

Update - Mon, 09 Feb 2026 04:47:18 UTC

Zscaler teams have taken steps to mitigate the impact of this issue while we continue to work with the third party to fully resolve it and restore service stability.

Update - Mon, 09 Feb 2026 05:32:52 UTC

We have implemented a temporary mitigation to address the email delivery failures by redirecting traffic to alternate Email DLP clusters that are not impacted by the third-party blocklist. As a result, affected customers should now see email delivery restored while we continue working with the third party on permanent remediation (including delisting and policy override options). Customers using Google Workspace (G Suite) may need to whitelist the updated egress IP ranges to ensure continued email delivery. Customers are advised to refer to the Service Status section in their Zscaler customer support portal (CSP) for more details.

Update - Mon, 09 Feb 2026 16:02:12 UTC

The actions implemented earlier have provided a temporary mitigation and continue to be effective. Zscaler is working with the third-party provider on a permanent remediation, and progress is being made. We will share a further update as more details become available.

Update - Mon, 09 Feb 2026 21:40:45 UTC

Zscaler continues to work with the third-party provider on a permanent remediation. Portions of the fix have been completed and are in place, and we are actively working on the remaining items. We will share further updates as more details become available.

Update - Tue, 10 Feb 2026 06:39:11 UTC

Zscaler has finalized the necessary steps to achieve full resolution for the incident. As part of the standard weekend maintenance window across all cloud environments, we will apply a permanent fix to remediate the recently observed issue. The temporary mitigation currently in effect will remain active until the fix is fully implemented.

Update - Wed, 11 Feb 2026 09:56:20 UTC

Previously, Zscaler implemented a temporary mitigation to address email delivery failures by updating DNS to redirect Email DLP traffic to alternate clusters that were not impacted by a third-party blocklist. Zscaler has now finalized the steps required for full resolution and, as part of the standard weekend maintenance window across all cloud environments, will apply a permanent fix to remediate the recently observed issue. Customers should review and complete any applicable action items outlined in the advisory; the implementation schedule is also available in the advisory link.

Update - Sun, 15 Feb 2026 18:09:18 UTC

Performance Degradation in Mumbai VI (BOM6) Data Center - zscaler.net, zscalerone.net, zscalertwo.net, zscloud.net, zscalerthree.net

Sun, 08 Feb 2026 19:24:13 GMT

Zscaler investigated reports of intermittent performance degradation impacting a subset of customers whose traffic was primarily traversing the Mumbai VI (BOM6) data center. Affected customers may have experienced a significant reduction in internet throughput, resulting in slow application performance and degraded browsing experience. Zscaler has identified the underlying issue and implemented targeted mitigation actions. The environment is being closely monitored to ensure stability during peak and business-hour traffic conditions, after which the mitigation will be extended as appropriate.

Customers who continue to experience traffic impact may consider temporarily steering traffic to a secondary or alternate Zscaler data center. For more information, please refer to the following support article.

For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and updates will be posted there as they become available.

Root cause- Incident caused by a latent software defect.

Latest Update - Thu, 12 Mar 2026 08:10:19 UTC

A fix for the defect causing performance issues for a subset of customers has been deployed on the remaining zscalerone.net, zscalertwo.net, and zscloud.net clouds. As a result, we are marking this incident as resolved.

Update - Wed, 11 Feb 2026 13:47:44 UTC

Zscaler continues to work on a permanent fix. In the meantime, we’ve implemented mitigations in the Mumbai VI (BOM6) data center and continue to monitor.

Update - Tue, 24 Feb 2026 19:04:36 UTC

Based on ongoing telemetry analysis and continuous service monitoring, we are observing stable system behavior with no further customer impact and no additional customer reports. As part of our continued focus on service resiliency and long-term stability, additional enhancements are in progress and will be deployed during an upcoming cloud maintenance window to further strengthen overall service stability and operational safeguards. We will continue to monitor closely and provide updates as appropriate.

Update - Thu, 26 Feb 2026 15:11:56 UTC

A fix for the defect causing performance issues for a subset of customers has been deployed on zscaler.net and zscalerthree.net clouds, remaining clouds will receive the fix in next two weeks as part of the scheduled update cycle.

Update - Thu, 12 Mar 2026 08:10:19 UTC

Device registration and portal failure for Zscaler Client Connector - zscaler.net, zscalertwo.net

Fri, 06 Feb 2026 13:07:43 GMT

We are investigating device registration failures issue with our zscaler.net, zscalertwo.net Clouds. For additional information please reach out to Zscaler Support referencing this incident, status changes will be updated here as they become available.

Root cause- The issue occurred because a third-party cross-connect provider experienced a fiber outage.

Update - Fri, 06 Feb 2026 13:07:43 UTC

The incident has been resolved. Our systems remain fully operational, and we will continue to monitor the situation closely to ensure ongoing stability.

SCIM Auto-provisioning issue - zscalerone.net

Fri, 06 Feb 2026 13:02:34 GMT

Zscaler has detected an issue with the SCIM-based provisioning for users on its zscalerone.net Cloud.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Update - Fri, 06 Feb 2026 13:02:34 UTC

This incident has been resolved. Please contact Zscaler Support if you have additional questions.

San Francisco IV Datacenter Issue - zscalertwo.net, zscalerthree.net

Fri, 06 Feb 2026 12:44:46 GMT

Zscaler has detected an issue with its San Francisco IV datacenter and is currently investigating the matter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC or any other alternate DC. For more information, please refer to the following support article.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Update - Fri, 06 Feb 2026 12:44:46 UTC

The incident has been resolved. Our systems remain fully operational, and we will continue to monitor the situation closely to ensure ongoing stability.

Dusseldorf I Datacenter Issue - zscalertwo.net

Thu, 05 Feb 2026 02:46:57 GMT

Zscaler has detected an issue with our Dusseldorf I datacenter and is currently investigating the matter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC or any other alternate DC. For more information, please refer to the following support article. We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root Cause- The issue occurred during a planned change to update services for cloud optimization.

Impacted Service - Traffic forwarding | IPSEC and ZCC Tunnel 2.0 | zscalertwo.net

Update - Thu, 05 Feb 2026 03:25:49 UTC

Zscaler has successfully implemented a mitigation for the issue and the incident has been resolved. Our systems remain fully operational, and we will continue to monitor the situation closely to ensure ongoing stability.

Issues accessing external resources including Microsoft applications through the Hong Kong III data center - zscaler.net, zscalertwo.net, zscloud.net, zscalerthree.net

Thu, 05 Feb 2026 01:55:56 GMT

Zscaler has detected an issue with its Hong Kong III datacenter and is currently investigating the matter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC or any other alternate DC. For more information, please refer to the following support article.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root Cause: The preliminary root cause points to an issue within a third‑party CDN provider’s infrastructure impacting affected destinations.

Latest Update - Fri, 06 Feb 2026 03:22:36 UTC

The issue has been resolved, and service has remained stable since the correction. While no changes were required within the Zscaler service, we are working with the third-party CDN provider to identify the root cause and prevent recurrence.

Update - Thu, 05 Feb 2026 03:35:40 UTC

Initial investigation suggests the issue is impacting destinations fronted by a third party CDN provider. We are actively engaging with the provider through available channels to support further investigation and resolution.

Update - Thu, 05 Feb 2026 04:25:44 UTC

In parallel with our ongoing investigation, we recommend impacted customers also open a case with the relevant CDN provider for the impacted domains and reference observed connectivity failures from the HKG3 DC. We are actively attempting to engage the third‑party provider through available channels and will provide further updates as more information or mitigations become available.

Update - Thu, 05 Feb 2026 05:04:17 UTC

We are actively coordinating with the CDN provider. At this time, there is no issue identified within Zscaler infrastructure, and the impact appears to be isolated to the CDN provider. Impacted customers are advised to open a case with their CDN provider for the affected domains and reference the observed connectivity failures from the HKG3 data center.

Update - Thu, 05 Feb 2026 06:50:08 UTC

We are coordinating with the CDN provider (Akamai). At this time, no issues have been identified within Zscaler infrastructure, and the impact appears isolated to the CDN provider. Impacted customers are advised to open a support case with their CDN provider for the affected domains and reference the observed connectivity failures originating from the HKG3 data center. No ETA is available at this time. Status updates will be shared when available.

Update - Thu, 05 Feb 2026 08:05:06 UTC

The Zscaler team was working on a mitigation. While it was being implemented, we started seeing improvements in the services, even though no changes had been made on the Zscaler side. We will continue to monitor closely and work with the CDN provider to confirm the root cause and next steps.

Update - Fri, 06 Feb 2026 03:22:36 UTC

New Cloud Connector and Branch Connector Deployment Issue - zscaler.net, zscalertwo.net, zscloud.net, zscalerthree.net

Tue, 03 Feb 2026 17:35:37 GMT

Zscaler is investigating an issue impacting customers performing new Cloud Connector and Branch Connector deployment operations across zscaler.net, zscalertwo.net, zscloud.net, zscalerthree.net Cloud. Existing Cloud Connector and Branch Connector instances remain unaffected. Customers attempting to deploy new Cloud Connector or Branch Connector instances may experience deployment failures. Newly provisioned connectors are unable to retrieve required software packages, which can prevent successful startup.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Affected Services: Zscaler Branch Connector and Cloud Connector

Root cause: The incident resulted from a compatibility issue during a service update that affected new connector deployments. Full details will be provided in the final Root Cause Analysis report.

Latest Update - Wed, 04 Feb 2026 16:46:30 UTC

Following the mitigation, Zscaler has received positive confirmation from impacted customers, and ongoing monitoring indicates stable service behavior. The incident has now been resolved.

Update - Tue, 03 Feb 2026 17:55:43 UTC

Update - Tue, 03 Feb 2026 18:22:05 UTC

Zscaler has identified the cause of the issue and is implementing the necessary fix to restore normal service. Further updates will be provided as progress is made.

Update - Tue, 03 Feb 2026 19:24:24 UTC

Zscaler continues to work on an issue impacting the deployment of new Cloud Connector and Branch Connector instances. A mitigation has been deployed, and validation is currently in progress across regions. Initial validation is successful in some environments; however, additional testing is ongoing to ensure consistent behavior across all deployments. Customers attempting to deploy new Cloud Connector or Branch Connector instances may continue to experience deployment failures during this period. Existing, already-running connector instances remain unaffected. Further updates will be provided as validation progresses.

Update - Tue, 03 Feb 2026 21:17:33 UTC

Zscaler continues to validate a fix for an issue impacting the deployment of new Cloud Connector and Branch Connector instances. Progress has been observed in multiple environments, and additional validation is ongoing. Existing connector instances remain unaffected.

Update - Tue, 03 Feb 2026 21:36:02 UTC

Zscaler has resolved the issue impacting the deployment of new Cloud Connector and Branch Connector instances. The fix has been validated across environments, and systems are now operating as expected. Zscaler is continuing to monitor the service to ensure ongoing stability.

Update - Wed, 04 Feb 2026 16:46:30 UTC

Following the mitigation, Zscaler has received positive confirmation from impacted customers, and ongoing monitoring indicates stable service behavior. The incident has now been resolved.

Shanghai IV and Shanghai VI Datacenter Issue - zscaler.net, zscalertwo.net, zscloud.net, zscalerthree.net, private.zscaler.com, zpatwo.net

Tue, 03 Feb 2026 09:06:53 GMT

Zscaler has detected an issue with its Shanghai IV, Shanghai VI datacenter and is currently investigating the matter. Customers may experience intermittent disconnects, authentication failures, degraded performance, or increased latency when accessing international destinations. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC. For more information, please refer to the following support article. We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root cause- Issue occurred due to congestion along the network path related to a subsea cable fault.

Latest Update - Mon, 09 Feb 2026 13:38:33 UTC

Zscaler has received confirmation from our partner that the impacted submarine cable has been repaired. We are now seeing improved connectivity across all data centers, with reduced packet loss and positive customer feedback. This incident is now marked as Resolved.

Update - Tue, 03 Feb 2026 09:16:38 UTC

Zscaler has isolated the ongoing issue to submarine cable repairs, which are outside the control of both Zscaler and our partner. As a result, an estimated time to restoration (ETR) is not available at this time. Further updates will be shared as they become available.

Update - Tue, 03 Feb 2026 10:56:37 UTC

Zscaler has isolated the issue to congestion and ongoing submarine cable repairs impacting the forward path from customers to the Zscaler data centers. Customers can work with their ISP/carrier to reroute traffic and bypass the impacted path where possible while repairs are in progress.

Update - Thu, 05 Feb 2026 16:25:15 UTC

Zscaler continues to work with our carrier partner. At this time, there is no new update to share regarding the congestion/submarine cable repairs, and we will continue to follow up with the carrier. Where possible, customers may also work with their ISP/carrier to explore rerouting options to bypass the impacted path and associated congestion while repairs are in progress.

Update - Fri, 06 Feb 2026 08:07:33 UTC

Zscaler has received an update from the partner that the submarine cable has been repaired, and we’re seeing improved connectivity across all data centers with reduced packet loss and positive customer feedback. We will continue to monitor the situation to ensure stability.

Update - Mon, 09 Feb 2026 13:38:33 UTC

Shanghai, Shanghai II and Beijing III Datacenter Issue - zscaler.net, zscalertwo.net, zscloud.net, zscalerthree.net, private.zscaler.com, zpatwo.net

Mon, 02 Feb 2026 03:00:09 GMT

Zscaler has detected an issue with its Shanghai, Shanghai II, and Beijing III datacenters and is currently investigating the matter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC or any other alternate DC. For more information, please refer to the following support article.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root Cause: Submarine Cable Fault / Congestion in the network path | Traffic Forwarding | ZSC, ZS2, ZSN, ZS3, ZPA clouds

Latest Update - Tue, 10 Feb 2026 14:36:47 UTC

Zscaler has received confirmation that the submarine cable issue has been remediated and has verified improvements in the affected network path where congestion was previously observed. Following a monitoring period, Zscaler confirms the incident is resolved.

Update - Mon, 02 Feb 2026 03:40:08 UTC

Zscaler has identified issue with its carrier partner and working to the resolve the issue. Updated will be shared as they become available.

Update - Mon, 02 Feb 2026 07:28:48 UTC

Zscaler continues to work with its carrier partner to expedite resolution, and additional updates will be provided as they become available.

Update - Mon, 02 Feb 2026 12:15:44 UTC

Zscaler continues to work with its carrier partner to expedite resolution and will share further updates as they become available.

Update - Mon, 02 Feb 2026 16:27:35 UTC

Zscaler has received confirmation from its carrier partner that the issue is due to congestion along the network path related to subsea cable impacts. Zscaler continues to work with the partner to investigate and implement any potential mitigations.

Update - Tue, 03 Feb 2026 04:17:01 UTC

Zscaler has not received new updates from its carrier partner. The ongoing submarine cable repairs are outside of Zscaler’s and the partner’s control; therefore, no estimated time to restoration (ETR) is available at this time. Further updates will be shared as they become available.

Update - Tue, 03 Feb 2026 07:44:57 UTC

Zscaler has still not received any new updates from its carrier partner. The ongoing submarine cable repairs remain outside of Zscaler’s and the partner’s control; therefore, an estimated time to restoration (ETR) is not available at this time. As the investigation continues, we have expanded the list of impacted data centers and extended the impact details based on the latest findings. We will share further updates as soon as new information becomes available.

Update - Thu, 05 Feb 2026 16:26:00 UTC

Update - Fri, 06 Feb 2026 12:12:06 UTC

The Zscaler teams have received an update that the submarine cable fault has been fixed, and Zscaler has verified improvement along the affected network paths. To validate the effectiveness of the fix, Zscaler will continue to monitor the situation closely to ensure ongoing stability and to promptly address any recurrence or new issues that may arise. Customers who are able to do so are requested to retest and provide feedback.

Update - Tue, 10 Feb 2026 14:36:47 UTC

ZPA Browser-Based and Privileged Remote Access Application Accessibility Issue - private.zscaler.com

Sun, 01 Feb 2026 17:52:27 GMT

Zscaler detected an issue impacting the private.zscaler.com Cloud. A subset of customers in the impacted environments might have observed the following:

Loss of access to browser based applications
Loss of access to Privileged Remote Access applications

ZCC enrollment and ZPA logins remain fully functional, and all other production services continue to operate normally. We have identified the root cause and remediated to bring access back to all configured browser based and Privileged Remote Access applications.

For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root cause: During a planned maintenance window, a service configuration change intended to enhance logging capabilities resulted in a temporary disruption to ZPA Browser Access and Privileged Remote Access.

Update - Sun, 01 Feb 2026 20:46:34 UTC

Atlanta II Datacenter Issue - zscaler.net, zscalertwo.net, zscloud.net, zscalerthree.net, private.zscaler.com

Sat, 31 Jan 2026 03:06:24 GMT

Zscaler is currently investigating reports of an issue with its Atlanta II datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC or any other alternate DC. For more information, please refer to the following support article.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and updates will be posted there as they become available.

Incident Status- Resolved

Root Cause: Preliminary findings indicate an interconnect fault that caused packet loss, resulting in intermittent accessibility issues.

Latest Update - Sat, 31 Jan 2026 05:32:16 UTC

Following the actions previously taken by Zscaler, the incident has been resolved.

Update - Sat, 31 Jan 2026 04:26:01 UTC

Zscaler has successfully implemented a mitigation for the issue, completed at 03:49 UTC, 31 Jan 2026. Initial test results suggest that the mitigation effectively resolves the issue. We are currently conducting further validation through internal testing and gathering customer feedback to ensure that the problem is fully addressed and the service is functioning as intended.

Update - Sat, 31 Jan 2026 05:32:16 UTC

Following the actions previously taken by Zscaler, the incident has been resolved.

Rio de Janeiro I Datacenter Issue - zscaler.net, zscalertwo.net, zscloud.net, zscalerthree.net

Sat, 31 Jan 2026 02:19:09 GMT

Zscaler has detected an issue with its Rio de Janeiro I datacenter and is currently investigating the matter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC or any other alternate DC. For more information, please refer to the following support article.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Incident Status- Resolved

Root Cause: The incident was caused by an issue within a carrier partner’s network infrastructure.

Latest Update - Sat, 31 Jan 2026 03:23:10 UTC

This incident has been resolved. Please contact Zscaler Support if you have additional questions.

Update - Sat, 31 Jan 2026 02:53:55 UTC

Zscaler has collaborated with its carrier partner to resolve the issue and is now monitoring the situation to ensure ongoing stability.

Update - Sat, 31 Jan 2026 03:23:10 UTC

This incident has been resolved.

Authentication Issue on Zscaler Client Connector for Android - zscaler.net, zscalertwo.net, zscloud.net, zscalerthree.net

Thu, 29 Jan 2026 23:13:38 GMT

Zscaler is investigating reports of an authentication issue affecting a subset of Android users who authenticate using Microsoft Entra ID. Impacted users may encounter an error stating “SSL Error occurred. The server certificate is not trusted” when attempting to sign in to the Zscaler Client Connector.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root Cause: The root cause was determined to be delayed security updates on affected Android and Chromebook devices, which prevented them from recognizing the latest intermediate certificate.

Latest Update - Wed, 04 Feb 2026 04:39:57 UTC

Based on feedback from several customers and the absence of any new reports, we believe the security update is now in effect and are considering the issue to be resolved.

Update - Fri, 30 Jan 2026 01:53:07 UTC

Zscaler is actively investigating this issue and has prioritized efforts to isolate the cause. Based on initial analysis, the behavior appears to be related to a recent intermediate certificate change associated with Microsoft authentication services. We appreciate your patience as we continue our investigation and work toward a resolution. Additional updates will be shared as more information becomes available.

Update - Fri, 30 Jan 2026 03:06:52 UTC

Zscaler has implemented a validated workaround to mitigate the issue. The permanent resolution will occur automatically when the updated CA is distributed through Microsoft Security Updates.

Update - Wed, 04 Feb 2026 04:39:57 UTC

Based on feedback from several customers and the absence of any new reports, we believe the security update is now in effect and are considering the issue to be resolved.

Mumbai VI Datacenter Issue - zscaler.net, zscalertwo.net, zscloud.net, zscalerthree.net

Thu, 29 Jan 2026 06:36:35 GMT

Zscaler has detected an issue with its Mumbai VI datacenter and is currently investigating reports of slowness. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC or any other alternate DC. For more information, please refer to the following support article.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Latest Update - Wed, 04 Feb 2026 16:31:48 UTC

Zscaler has completed additional optimization measures, providing further mitigation beyond the actions taken last week. Zscaler teams have continued to monitor the environment and validate service stability. This issue is now resolved.

Update - Thu, 29 Jan 2026 18:05:07 UTC

Zscaler has identified the issue and has implemented necessary actions to improve service availability and stabilize performance. Zscaler teams continue to actively monitor the environment, evaluate additional optimization measures, and seek customer feedback to confirm service stability. Further updates will be provided as monitoring continues.

Update - Fri, 30 Jan 2026 14:09:46 UTC

Following the mitigation actions taken to improve service availability and stabilize performance, Zscaler will continue to monitor the situation closely throughout the weekend and into early next week’s business hours to ensure ongoing stability and to promptly address any potential recurrence or new issues.

Update - Mon, 02 Feb 2026 14:22:45 UTC

Zscaler confirmed that the previously implemented mitigation actions to improve service availability and stability remain effective. We continue to monitor the environment while the Zscaler teams implements additional measures to help prevent recurrence.

Update - Wed, 04 Feb 2026 16:31:48 UTC

User Authentication Issue on Capetown IV and Johannesburg III Datacenters - zscaler.net, zscalerone.net, zscalertwo.net, zscloud.net, zscalerthree.net

Wed, 28 Jan 2026 17:39:48 GMT

Zscaler has detected an issue with its Capetown IV and Johannesburg III datacenters and is currently investigating the matter. For more information, please refer to the following support article.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Incident Status- Resolved

Root Cause: The root cause of the issue is attributed to a network event in the international backbone connectivity.

Latest Update - Thu, 29 Jan 2026 08:08:50 UTC

Update - Wed, 28 Jan 2026 20:20:27 UTC

Update - Wed, 28 Jan 2026 21:25:36 UTC

Zscaler identified a connectivity issue with an upstream internet service provider affecting the Cape Town (CPT4) and Johannesburg (JNB3) data centers. Some customers may have experienced intermittent authentication issues or degraded connectivity when accessing international destinations. Zscaler engaged the provider immediately and implemented protective measures while the issue was addressed. Network conditions have improved, services are recovering, and monitoring remains in place to ensure stability.

Update - Wed, 28 Jan 2026 22:08:45 UTC

Further monitoring and telemetry confirm that network stability has been restored and all services are operating normally. Zscaler will continue to monitor to ensure sustained stability.

Update - Thu, 29 Jan 2026 08:08:50 UTC

Following the actions previously taken by the provider, the incident has been resolved.

User Authentication Issue on Kingdom of Saudi Arabia I Datacenter - zscaler.net, zscalertwo.net, zscloud.net, zscalerthree.net

Wed, 28 Jan 2026 15:42:43 GMT

Zscaler has detected an issue with its Kingdom of Saudi Arabia I datacenter and is currently investigating the matter. For more information, please refer to the following support article.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Incident Status- Resolved

Latest Update - Wed, 28 Jan 2026 17:40:07 UTC

Update - Wed, 28 Jan 2026 16:29:59 UTC

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

Update - Wed, 28 Jan 2026 17:40:07 UTC

Upstream Network Routing Issue Affecting Connectivity in Australia - zscaler.net, zscalertwo.net, zscloud.net, zscalerthree.net

Tue, 27 Jan 2026 21:14:44 GMT

Zscaler is investigating reports of connectivity issues impacting customers connecting through the Sydney III (SYD3) and Canberra I (CBR1) data centers. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC or any other alternate DC. For more information, please refer to the following support article.

Our teams are actively engaged in the investigation and working to identify the cause. Additional updates will be shared as more information becomes available. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Root cause: A routing anomaly within a third‑party service provider’s network disrupted connectivity to the affected data centers.

Incident Status: Resolved

Latest Update - Wed, 28 Jan 2026 07:07:19 UTC

Following continuous monitoring, Zscaler confirms the connectivity issue impacting the data centers is no longer present. Service telemetry remains stable, and services are operating as expected. Accordingly, we are marking this incident as resolved.

Update - Tue, 27 Jan 2026 22:04:09 UTC

Zscaler has determined that the previously reported connectivity issues affecting access to the Sydney III (SYD3) and Canberra I (CBR1) data centers were caused by a routing issue within a third-party service provider’s network. The third-party provider has resolved the routing issue, and normal network paths and service performance have been restored. Zscaler is monitoring service telemetry to detect and respond to any anomalies.

Update - Wed, 28 Jan 2026 00:46:47 UTC

Zscaler received additional reports that some customers connecting through the Melbourne II (MEL2) data center may have experienced connectivity issues related to a third-party ISP routing issue. Zscaler confirmed that data center health and internal services were operating normally and continues to monitor service telemetry for any anomalies.

Update - Wed, 28 Jan 2026 07:07:19 UTC

Audit Log Access Issue in Zscaler Client Connector Portal - zscaler.net, zscalerone.net, zscalertwo.net, zscloud.net, zscalerthree.net

Sat, 24 Jan 2026 13:30:34 GMT

We are investigating an issue with audit logs on the Mobile Admin portal on all the ZIA Clouds.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and additional details will be posted there as they become available.

Incident Status- Resolved

Update - Sat, 24 Jan 2026 13:58:56 UTC

Zscaler identified and resolved an issue affecting the availability of audit logs within the Zscaler Client Connector Portal across ZIA clouds. During the incident, customers may have experienced errors when attempting to access audit logs. The service has been fully restored, and audit log access is now operating normally.

Sydney III Datacenter Issue - zscaler.net, zscalertwo.net, zscloud.net, zscalerthree.net, private.zscaler.com

Fri, 23 Jan 2026 03:30:59 GMT

Zscaler is currently investigating reports of an issue with its Sydney III datacenter. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC or any other alternate DC. For more information, please refer to the following support article.

We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP). Status changes and updates will be posted there as they become available.

Incident Status- Resolved

Root Cause: The issue was identified to be with an external service provider. The issue was automatically resolved without Zscaler's intervention.

Latest Update - Tue, 27 Jan 2026 04:09:27 UTC

Zscaler monitored the situation and observed recovery, with customers reporting normal performance and no further packet loss on the affected paths. No changes were made on the Zscaler side; the issue resolved without any intervention from Zscaler, indicating remediation occurred within the external provider network. We request customers to raise a ticket with their service providers for more details on the cause of the issue.

Update - Fri, 23 Jan 2026 04:07:19 UTC

We are still investigating the issue and we will share further updates as available.

Update - Fri, 23 Jan 2026 05:28:41 UTC

After analyzing bidirectional MTRs from affected paths, we identified a consistent packet loss closer to customers’ networks, common across all impacted routes. Based on these findings, we concluded that the issue is external to Zscaler, and we recommend customers open tickets with their service providers to address the path issue between their network and Zscaler. For detailed updates, please check the Service Status section in your Zscaler customer support portal (CSP).

Update - Tue, 27 Jan 2026 04:09:27 UTC

Capetown IV Datacenter Issue - zscaler.net, zscalertwo.net, zscloud.net, zscalerthree.net

Thu, 22 Jan 2026 21:34:13 GMT

Root Cause- Issue was caused by network degradation between Cape Town IV data center and a transit provider.

Incident Status- Resolved

Latest Update - Fri, 23 Jan 2026 08:23:43 UTC

Following continuous monitoring and validation of service stability, all services are operating as expected, and we are closing this incident.

Update - Thu, 22 Jan 2026 22:53:55 UTC

Zscaler has identified the issue and determined it was caused by network path degradation. Our network partner has been engaged, and Zscaler has proactively rerouted affected connections to maintain service availability. The environment continues to be closely monitored to ensure a stable and consistent customer experience.

Update - Fri, 23 Jan 2026 08:23:43 UTC

Following continuous monitoring and validation of service stability, all services are operating as expected, and we are closing this incident.

Update - Fri, 23 Jan 2026 08:26:11 UTC

This incident has been resolved. Please contact Zscaler Support if you have additional questions.