| Posted on: Mon, 22 Dec 2025 06:52:31 UTC | |
| Impact Start Time: Mon, 22 Dec 2025 06:52:21 UTC | |
| Shanghai II (SHA2), Beijing (BJS1), Beijing III (BJS3) Datacenter Issue Customer Impact: Customers may encounter intermittent issues with CDN URLs failing to resolve. Available Workaround: For Road warriors: Modify PAC File or Subcloud and remove the problematic Datacenter. For more information please refer to: https://help.zscaler.com/zia/editing-subcloud. For customers using GRE: It is important to ensure that you fail over to the secondary DC. For more information on configuring high availability when using GRE, please refer to https://help.zscaler.com/zia/configuring-gre-tunnels. For customers using IPsec: It is also important to ensure that you fail over to the secondary DC. For more information on configuring high availability when using IPsec, please refer to https://help.zscaler.com/zia/configuring-ipsec-vpn-tunnel. Next Update: 4 Hours Datacenters affected: APAC, Beijing, Beijing III, Shanghai II Status: In Progress Event Type: Under Investigation Zscaler is currently investigating reports of an issue with its Shanghai II (SHA2), Beijing (BJS1), Beijing III (BJS3) datacenters. We are investigating periods of slowness, connection timeouts and/or increased latency. 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. Latest Update - Tue, 23 Dec 2025 08:37:37 UTC We applied a partial mitigation in our Beijing (BJS3) environment by switching to alternative public DNS resolvers, which has significantly reduced DNS errors. Validation confirms these resolvers successfully resolve the affected domains, whereas the previous resolvers were intermittently not able to get response from authoritative DNS servers. Some users may still experience intermittent issues. We plan to extend the change during the next off-peak maintenance window and will provide the next update as we proceed. Update - Mon, 22 Dec 2025 08:24:46 UTC Zscaler has implemented mitigation for the issue. Our systems remain fully operational, and we will continue to monitor closely to ensure ongoing stability. Update - Mon, 22 Dec 2025 10:58:22 UTC The issue has resurfaced, impacting Shanghai II (SHA2), Beijing (BJS1), Beijing III (BJS3) datacenters with intermittent slowness, timeouts, and increased latency. We are investigating further and will share updates when available. Update - Mon, 22 Dec 2025 15:50:23 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, 22 Dec 2025 18:12:17 UTC We have not yet received an update from the initial service provider we engaged. In parallel, we are working with another provider familiar with the issue to continue the investigation and determine recommended actions. We will share further updates as soon as more information becomes available. Update - Tue, 23 Dec 2025 03:30:02 UTC We have not yet received an update from the providers we engaged. We are contacting them to confirm the recommended next steps and will share further updates as soon as additional information becomes available. Update - Tue, 23 Dec 2025 07:20:32 UTC We applied a partial mitigation on the BJS3 ZSN cloud by shifting to alternative public DNS resolvers and are observing the issue and related metrics. We are monitoring error rates and resolution latency, coordinating with external partners, and will review the metrics to discuss the effectiveness of the change and decide next steps at the upcoming checkpoint. Update - Tue, 23 Dec 2025 08:37:37 UTC We applied a partial mitigation in our Beijing (BJS3) environment by switching to alternative public DNS resolvers, which has significantly reduced DNS errors. Validation confirms these resolvers successfully resolve the affected domains, whereas the previous resolvers were intermittently not able to get response from authoritative DNS servers. Some users may still experience intermittent issues. We plan to extend the change during the next off-peak maintenance window and will provide the next update as we proceed. | |