Zscaler's Mexico City I and Mexico City II datacentres had a 3 hour 10 minute issue starting at 00:48 UTC, affecting the Americas component. The fault sat on Zscaler's side of the connection.
Started
00:48 UTC
Duration
Lasted 3h 10m
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: Americas
What happened?
Zscaler's status page logged one incident on this day, titled "Mexico City I, Mexico City II Datacenter Issue", starting at 00:48 UTC and running for 3 hours 10 minutes. The affected component was listed simply as Americas, with no breakdown of which specific traffic or services were degraded. Zscaler published no updates during the incident's lifetime, so there is no record of what went wrong inside those two datacentres, no scope detail beyond the title, and no note on what fixed it. One filing from a vendor's status page, with zero updates attached, is thin evidence: it tells you an incident existed and roughly how long it lasted, nothing more. No user reports were filed during the window, so there is no independent account of what this looked like for anyone routing traffic through Mexico City. Zscaler's history shows 36 incidents in the past 90 days with a median duration of 2 hours 16 minutes, and 377 incidents across all time at a rate of about 9 a month, so a single-region datacentre issue of this length is well within the pattern for this provider. Zscaler's own 30-day record shows 8 incidents, all resolved, with a median duration of 3 hours 8 minutes, close to what this one ran. The cause is not on the record. Nothing Zscaler published explains whether this was hardware, routing, or something else inside those two facilities.
Learning
UptimeRobot's probes watch the edge component across European and North American regions, and over the 30 days surrounding this incident they recorded 8 incidents of their own, all resolved, with a median duration of 3h 8m, and this particular incident is not marked as registered against those probe results. That gap is expected rather than contradictory: Zscaler's Mexico City datacentre issue could sit entirely inside their own infrastructure, affecting traffic that never touches the specific edge paths UptimeRobot's probes exercise from the regions they check. A provider-side datacentre problem can degrade service for customers routed through that facility while leaving every external check elsewhere green, because the failure is regional and internal, not a wholesale collapse of the provider's edge. If you only watch your own endpoints, an outage like this can pass unnoticed until support tickets start arriving from the affected region, because your monitoring never reaches inside Zscaler's datacentre to see the fault directly. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.