Update - Thu, 19 Nov 2026 15:34:36 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, 19 Nov 2026 16:12:46 UTC
Following the actions previously taken by Zscaler, the incident has been resolved. Our systems remain fully operational, and we will continue to monitor the situation closely to ensure ongoing stability.
Update - Thu, 19 Nov 2026 09:45:39 UTC
Issue was reported for zscaler.net in error; impact is observed on zscloud only. zscaler.net will be removed from this Trust post.
Update - Thu, 19 Nov 2026 12:16:27 UTC
The Zscaler teams have successfully mitigated the issue, supported by positive feedback from customers. To validate the effectiveness of the resolution, a thorough health check was conducted. 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 - Thu, 19 Nov 2026 02:26:30 UTC
Following the actions previously taken by Zscaler, the incident has been resolved. Our systems remain fully operational, and we will continue to monitor the situation closely to ensure ongoing stability.
Update - Thu, 19 Nov 2026 03:00:06 UTC
Zscaler has applied mitigation and confirmed recovery across all affected clouds except zscalertwo.net, which is continuing to recover gradually. Zscaler continues to monitor progress and will provide further updates once full resolution has been achieved.
Update - Thu, 19 Nov 2026 04:28:01 UTC
Following the actions previously taken by Zscaler, the incident has been resolved.
Update - Wed, 18 Nov 2026 23:10:52 UTC
Zscaler has identified the issue that prevents posture control results and third-party app information from appearing in the AppTotal portal for certain SaaS applications configured for SaaS Security Posture Management (SSPM). Our teams are working on a fix. We will schedule the fix for deployment after testing confirms it addresses the visibility issue and our teams complete their release review. We will post the next update here as more information becomes available.
Update - Thu, 19 Nov 2026 14:05:42 UTC
Zscaler teams have developed, deployed, and completed the required testing for the fix in the beta environment. The fix has now been deployed to the Zscaler.net cloud. Deployment to the Zscloud.net cloud is scheduled to be completed by end of day.
Update - Wed, 18 Nov 2026 04:28:44 UTC
Zscaler is working towards identifying the cause of the issue and further updates will be shared when available
Update - Wed, 18 Nov 2026 05:19:44 UTC
Zscaler is investigating connectivity and tunnel stability issues impacting zscaler.net cloud on the SYD3 data center, with related timeout events also observed on zscalertwo.net and zscalerthree.net clouds. Our teams are reviewing potential network path-related factors and continue to monitor the affected environments. Further updates will be provided as more information becomes available.
Update - Wed, 18 Nov 2026 06:39:11 UTC
Zscaler is monitoring intermittent tunnel stability issues affecting the SYD3 data center across ZSN, ZS2, and ZS3. The issue has currently subsided, and the environment has remained stable since 0400 UTC, Nov 18. Zscaler continues to investigate potential network path-related factors and will provide further updates as available.
Update - Wed, 18 Nov 2026 19:10:10 UTC
Connection timeouts at the Sydney III data center increased again over the past several hours and have since declined. Our latest observations indicate that connectivity is currently stable. Zscaler continues to monitor connectivity and investigate the root cause. We will provide further updates as new information becomes available.
Update - Thu, 19 Nov 2026 07:37:20 UTC
Zscaler continues to investigate intermittent tunnel stability issues affecting Sydney 3 data center. Timeout events have reduced significantly, and current checks do not show packet loss from the Zscaler side. The root cause remains under investigation, with network path-related factors still under review. Zscaler continues to monitor the environment and collect additional diagnostic data to further isolate the cause.
Update - Thu, 19 Nov 2026 20:31:40 UTC
Zscaler identified network anomalies during the investigation and has taken action to address intermittent tunnel disconnections at the Sydney III data center. We are closely monitoring connectivity to validate the effectiveness of these actions while continuing to investigate the root cause. Further updates will be provided as more information becomes available.
Update - Tue, 17 Nov 2026 19:44:09 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 - Tue, 17 Nov 2026 21:15:29 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, 19 Nov 2026 20:34:13 UTC
Following the actions previously taken by Zscaler, the incident has been resolved. Our systems remain fully operational, and we will continue to monitor the situation closely to ensure ongoing stability.
Update - Thu, 12 Nov 2026 21:56:29 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 Nov 2026 22:28:59 UTC
Following the actions previously taken by Zscaler, the incident has been resolved. Our systems remain fully operational, and we will continue to monitor the situation closely to ensure ongoing stability.
Update - Thu, 12 Nov 2026 07:24:00 UTC
Zscaler has implemented preliminary mitigation measures to address the issue. The team is actively monitoring and evaluating the effectiveness of these measures. Admin UI Read-Only Mode has now been removed.
Update - Fri, 13 Nov 2026 02:41:12 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 - Tue, 10 Nov 2026 19:36:37 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 - Tue, 10 Nov 2026 10:33: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 - Tue, 10 Nov 2026 12:35:25 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 - Tue, 10 Nov 2026 06:07:29 UTC
Zscaler has implemented mitigation measures to address the issue. The incident is now resolved. Our systems remain fully operational, and we will continue to monitor the situation closely to ensure ongoing stability.
Update - Mon, 09 Nov 2026 07:30:55 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 - Mon, 09 Nov 2026 08:23:20 UTC
The Zscaler team has identified the root cause and is actively prioritizing the incident, exploring various mitigation options, and working to restore service for all affected traffic.
Update - Mon, 09 Nov 2026 17:33:33 UTC
Zscaler is working to mitigate the issue and will apply an interim workaround as needed. A long-term improvement is also being planned to help prevent similar issue.
Update - Mon, 09 Nov 2026 23:04:45 UTC
Service performance at the affected Sydney data center has returned to expected levels following a temporary workaround recommended by Zscaler. We continue to monitor the data center to confirm that performance remains stable. Zscaler is planning a long-term improvement to reduce the likelihood of recurrence. We will provide another update once monitoring is complete or sooner if conditions change.
Update - Tue, 10 Nov 2026 12:44:16 UTC
Monitoring remains ongoing to confirm continued stability, and we are continuing to plan a longer-term improvement to reduce the likelihood of similar degradation recurring. We will provide a further update once monitoring has been completed, or sooner if service conditions change.
Update - Wed, 11 Nov 2026 12:30:32 UTC
Monitoring remains ongoing while Zscaler continues to plan a longer-term improvement to reduce the likelihood of similar degradation recurring. We will provide a further update once monitoring has been completed, or sooner if service conditions change.
Update - Thu, 12 Nov 2026 04:04:58 UTC
Following the actions previously taken by Zscaler, the incident has been resolved. Our systems remain fully operational, and we will continue to monitor the situation closely to ensure ongoing stability.
Update - Wed, 04 Nov 2026 19:26:51 UTC
We have identified the root cause of the issue and working on resolution.
Update - Wed, 04 Nov 2026 22:08:58 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 - Wed, 04 Nov 2026 23:22:17 UTC
Update - Wed, 04 Nov 2026 23:24:10 UTC
Zscaler has observed packet loss on network paths serving Dallas, Miami, and Atlanta. We are investigating whether an upstream carrier or routing issue is contributing to the degraded performance and continue to assess the impact on Zscaler Internet Access (ZIA) and Zscaler Private Access (ZPA). If you are experiencing degraded performance with ZIA, fail over to an alternate Zscaler data center if one is configured. If you are experiencing degraded performance with ZPA, contact Zscaler Support for assistance with failing over to your secondary data center.
Update - Wed, 04 Nov 2026 23:50:18 UTC
Zscaler continues to investigate degraded performance affecting users of Zscaler Internet Access (ZIA) and Zscaler Private Access (ZPA) who connect through Dallas, Miami, or Atlanta. Packet loss on network paths serving Dallas and Miami briefly decreased before increasing again. We continue to monitor the affected paths and investigate whether an upstream carrier or routing issue is contributing to the degradation. Guidance for affected customers ZIA: If your deployment has an alternate Zscaler data center configured, you can fail over to that data center. ZPA: Contact Zscaler Support for assistance with failing over to your secondary data center. We will share further updates as the investigation progresses.
Update - Thu, 05 Nov 2026 00:24:08 UTC
Zscaler has observed periods of reduced packet loss on network paths serving Dallas, Miami, and Atlanta, where users of Zscaler Internet Access (ZIA) and Zscaler Private Access (ZPA) experienced degraded performance. Our investigation indicates that an issue on an upstream network provider's path is contributing to the packet loss. We are monitoring the affected paths to confirm sustained recovery. Customers who have already failed over should continue using their alternate data center until we confirm stability. If you continue to experience degraded performance with ZIA, you can fail over to an alternate Zscaler data center. For ZPA, please contact Zscaler Support for assistance with failover.
Update - Thu, 05 Nov 2026 20:14:33 UTC
The performance degradation affecting Zscaler Internet Access (ZIA) and Zscaler Private Access (ZPA) users connecting through Dallas, Miami, Atlanta, and Los Angeles has been resolved. One of Zscaler's network transit providers confirmed that disruptions within its network caused congestion. The provider has restored normal network operation, and Zscaler verified sustained stability through additional monitoring. Customers who temporarily switched to an alternate data center can now return to their original configuration. For assistance reverting ZPA failover changes, please contact Zscaler Support.
Update - Wed, 04 Nov 2026 16:36:38 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 - Wed, 04 Nov 2026 18:26:57 UTC
Zscaler continues to commit to resolving the issue and is actively engaged in efforts to isolate the cause and determine the root of the problem. Zscaler appreciates your ongoing patience and understanding during this process, and further updates will be provided as new information becomes available.
Update - Wed, 04 Nov 2026 18:31:39 UTC
Zscaler has implemented preliminary mitigation measures to address the issue. The team is actively monitoring and evaluating the effectiveness of these measures.
Update - Wed, 04 Nov 2026 19:44:05 UTC
Zscaler has stabilized services, and we are continuing to monitor overall service health.
Update - Fri, 06 Nov 2026 20:40:41 UTC
Zscaler has mitigated the issue affecting our WAS data center, and all systems have remained stable for the past two business days. Customers may begin moving traffic back to WAS, and we will continue to monitor closely during the transition.
Update - Thu, 12 Nov 2026 17:38:33 UTC
Update - Wed, 04 Nov 2026 04:22:28 UTC
Zscaler has identified the cause of the issue affecting the cluster as a resource utilization condition on backend nodes, which resulted in node instability and log processing delays. Remediation is in progress to free resources, restore node stability, and reduce accumulated lag. Some customers may continue to experience delayed log processing while the affected cluster recovers. Zscaler is closely monitoring recovery and will provide further updates as available.
Update - Wed, 04 Nov 2026 07:58:36 UTC
Zscaler is monitoring the recovery progress of the affected cluster. Weblog processing lag is expected to settle within the next 2 hours as the environment stabilizes. Zscaler will continue to monitor the situation and provide updates as they become available.
Update - Wed, 04 Nov 2026 09:54:33 UTC
Zscaler continues to monitor recovery of the affected cluster. Weblog processing lag has now returned to normal. We will keep monitoring the situation and provide further updates as they become available.
Update - Wed, 04 Nov 2026 19:07:16 UTC
Following the actions previously taken by Zscaler, the incident has been resolved. Our systems remain fully operational, and we will continue to monitor the situation closely to ensure ongoing stability.
Update - Mon, 02 Nov 2026 06:07:48 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 - Sat, 31 Oct 2026 02:47:26 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 - Sat, 31 Oct 2026 03:19:51 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, 02 Nov 2026 14:35:32 UTC
Following the actions previously taken by Zscaler, the incident has been resolved. Our systems remain fully operational, and we will continue to monitor the situation closely to ensure ongoing stability.
Update - Fri, 30 Oct 2026 08:27:22 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 - Fri, 30 Oct 2026 09:11:30 UTC
Zscaler has implemented preliminary mitigation measures to address the issue. The team is actively monitoring and evaluating the effectiveness of these measures.
Update - Fri, 30 Oct 2026 12:15:57 UTC
Following the actions previously taken by Zscaler, the incident has been resolved. Our systems remain fully operational, and we will continue to monitor the situation closely to ensure ongoing stability.
Update - Thu, 29 Oct 2026 01:04:30 UTC
An issue with a third-party network provider has been identified, and Zscaler teams are actively working to address and mitigate the problem.
Update - Thu, 29 Oct 2026 03:56:47 UTC
Zscaler is monitoring the connectivity degradation affecting international traffic from the Mexico Data Centers after upstream network conditions improved and monitoring alerts cleared as of 03:03 UTC. The issue was caused by a network event in the Mexico region. Zscaler will continue to monitor service health and network paths to ensure continued stability.
Update - Thu, 29 Oct 2026 07:45:29 UTC
Zscaler has monitored the connectivity issue and confirmed sustained stability with packet loss and latency at normal levels. This incident is now marked as Resolved.
Update - Tue, 27 Oct 2026 21:41:01 UTC
Zscaler has resolved the issue affecting administrative services on the zscloud.net cloud. Between 19:43 and 20:25 UTC, customers may have intermittently experienced Admin Portal unavailability, API errors, and an inability to save or activate policy and configuration changes. SCIM provisioning was also affected. Following further assessment, Zscaler confirmed that new device registrations and Zscaler Client Connector enrollments were not affected. Existing user connections, traffic forwarding, and security policy enforcement remained unaffected throughout the incident. Services have remained stable since 20:25 UTC.
27 incidents visible (ongoing and monitoring). A free account unlocks resolved history and filters.