Zscaler's Chennai II datacentre had an issue affecting the APAC region for 1h 25m on 2 November 2026. The fault sat on Zscaler's side of the connection, not yours.
Started
05:41 UTC
Duration
Lasted 1h 25m
Source
IsDown
Next time
Zscaler is degraded. Is your product working?
An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.
50 monitors for your own websites. No card.
Affected components: APAC, Chennai II
What happened?
Zscaler's own status page logged one incident on 2 November 2026, titled "Chennai II Datacenter Issue", starting at 05:41 UTC and lasting 1h 25m. It touched two listed components: the APAC region and the Chennai II datacentre itself. Zscaler published no updates against this incident, so there is no account of what failed inside the datacentre, no mitigation note, and no confirmation of root cause. That leaves the cause not on the record. No user reports were filed during the window that this page covers. Over the past 90 days Zscaler has logged 36 incidents with a median duration of 1 hour 49 minutes, so this one at 1h 25m sits a little under that median, not an outlier for this provider. Across its history Zscaler averages 8.8 incidents a month, which puts this single-incident day well within its normal pattern rather than a one-off bad day. With zero updates published, you're left with a start time, a duration and a location, and nothing else from Zscaler's side to work with.
Learning
UptimeRobot's own probes watch Zscaler's edge from the EU and North America, and for this incident they stayed at 100% uptime over the preceding 24 hours, which is consistent with the fault being confined to APAC and Chennai II rather than the edge paths those probes check. That is not a contradiction: a regional datacentre issue can take down service for users routed through Chennai II while leaving every other region's edge path untouched, and both readings are accurate for what they each measure. This is the general shape of a provider-side outage, it fails underneath you, in infrastructure you do not operate and cannot see into, so watching only your own application endpoints would not have shown you anything wrong. Over 30 days, UptimeRobot recorded 9 incidents against Zscaler with a median duration of 3h 7m, all resolved, giving you a sense of how often and how long these regional faults tend to run. If your users sit in or route through APAC, an incident like this one can affect them even while every monitor pointed at your own servers stays green. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.