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.
May 2026
RI DC Test - zscaler.net
majorSource not attested
Last archived state: investigating
View archived record details
investigating
Zscaler has detected an issue with its Atlanta II 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 chang...
Chicago I (CHI1) Datacenter Network Maintenance - zscaler.net, zscalerone.net, zscalertwo.net, zscalerthree.net, zpabeta.net
majorSource not attested
Last archived state: investigating
View archived record details
investigating
Zscaler will be performing hardware maintenance in Chicago I (CHI1) Datacenter Datacenter.Scheduled Maintenance window, Start: 2026-05-15 23:00 UTC End: 2026-05-16 01:00 UTC (Local Time 2026-05-15 18:00 - 2026-05-15 20:00)
Urgent Maintenance - zdxcloud.net
majorSource not attested
Last archived state: investigating
View archived record details
investigating
The Zscaler SRE team will be performing an urgent maintenance on the zdxcloud.net cloud. This maintenance is scheduled for Thursday at 03:00 AM UTC on 14th May, 2026, and can take up to 2 hour to complete. During this maintenance window the ZDX Admin Portal, including policy management, reporting access, and authentication of new users will not be available. As part of our standard maintenance process all logs will be collected and available after maintenance has completed.Update - Thu, 14 Ma...
London III (LON3) Datacenter Network Maintenance - zscaler.net
minorSource not attested
Last archived state: resolved
View archived record details
resolved
Zscaler will be performing hardware maintenance in the London III (LON3) Datacenter.Maintenance window,Start: 2026-05-14 20:30 BSTEnd: 2026-05-14 23:30 BST(i.e. 2026-05-14 19:30 - 22:30 UTC)Update - Thu, 14 May 2026 21:54:47 UTCThis activity has been completed. Please contact Zscaler Support if you have additional questions.
Datacenter Maintenance - private.zscaler.com
minorSource not attested
Last archived state: resolved
View archived record details
resolved
Zscaler is performing proactive emergency maintenance activity for data centers across Geo regions.Users may observe very brief disconnect and reconnect to ZPA cloud during the maintenance activity. Update - Wed, 13 May 2026 14:50:30 UTCThis activity has been completed. Please contact Zscaler Support if you have additional questions.
Duplicate User Activity Logs Observed in SIEM LSS - private.zscaler.com, zpatwo.net
majorSource not attested
Last archived state: investigating
View archived record details
investigating
Zscaler is investigating an issue impacting a subset of customers using SIEM Log Streaming Service (LSS), where duplicate User Activity log entries may be observed within streamed payloads. Customers may experience increased SIEM log ingestion volume. There is no impact to inline traffic processing, policy enforcement, or overall service availability.Zscaler teams are actively investigating the issue and evaluating mitigation options. For detailed updates, please check the Service Status sect...
Connectivity Issues Affecting India Data Centers - zscaler.net, zscalertwo.net, zscloud.net, zscalerthree.net, private.zscaler.com, zpatwo.net
majorSource not attested
Last archived state: investigating
View archived record details
investigating
We are currently investigating a connectivity issue impacting traffic between India and certain European destinations, primarily the UK. Customers may experience intermittent performance degradation affecting international traffic originating from the following Zscaler data centers: Chennai II, Hyderabad I, Kolkata I, Mumbai VI, and Mumbai VII. If you’re currently experiencing any traffic impacting issues please failover to your secondary DC or any other alternate DC. For more information, ...
Singapore IV (SIN4) Datacenter Network Maintenance - zscloud.net, zscalerthree.net, zdxcloud.net
majorSource not attested
Last archived state: investigating
View archived record details
investigating
Zscaler will be performing hardware maintenance in the Singapore IV (SIN4) Datacenter.Maintenance window,Start: 2026-05-15 11:00 UTCEnd: 2026-05-15 13:00 UTC(Local Time 2026-05-15 19:00 - 21:00)
Zscaler will be performing hardware maintenance in the Zurich I (ZRH1) Datacenter.Maintenance window,Start: 2026-05-13 19:00 CESTEnd: 2026-05-13 23:00 CEST(i.e. 2026-05-13 17:00 - 21:00 UTC)During this maintenance, traffic will failover to redundant devices in the same datacenter, and we expect no service impact.Update - Wed, 13 May 2026 23:50:32 UTCThis activity has been completed. Please contact Zscaler Support if you have additional questions.
Zscaler will be enabling IPv6 at our Copenhagen II (CPH2) Data Center. During the maintenance window the services through CPH2 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 May 15, 9:00 am PDT (May 15, 16:00 UTC)End time is May 15, 2:00 pm PDT (May 15, 21:00 UTC)
