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.
August 2026
Reporting and Logging Issue - zscalerthree.net
partialSource not attested
Last archived state: investigating
View archived record details
investigating
Zscaler has identified a reporting and logging issue affecting the zscalerthree.net cloud. A subset of customers may experience delays or issues with logging and reporting. 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 failed over services to a healthy no...
ZTW Cloud Connector: Intermittent ZPA Access Impact for Some VDI/AVD Users - zscaler.net, zscalertwo.net, zscloud.net, zscalerthree.net
partialSource not attested
Last archived state: investigating
View archived record details
investigating
Zscaler is aware of and investigating an intermittent issue affecting a subset of users connecting through ZTW Cloud Connectors from VDI/AVD environments. Impacted users may be unable to access certain ZPA private applications, even though DNS resolution completes successfully.Zscaler has identified an interim mitigation to clear impacted sessions and help restore access while a permanent fix is being developed. Customers experiencing this issue should contact Zscaler Support for assistance w...
Administration UI and User Authentication Issues - zscalertwo.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 zscalertwo.net Cloud. Customers may encounter issues with Administation UI login, Authentication, User Policies, Zscaler Client Connector portal, and SCIM auto-provisioning. 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 poste...
Zscaler has identified an issue affecting ZPA App Connector connectivity in the China region, impacting services through the Shanghai and Beijing data centers. Affected customers may experience application access failures, including AC connection setup timeout or cannot connect to broker errors. 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 a...
Datacenter Expansion San Francisco IV (SJC4) - zpatwo.net
minorSource not attested
Last archived state: resolved
View archived record details
resolved
As part of our regular expansion of capacity, we are adding ZPA Public Service Edge nodes to our existing data center in San Francisco IV (SJC4).If you restrict outbound firewall access, please ensure you have added the complete set of published IPs in the URL belowhttps://config.zscaler.com/zpatwo.net/zpaUpdate - Thu, 20 Aug 2026 17:04:14 UTCThis activity has been completed. Please contact Zscaler Support if you have additional questions.
ZPA connectivity issues in China region - private.zscaler.com
Source not attested
Last archived state: investigating
View archived record details
investigating
Zscaler is investigating an issue with its Beijing III, Shanghai I datacenter on the private.zscaler.com cloud and is currently investigating the matter. 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: Root cause of this issue is attributed to a recent configuratio...
Mexico City I and Mexico City II - Data Center Issue - zscaler.net, zscalertwo.net, zscloud.net, zscalerthree.net, private.zscaler.com
partialSource not attested
Last archived state: investigating
View archived record details
investigating
Zscaler is investigating a network connectivity issue affecting some traffic associated with our Mexico City I and Mexico City II Data Centers. Customers may experience intermittent increases in latency and degraded performance. 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 provide further updates as additional information becomes avai...
Datacenter Expansion Singapore V (SIN5) - 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 existing data center in Singapore V (SIN5).If you restrict outbound firewall access, please ensure you have added the complete set of published IPs in the URL belowhttps://config.zscaler.com/private.zscaler.com/zpa
Unexpected Changes to Data Matching and Aggregation Behavior - app.avalor.io, app.eu.avalor.io, app.aps.avalor.io
partialSource not attested
Last archived state: investigating
View archived record details
investigating
Zscaler has detected an issue with its app.avalor.io, app.eu.avalor.io, app.aps.avalor.io Cloud. Some customers may experience changes in how incoming data is matched, merged, and aggregated, which could lead to differences in normalized results, aggregated outputs, and first-seen or other derived values.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 c...
Datacenter Expansion Capetown IV (CPT4) - zpatwo.net
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 EMEA, Capetown IV (CPT4).If you restrict outbound firewall access, please ensure you have added the complete set of published IPs in the URL belowhttps://config.zscaler.com/zpatwo.net/zpa
