Live  /  Zscaler  /  Incident

Zscaler: Network Connectivity Degradation — Mexico City I and Mexico City II Data Centers - zscaler.net, zscalertwo.net, zscloud.net, zscalerthree.net

Zscaler · zscaler.comResolved2026-10-10 20:20 UTC
Public — what happened

Summary

Zscaler said it detected a network connectivity problem at its Mexico City I and Mexico City II data centers starting around 20:56 UTC on 9 October 2026, and it advised affected customers to switch to a backup or other data center. The company said a subset of customers was affected and attributed the problem to a fiber fault in a third-party provider's network. Zscaler said it changed its routing to bypass the affected path, and by early on 10 October it reported that this had worked. At 20:20 UTC on 10 October it said service was restored and stable, with the routing changes staying in place while the provider finishes permanent repairs.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Zscaler against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Zscaler: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Zscaler report →

More from Zscaler

Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.

The full archive is on the Zscaler status & history page.

Related: Zscaler status & history. SquidGrid is not affiliated with Zscaler.