Provider resolved: . The notice publication date does not establish the outage start.
resolved
Following the actions 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.
Zscaler has implemented preliminary mitigation measures to address the issue. The team is actively monitoring and evaluating the effectiveness of these measures.
Provider resolved: . The notice publication date does not establish the outage start.
resolved
Zscaler has resolved the issue affecting audit log visibility in the admin portal. The underlying cause has been addressed and audit logs are now visible and accessible across all affected clouds.
Provider resolved: . The notice publication date does not establish the outage start.
resolved
Zscaler has resolved the issue preventing a subset of administrators from logging into the Zscaler Admin Console. The issue was caused by a routing defect introduced in a recent build upgrade that caused IDP-based authentication requests to be misrouted to an incorrect region, resulting in a tenant lookup failure and 401 unauthorized error. The build has been successfully rolled back to the previous stable version, and admin console login has been confirmed restored.
Mexico City II Datacenter Issue - zscaler.net, zscalertwo.net, zscloud.net, zscalerthree.net
Provider resolved: . The notice publication date does not establish the outage start.
resolved
Zscaler can confirm that the issue has been resolved without any intervention. Preliminary findings indicate that the issue was observed within the network provider’s infrastructure, and our monitoring has confirmed that the network is stable.
Risk360 Data Update and Risk Score Accuracy Issue - zscaler.net, zscalerone.net, zscalertwo.net, zscloud.net, zscalerthree.net, zscalerrisk.net
Provider resolved: . The notice publication date does not establish the outage start.
resolved
Zscaler has resolved the issue causing interrupted ZPA-related data updates in Risk360. Affected connectors have been successfully reactivated and data updates have resumed across impacted accounts. A code-level fix addressing the underlying cause has been deployed to production. Risk360 data and risk scores are confirmed accurate and the issue is resolved.
Network Connectivity Degradation — Mexico City I and Mexico City II Data Centers - zscaler.net, zscalertwo.net, zscloud.net, zscalerthree.net
Provider resolved: . The notice publication date does not establish the outage start.
resolved
Following the routing adjustments applied by Zscaler, service has been restored at the Mexico City I and Mexico City II data centers, and monitoring has confirmed continued stability. The incident is resolved. The routing adjustments remain in place while the third-party provider completes permanent repairs to the affected connectivity.
Provider resolved: . The notice publication date does not establish the outage start.
resolved
Zscaler has resolved an issue where a subset of customers across ZSNet and ZSCloud may have experienced disruption in Cloud NSS firewall log delivery to their configured SIEMs. The issue has been fully resolved and services are confirmed stable.
Provider resolved: . The notice publication date does not establish the outage start.
resolved
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.
A fix has been verified and is planned for release in an upcoming production update, with more details to be shared as they become available.
Legacy Incident Archive
453 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
Zscaler will be enabling IPv6 at our Miami III (MIA3) Data Center. During the maintenance window the services through MIA3 Data Center will be restarted in phases to minimize the service impact.Other Zscaler sites and Zscaler Services will continue to operate normally.Maintenance Window:Start time is July 13, 4:00 pm PDT (July 13, 23:00 UTC)End time is July 13, 9:00 pm PDT (July 14, 4:00 UTC)Update - Tue, 14 Jul 2026 04:36:49 UTCThis activity has been completed. Please contact Zscaler Suppo...
Product Name Update: ZIdentity is now Authentication Service - zscaler.net, zscalerone.net, zscalertwo.net, zscloud.net, zscalerthree.net, private.zscaler.com, zdxcloud.net, zpatwo.net, zslogin.net
Source not attested
Last archived state: investigating
View archived record details
investigating
What's Changing?Zscaler is renaming ZIdentity to Authentication Service. This is a name change only, with no changes to product functionality.Why Are We Making This Change?The name Authentication Service more clearly reflects the product’s purpose as the centralized authentication and identity management service across Zscaler services.For more information, please refer to the following article: What is Authentication Service
Bogota I (BOG1) Data Center - Performance Degradation - zscalertwo.net
partialSource not attested
Last archived state: investigating
View archived record details
investigating
Zscaler is aware of and currently investigating performance degradation affecting the Bogota I (BOG1) Data Center. Customers may experience increased latency or degraded performance while accessing services through this location. 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 progres...
The Zscaler Site Reliability Engineering team will be performing an urgent maintenance during which access to the Zscaler Management Portal for Partners and ZDX Admin Portal might not be available. This maintenance is scheduled for Saturday at 11:00 AM Pacific Time on July 11, 2026 (Saturday, July 11, 2026 06:00 PM UTC), and can take up to 2 hours to complete. All logs will be collected and available after maintenance is complete. Please contact Zscaler Support if you have additional question...
Reporting and Logging Issue - zscaler.net, zscalerone.net, zscalertwo.net, zscloud.net, zscalerthree.net
partialSource not attested
Last archived state: investigating
View archived record details
investigating
Zscaler is currently investigating reports of an issue affecting Reporting and Logging on the zscalerthree.net cloud. Customers may intermittently encounter errors when attempting to download Web Insights logs.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 backen...
Tianjin Datacenter Issue - zscloud.net
Source not attested
Last archived state: investigating
View archived record details
investigating
Zscaler is currently investigating reports of an issue with its Tianjin datacenter. Customers may encounter disconnections, periods of slowness 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. We will continue to provide updates here as the investigation progresses. For detailed updates, please check the Service Status secti...
Datacenter Expansion New Delhi (DEL1) - private.zscaler.com
Source not attested
Last archived state: investigating
View archived record details
investigating
As part of our regular expansion of capacity, we are adding ZPA Public Service Edge nodes to our new data center in New Delhi I (DEL1).These would be available anytime on or after 11th July 2026.RegionLocationNotesASIANEW DELHI IOld DCThe IP addresses for the DC are part of the already published IP address range.Please update your firewall policy rules along with any upstream ACL(s) to allow the IP address ranges to avoid any service disruption.For more information, please visit:https://confi...
Changes in exclusion method for Zoom and Teams on iOS - zscaler.net, zscalerone.net, zscalertwo.net, zscloud.net, zscalerthree.net
Source not attested
Last archived state: investigating
View archived record details
investigating
As a part of Zscaler’s continuous product improvement process, we are making a change to how the built-in exclusions for Zoom and Teams work on iOS. Today these exclusions are processed inside Zscaler Client Connector (ZCC) itself, where ZCC will receive the traffic and then bypass it from tunneling. We have seen vastly improved performance with these applications by excluding this traffic pre-zcc, commonly referred to as VPN Gateway Bypass, and we will be making a change to exclude this t...
Zscaler will perform scheduled maintenance for Experience Center on Jul 18, 2026, 1:00 AM to 3:00 AM UTC. During this maintenance window, the service is expected to remain available; however, users may experience brief intermittent disruptions. This maintenance is intended to improve platform reliability and performance.After the maintenance is complete, service is expected to operate normally, and no customer action is required. If you experience any issues after the maintenance window, plea...
Intermittent Failures Affecting Mobile Admin Public API Requests - zscaler.net
partialSource not attested
Last archived state: investigating
View archived record details
investigating
Zscaler is investigating an issue causing intermittent failures for the Mobile Admin Public API service on zscaler.net. Some customers may experience failures when accessing the Mobile Admin public API.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 is...
