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.
Root Cause: Preliminary root cause is attributed to an internal backend infrastructure issue, which has since been fully resolved.
Following the actions previously taken by Zscaler, the incident has been resolved.
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.
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.
Provider resolved: . The notice publication date does not establish the outage start.
resolved
Services have recovered following remediation of a network configuration issue by our infrastructure partner. We are continuing to monitor the environment to ensure stability.
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.
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.
Tokyo IV and Tokyo V Data Center Issue - zscalerthree.net
Provider resolved: . The notice publication date does not establish the outage start.
resolved
The performance issue has been resolved. The degradation was observed between 0800–1000 Japan time following resumption of business activity post a holiday period, and recovered without any intervention. The environment is confirmed stable.
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.
June 2026
New Delhi I Datacenter Issue - zscaler.net, zscalertwo.net, zscloud.net, zscalerthree.net, private.zscaler.com, zpatwo.net
Source not attested
Last archived state: investigating
View archived record details
investigating
Zscaler is currently investigating reports of an issue with its New Delhi I 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 s...
Administration UI and User Authentication Issues - zscalerthree.net
Source not attested
Last archived state: investigating
View archived record details
investigating
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: Primary CA was recoveredLatest Update - Fri, 26 Jun 2026 11:15:59 UTCFollowing the actions previously tak...
Oslo III Datacenter Scheduled Maintenance - IPv6 Enablement - zscaler.net, zscalertwo.net, zscloud.net, zscalerthree.net
minorSource not attested
Last archived state: resolved
View archived record details
resolved
Zscaler will be enabling IPv6 at our Oslo III (OSL3) Data Center. During the maintenance window the services through OSL3 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 June 29, 9:00 am PDT (June 29, 16:00 UTC)End time is June 29, 2:00 pm PDT (June 29, 21:00 UTC)Update - Mon, 29 Jun 2026 20:50:55 UTCThis activity has been completed. Please contact Zscaler Suppo...
Scheduled Maintenance Extended - APAC Region - zscalerthree.net
minorSource not attested
Last archived state: resolved
View archived record details
resolved
The Zscaler Site Reliability Engineering team will be extending the scheduled maintenance of the APAC region's datacenters on zscalerthree.net cloud by 3 hours. During this extended maintenance window the ZIA Admin Portal, including policy management and reporting access, and new user authentication should be successful. As part of our standard maintenance process, all logs will be collected and available after maintenance has been completed.
Connectivity Issues Affecting India Data Centers - zscaler.net, zscalertwo.net, zscloud.net, zscalerthree.net, private.zscaler.com, zpatwo.net
Source not attested
Last archived state: investigating
View archived record details
investigating
Zscaler has detected an issue with its Chennai II, Chennai III, Hyderabad I, Mumbai VI, Mumbai VII, New Delhi I datacenter and is currently investigating the matter. 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. We will continue to provide updates here as t...
Warsaw II (WAW2) Datacenter Issue - zscaler.net, zscloud.net
Source not attested
Last archived state: investigating
View archived record details
investigating
Zscaler has detected an issue with its Warsaw II (WAW2) datacenter and is currently investigating the matter. 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 chec...
Vancouver I Datacenter Issue - zscalertwo.net
Source not attested
Last archived state: investigating
View archived record details
investigating
Zscaler has detected an issue with our Vancouver 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 chan...
ZPA Diagnostic logs Issue - private.zscaler.com
Source not attested
Last archived state: investigating
View archived record details
investigating
Zscaler is currently investigating reports of issues with its private.zscaler.com 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 an internal processing issueLatest Update - Wed, 24 Jun 2026 03:45:28 UTCFollowing the actions previously t...
Intermittent 403 Errors - zslogin.net
partialSource not attested
Last archived state: investigating
View archived record details
investigating
Zscaler has detected an issue with its zslogin.net Cloud. Customers may experience intermittent 403 errors when attempting to access zslogin.net. 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 fix was deployed to restore stability following a software defect.Lat...
Authentication Errors Affecting Zscaler Client Connector (ZCC) API Requests via the Authentication Service - zscalertwo.net, zscalerthree.net
partialSource not attested
Last archived state: investigating
View archived record details
investigating
Zscaler is investigating an issue impacting a subset of customers where API requests to the Zscaler Client Connector (ZCC) APIs through the Authentication Service (ZIdentity) may return HTTP 401 responses. Other API services may continue to operate as expected. Zscaler teams are actively investigating the issue and working to identify the cause. We will provide additional updates as more information becomes available. For detailed updates, please check the Service Status section in your Zsca...
