Zscaler favicon

Zscaler outage on 2026-11-04

zscaler.com
November 2026 4 Minor incident

Zscaler flagged degraded performance for some users connecting through Dallas, Miami, and Atlanta starting at 22:52 UTC on 4 November 2026. The disruption ran for 1h 35m and the fault sat on Zscaler's side, affecting five listed components including the broader Americas region.

Started

22:52 UTC

Duration

Lasted 1h 35m

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: Denver III, Americas, Atlanta II, Dallas I, Miami III

What happened?

Zscaler's status page logged a single incident on 4 November 2026, titled "Degraded Performance for Some Users Connecting Through Dallas, Miami, and Atlanta". It started at 22:52 UTC and lasted 1h 35m. Five components were listed as affected: Denver III, Americas, Atlanta II, Dallas I, and Miami III, which points to a regional edge problem rather than a single data centre fault. Zscaler filed no updates against this incident, so there is no record of what was degraded, how severe it got, or when it was confirmed resolved beyond the closing timestamp implied by the duration. No user reports were filed during the window on this page. For context, Zscaler has logged 37 incidents in the past 90 days with a median duration of 1 hour 48 minutes, and 379 incidents all time, averaging 8.8 a month, so this sits within a pattern of frequent, usually short disruptions rather than being unusual for the provider. With zero updates published, you are left with the title and the component list as the only facts on record. Zscaler's own status page does not say what caused the degradation. There is nothing here to confirm whether it was a routing issue, a capacity problem, or something else entirely.

Learning

UptimeRobot's own probes watch the edge component from EU and NA regions and recorded 99.959% uptime over 24 hours, 99.614% over 7 days, and 99.715% over 30 days, with this incident not registered against those probe results. That is not a contradiction. Zscaler's incident described degraded performance for some users connecting through specific regional points of presence, a symptom that can sit entirely inside the provider's internal routing or capacity layer without ever showing up as a hard failure on an external edge check. Your own monitoring, watching your application and its dependencies, would have no visibility into which of Zscaler's regional nodes a given user session landed on. This is the general shape of these incidents: a partial, user-specific slowdown that a probe hitting a healthy endpoint simply will not reproduce, while real sessions routed through Dallas, Miami, or Atlanta could still have felt it. Over the past 30 days UptimeRobot recorded 10 incidents against this provider, all resolved, with a median duration of 2h 27m, longer than this one's 1h 35m, which gives a sense of the usual range. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.

4.7
stars out of 5
284+ reviews on

Start monitoring in 30 seconds.

There's nothing to install. No credit card required. 50 monitors for free.