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.
The Zscaler Site Reliability Engineering team will be performing a scheduled maintenance on the AMER region's Egress NAT nodes on zscalerone.net, zscalertwo.net, zscalerthree.net, zscloud.net and zscaler.net clouds. This maintenance is scheduled for Saturday at 6:00 PM Pacific Time on Mar 14, 2026 (Sunday, Mar 15, 2026 01:00 AM UTC), and 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 ...
The Zscaler Site Reliability Engineering team will be performing a scheduled maintenance on the APAC region's Egress NAT nodes on zscalerone.net, zscalertwo.net, zscalerthree.net, zscloud.net and zscaler.net clouds. This maintenance is scheduled for Saturday at 6:00 AM Pacific Time on Mar 14, 2026 (Saturday, Mar 14, 2026 01:00 PM UTC), and 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 afte...
The Zscaler Site Reliability Engineering team will be performing a scheduled maintenance on the EMEA region's Egress NAT nodes on zscalerone.net, zscalertwo.net, zscalerthree.net, zscloud.net and zscaler.net clouds. This maintenance is scheduled for Friday at 6:00 PM Pacific Time on Mar 13, 2026 (Saturday, Mar 14, 2026 01:00 AM UTC), and 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 ...
