Zscaler Outage History

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 with their Kuala Lumpur I datacenter that affected APAC region traffic for 1.3 hours. The company recommended users failover to secondary or alternate datacenters to mitigate traffic impact while they investigated and worked to isolate the root cause. The incident was resolved after active troubleshooting efforts to identify and address the underlying problem.

Zscaler experienced an issue with its Mumbai VI datacenter in the APAC region that lasted 3.2 hours. The incident affected traffic routing through that datacenter, requiring users to failover to secondary or alternate datacenters to maintain service. Zscaler investigated and worked to isolate the problem and identify the root cause during the outage period.

Zscaler's Risk360 service experienced a data loading issue that caused computation delays, resulting in outdated or unavailable risk scores and insights displayed in dashboards. The incident affected the Admin UI component and lasted 56.7 hours, though actual security posture and traffic protection remained unaffected. Resolution involved addressing multiple dependencies to restore normal data processing and real-time scoring functionality.

Zscaler experienced issues with their Administration UI and Mobile Admin Portal across multiple clouds (zscaler.net, zscalertwo.net, and zscalerthree.net), causing customers to encounter intermittent slowness, timeouts, and increased latency when accessing these administrative interfaces. The Zscaler team identified the root cause and deployed mitigations progressively across the affected clouds, with testing showing improved service performance. The incident lasted 5.7 hours with mitigations being rolled out in phases, starting with zscaler.net and zscalerthree.net clouds, with completion expected within 45 minutes of the final update.

Zscaler experienced a software defect that prevented some customers from creating new Certificate Signing Requests (CSR) through the administration UI, with the CSR creation option appearing greyed out. The issue affected the Admin UI component and lasted 27.5 hours. Zscaler identified the root cause as a software defect and implemented a fix to restore normal CSR creation functionality.