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
Scheduled Maintenance Extended - EMEA Region - zscloud.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 EMEA region's datacenters on zscloud.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.
Urgent Maintenance on Dallas I, Dallas II, New York III, New York IV datacenters - zscaler.net
minorSource not attested
Last archived state: resolved
View archived record details
resolved
The Zscaler Site Reliability Engineering team will be performing an urgent maintenance on the Dallas I, Dallas II, New York III, New York IV datacenters on the zscaler.net cloud. This maintenance can take up to 3 hours to complete. We expect minimal to no impact to services during the maintenance window. All logs will be collected and available after maintenance is complete. Please contact Zscaler Support if you have additional questions.
Urgent Maintenance on Dallas I, Dallas II, Washington DC, Washington DC IV datacenters - zscloud.net
minorSource not attested
Last archived state: resolved
View archived record details
resolved
The Zscaler Site Reliability Engineering team will be performing an urgent maintenance on the Dallas I, Dallas II, Washington DC, Washington DC IV datacenters on the zscloud.net cloud. This maintenance can take up to 3 hours to complete. We expect minimal to no impact to services during the maintenance window. All logs will be collected and available after maintenance is complete. Please contact Zscaler Support if you have additional questions.
Zscaler is investigating an issue affecting Nanolog Streaming Service (NSS) feed filtering. 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.Latest Update - Thu, 18 Jun 2026 07:27:01 UTCZscaler has identified a permanent fix. The fix is being deployed to ZS3 and ZS3 Cloud this w...
Zscaler will be performing hardware maintenance in the Brussels II (PAR4) Datacenter.Maintenance window,Start: 2026-06-18 19:30 CESTEnd: 2026-06-18 21:30 CEST(i.e. 2026-06-18 17:30 - 19:30 UTC)During the maintenance, traffic will failover to redundant devices in the same datacenter. However, intermittent connections and connection reestablishment will be observed.Update - Thu, 18 Jun 2026 21:42:18 UTCThis activity has been completed. Please contact Zscaler Support if you have additional quest...
What Zscaler is standardizing the post-login landing experience so that tenants move to the Zscaler Experience Center as the steady-state destination instead of the Authentication Service.Action RequiredNo action is necessary. Zscaler encourages customers to utilize the Experience Center, as standalone portals are being phased out by Sept 30, 2026.AvailabilityChange is happening on June 19, 2026 What is changingZscaler is revising the Admin login redirection process to support the o...
Munich I (MUC1) Datacenter Network Maintenance - zscaler.net, zscloud.net
minorSource not attested
Last archived state: resolved
View archived record details
resolved
Zscaler will be performing hardware maintenance in the Munich I (MUC1) Datacenter.Maintenance window,Start: 2026-06-17 20:00 CESTEnd: 2026-06-17 23:00 CEST(i.e. 2026-06-17 18:00 - 21:00 UTC)During the maintenance, traffic will failover to redundant devices in the same datacenter. However, intermittent connections and connection reestablishment will be observed.Update - Thu, 17 Jun 2026 20:13:50 UTCThis activity has been completed. Please contact Zscaler Support if you have additional questions.
Manchester II (MAN2) 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 Manchester II (MAN2) Datacenter.Maintenance window,Start: 2026-06-17 22:00 BSTEnd: 2026-06-18 01:00 BST(i.e. 2026-06-17 21:00 - 2026-06-18 00:00 UTC)During the maintenance, traffic will failover to redundant devices in the same datacenter. However, intermittent connections and connection reestablishment will be observed.Update - Wed, 17 Jun 2026 23:07:39 UTCThis activity has been completed. Please contact Zscaler Support if you have addit...
Atlanta II (ATL2) Datacenter Network Maintenance - zscaler.net, zscalertwo.net, zscloud.net, zscalerthree.net, private.zscaler.com
minorSource not attested
Last archived state: resolved
View archived record details
resolved
Zscaler will be performing hardware maintenance in the Atlanta II (ATL2) Datacenter.Maintenance window,Start: 2026-06-17 03:00 EDTEnd: 2026-06-17 07:00 EDT(i.e. 2026-06-17 07:00 - 11:00 UTC)Update - Wed, 17 Jun 2026 09:56:29 UTCThis activity has been completed. Please contact Zscaler Support if you have additional questions.
Urgent Maintenance on AMER Region - zscloud.net
minorSource not attested
Last archived state: resolved
View archived record details
resolved
The Zscaler Site Reliability Engineering team will be performing an urgent maintenance on AMER Region on the zscloud.net cloud. This maintenance can take up to 4 hours to complete. We expect minimal to no impact to services during the maintenance window. All logs will be collected and available after maintenance is complete. Please contact Zscaler Support if you have additional questions.
