Zscaler Outage History

Zscaler experienced an issue with its Washington DC IV datacenter that caused DNS resolution difficulties for some customers in the Americas region. The company identified the root cause and worked on a resolution during the 2.1-hour incident. Customers were advised to failover to secondary or alternate datacenters to mitigate traffic impact.

Zscaler's Brussels II datacenter experienced a service disruption affecting traffic on the zscaler.net and zscloud.net clouds due to faulty hardware. Users were advised to failover to secondary or alternate datacenters while experiencing traffic impacting issues. The incident was resolved after 352.4 hours once replacement hardware arrived onsite and was successfully swapped by Zscaler teams.

Zscaler's Cloud Browser Isolation (CBI) service experienced issues in the Middle East (UAE) region, preventing customers from creating new sessions. The problem was traced to an AWS service issue in the ME-CENTRAL-1 region's mec1-az2 availability zone. Customers were advised to change their region selection in the Admin Portal's Isolation profile settings as a workaround until AWS services were restored.

Zscaler experienced an issue with their Beijing III and Shanghai datacenters that impacted traffic routing for users in the APAC region. The service disruption lasted 1.1 hours and affected users' ability to route traffic through these primary datacenter locations. Zscaler identified the root cause and resolved the issue, recommending users failover to secondary datacenters during the incident.

Zscaler experienced connectivity issues affecting six India data centers (Chennai II, Hyderabad I, Kolkata I, Mumbai VI, Mumbai VII, and New Delhi I) due to subsea cable problems and upstream international network congestion. Customers experienced increased latency, slowness, and degraded performance when accessing US and Europe-hosted destinations via ZIA and ZPA services. The incident was resolved after 6.1 hours when network connectivity stabilized and services returned to normal performance levels.

Zscaler experienced connectivity issues affecting six data centers across India (Chennai II, Hyderabad I, Kolkata I, Mumbai VI, Mumbai VII, and New Delhi I), impacting traffic routing for users in the APAC region. Users were advised to failover to secondary or alternate data centers to maintain service continuity. The incident was resolved after 33 minutes of investigation and remediation efforts.

Zscaler experienced issues with their Endpoint Data Loss Prevention (DLP) and incident logging services across multiple cloud environments, preventing some customers from enforcing new DLP policies while existing policies continued to function normally. The incident affected customers on zscaler.net, zscloud.net, and zscalerthree.net clouds for approximately 38 hours. Zscaler identified the root cause and deployed a fix in phases across all affected cloud environments, with resolution completed by 01:00 UTC on February 26th.