Zscaler Outage History

Zscaler experienced an issue with the ZIdentity Portal affecting multiple cloud environments including zscaler.net, zscalerone.net, zscalertwo.net, zscloud.net, zscalerthree.net, private.zscaler.com, and zdxcloud.net. The incident impacted the Admin UI component and was actively investigated by Zscaler's team. The issue was resolved after 56 minutes of service disruption.

Zscaler experienced an issue with PAC file serving on its zscaler.net Cloud that lasted 7 minutes. The incident was classified as minor and has been resolved. Customers were directed to check their Zscaler customer support portal for detailed updates during the investigation.

Zscaler detected an issue with its Atlanta II datacenter in the Americas region that lasted 7 minutes. The incident had minor impact and users were advised to failover to secondary or alternate datacenters to avoid traffic disruption. The issue was resolved after a brief investigation period.

Zscaler experienced connectivity issues affecting traffic between India and European destinations, particularly the UK, impacting five data centers in Chennai, Hyderabad, Kolkata, and Mumbai. Customers experienced intermittent performance degradation for international traffic originating from these locations. The root cause was identified after 3.4 hours, with Zscaler engaging upstream service providers and advising customers to failover to secondary data centers during the incident.

Zscaler experienced a user authentication issue affecting the Beijing III and Shanghai II datacenters in the APAC region, causing traffic-impacting problems for users in those locations. The service team identified the root cause and worked on mitigation options to restore normal authentication services. The incident was resolved after 39 minutes, with users advised to failover to secondary or alternate datacenters during the outage.

Zscaler's Amsterdam II datacenter experienced an issue that impacted traffic routing for users in the EMEA region. The company identified the root cause and implemented remediation efforts to restore service stability. The incident lasted 2.6 hours with users advised to failover to secondary or alternate datacenters during the outage.

Zscaler experienced an issue with its Shanghai VI datacenter that affected APAC region traffic for 44 minutes. Users were advised to failover to secondary or alternate datacenters to mitigate traffic impacts. The incident was classified as minor and resolved after investigation.

Zscaler's Seattle datacenter experienced an issue that impacted traffic routing for users in the Americas region. The company advised customers to failover to secondary or alternate datacenters while they investigated and worked to restore services. The incident was resolved after 1.1 hours once the root cause was identified and addressed.

Zscaler experienced connectivity issues affecting their Beijing III, Shanghai, and Shanghai II datacenters, causing slowness, connection timeouts, and increased latency for users in the APAC region. The service disruption impacted multiple locations including Tianjin for approximately 1.2 hours. Users were advised to failover to secondary or alternate datacenters as a workaround during the incident.

Zscaler experienced an issue where access tokens generated before April 11, 2026 could not be used to deploy Zscaler Client Connector for VDI environments, causing "Init Config error" messages for administrators attempting deployments. The problem particularly impacted non-persistent VDI deployments without backup restore mechanisms, as agents failed to re-enroll on every boot when using old tokens from golden images. Zscaler deployed a mitigation across most cloud environments and provided a workaround of generating new access tokens, with full resolution scheduled for completion during a maintenance window.