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.
Zscaler will be performing hardware maintenance in the Kolkata I (CCU1) Datacenter.Maintenance window,Start: 2026-05-06 01:30 ISTEnd: 2026-05-06 03:30 IST(i.e. 2026-05-06 20:00 - 22:00 UTC)During this maintenance, traffic will failover to redundant devices in the same datacenter, and we expect no service impact. Update - Wed, 06 May 2026 21:11:43 UTCThis activity has been completed. Please contact Zscaler Support if you have additional questions.
Tel Aviv II (TLV2) Datacenter Scheduled Maintenance - zscloud.net
majorSource not attested
Last archived state: investigating
View archived record details
investigating
Zscaler will be performing hardware maintenance in Tel Aviv II (TLV2) Datacenter.New Maintenance window, Start: 2026-05-05 01:00 UTC End: 2026-05-05 04:00 UTC (Local Time 2026-05-05 04:00 - 2026-05-05 07:00 Local Time)
ZPA Logging zone Maintenance - zpatwo.net
majorSource not attested
Last archived state: investigating
View archived record details
investigating
We will be performing maintenance activities to add a new Logging Zone in ZPATWO cloud to augment capacity, availability and resiliency. Some customers may witness below impact during this maintenance window:Admin UI dashboards and diagnostics may display incomplete data temporarily.If alerts are configured for these components, false events may be triggered.Nanolog enabled customer will see timeouts on the dashboards.Important Note:This maintenance will not impact live traffic. ZCC enrollmen...
Hong Kong III Datacenter Scheduled Maintenance - IPv6 Enablement - zscalertwo.net, zscalerthree.net
majorSource not attested
Last archived state: investigating
View archived record details
investigating
Zscaler will be enabling IPv6 at our Hong Kong III (HKG3) Data Center. During the maintenance window the services through HKG3 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 5, 9:00 am PDT (May 5, 16:00 UTC)End time is May 5, 5:00 pm PDT (May 6, 00:00 UTC)Update 5/5: Extending Maintenance
Helsinki I Datacenter Scheduled Maintenance - IPv6 Enablement - zscaler.net, zscalertwo.net, zscalerthree.net
majorSource not attested
Last archived state: investigating
View archived record details
investigating
Zscaler will be enabling IPv6 at our Helsinki I (HEL1) Data Center. During the maintenance window the services through HEL1 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 7, 9:00 am PDT (May 7,16:00 UTC)End time is May 7, 2:00 pm PDT (May 7, 21:00 UTC)
Helsinki I Datacenter Scheduled Maintenance - Service Expansion - zscloud.net
majorSource not attested
Last archived state: investigating
View archived record details
investigating
Zscaler will be expanding its global data center footprint and performing maintenance at our Helsinki I (HEL1) data center. We expect minimal to no impact to services during the maintenance window. Please update your firewall policy rules and any upstream Access Control Lists to allow all IP addresses for this DCFor more information, please visit:https://config.zscaler.com/zscloud.net/cenrMaintenance Window:Start time is May 7, 9:00 am PDT (May 7, 16:00 UTC)End time is May 7, 2:00 pm PDT...
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 8, 9:00 am PDT (May 8, 16:00 UTC)End time is May 8, 2:00 pm PDT (May 8, 21:00 UTC)
On April 29, 2026, Zscaler was made aware of CVE-2026-31431, a Local Privilege Escalation (LPE) vulnerability affecting Linux kernel versions 4.14 and later. Zscaler has addressed the vulnerability across all its clouds through patching or mitigation. Zscaler Internet Access (ZIA) distributed products are not impacted. Zscaler suggests adhering to the instructions issued by the operating system vendors for any Linux systems and Zscaler products listed below:Zscaler Private Access (ZPA):&...
Zscaler will be enabling IPv6 at our Capetown IV (CPT4) Data Center. During the maintenance window the services through CPT4 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 7, 9:00 am PDT (May 7, 16:00 UTC)End time is May 7, 2:00 pm PDT (May 7, 21:00 UTC)
Zscaler will be enabling IPv6 at our Amsterdam II (AMS2) Data Center. During the maintenance window the services through AMS2 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 6, 10:00 am PDT (May 6, 17:00 UTC)End time is May 6, 3:00 pm PDT (May 6, 22:00 UTC)
