- MonitoringMonitoring
Monitoring: Global Mitigation Applied by Zscaler
Zscaler has implemented a global fix to address the connectivity issues affecting multiple nodes (including Singapore, Chennai 2, and US-based data centers).
We have received initial confirmation from customers in both the US and APAC regions that service has been restored and they are now able to connect via their original primary nodes. Zscaler has also published an official update regarding this resolution on their Trust Portal: Zscaler Status Post 28871.
We are waiting the RCA from Zscaler engineering team
- UpdateUpdate
Monitoring: Expanded Impact to US Nodes & Escalation
The scope of this incident has broadened beyond the APAC region. We have now received reports of similar connectivity issues affecting Zscaler nodes in the US.
We have escalated this matter to senior Zscaler engineering leadership for an urgent, comprehensive investigation into what appears to be a multi-region disruption.
Current Status & Workarounds
While we await a global resolution from Zscaler, please continue to utilize the previously verified node failovers:
India: Move from Chennai 2 to Hyderabad 1.
APAC: Move from Singapore to Hong Kong 3 or Tokyo 4.
US: We are currently identifying stable target nodes for US traffic and will provide specific recommendations shortly.
Our internal teams remain on high alert and are working alongside Zscaler to stabilize service globally.
- UpdateUpdate
Monitoring: Additional Impacted Node (Chennai 2) & Verified Workaround
Our ongoing investigation has confirmed that the disruption is not limited to Singapore. The Chennai 2 node (India) is also experiencing significant instability. We have successfully verified a workaround with impacted customers in the region.
Verified Workaround
If you are experiencing connectivity issues or tunnel drops on the affected nodes, please implement the following failovers:
For India-based traffic (Chennai 2): Redirect tunnels to the Hyderabad 1 node. This has been confirmed to restore stable connectivity in live testing.
For Singapore-based traffic: Redirect to Hong Kong 3 or Tokyo 4.
We remain in constant communication with Zscaler support as they work toward a permanent fix for the Singapore and Chennai data centers.
- UpdateUpdate
Monitoring: Multiple Impacted Nodes Identified (Singapore & Chennai)
Our ongoing investigation has confirmed that the issue is not limited to the Singapore node. We have identified that the Chennai 2 node (India) is also experiencing disruptions, contributing to the connectivity issues across the APAC region.
Recommended Workaround
To restore connectivity immediately, we suggest customers manually switch their traffic to one of the following stable nodes:
Hong Kong 3
Tokyo 4
We continue to work with Zscaler to resolve the specific issue in Singapore and will provide a final update once the node is stabilized.
- UpdateUpdate
Monitoring: Expanded Scope & Investigation
Our investigation has confirmed that the impact extends beyond the zscloud.net environment to include zscaler.net and other Zscaler clouds within the APAC region.
Zscaler has acknowledged our high-priority ticket, and we are working closely with their team while our internal engineers continue to pursue a parallel remediation path.
- IdentifiedIdentified
Monitoring: Investigation & Remediation in Progress
Zscaler has officially acknowledged our support ticket and is investigating the issue. Simultaneously, our internal engineering teams are evaluating potential remediation steps to restore service for APAC customers.
We will share more details as our joint efforts progress.
- InvestigatingInvestigating
Investigating: Service Issues with Zscaler Integration (APAC)
We are currently investigating reports of connectivity issues affecting customers integrated with the zscloud.net cloud in the APAC region. We are working directly with Zscaler to identify the cause and will provide updates as they become available.
- PlannedMarch 19, 2026 at 1:00 PMPlannedMarch 19, 2026 at 1:00 PM
Change Description
We are implementing an update to the routing of captive portal redirection traffic originating from Hong Kong. Historically, this traffic did not transit through our China node. Following this change, all captive portal redirection traffic from Hong Kong will now be routed through our China infrastructure and directed to the Cloudi-Fi captive portal at login-cn.cloudi-fi.net.
Impact
No expected service disruption during the change.
Improved routing consistency for users connecting from Hong Kong.
All affected users will be redirected to the China-based captive portal endpoint (login-cn.cloudi-fi.net) and not anymore to (login.cloudi-fi.net) .
Change Date
This change will be deployed today (March 19th) at 2pm CET
Captive Portals - Degraded performance
Captive Portals
Admin Interface - Operational
Admin Interface
DHCP - Operational
DHCP

