Cloudi-Fi - Notice history

All systems operational

Captive Portals - Operational

100% - uptime
Feb 2026 · 99.9%Mar · 100%Apr · 100%
Feb 202699.9% uptime
Mar 2026100% uptime
Apr 2026100% uptime

Admin Interface - Operational

100% - uptime
Feb 2026 · 100%Mar · 100%Apr · 100%
Feb 2026100% uptime
Mar 2026100% uptime
Apr 2026100% uptime

DHCP - Operational

100% - uptime
Feb 2026 · 100%Mar · 100%Apr · 100%
Feb 2026100% uptime
Mar 2026100% uptime
Apr 2026100% uptime

Notice history

Apr 2026

Zscaler Error Code: 581000
  • Resolved
    Resolved

    Incident Update: Resolved

    Resolved: Global Service Restoration

    We have confirmed that service has been fully restored across all Zscaler clouds and regions, including the previously impacted nodes in Singapore, Chennai 2, and the US. Zscaler has implemented a global fix, and our internal telemetry shows that all integration traffic is now flowing normally.

    Next Steps

    Our engineering leadership is currently awaiting the formal Root Cause Analysis (RCA) from Zscaler’s engineering team. Once we have reviewed their technical breakdown of the multi-region disruption, we will provide a comprehensive summary to all affected customers.

  • Monitoring
    Monitoring

    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

  • Update
    Update

    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.

  • Update
    Update

    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.

  • Update
    Update

    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.

  • Update
    Update

    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.

  • Identified
    Identified

    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.

  • Investigating
    Investigating

    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.

New features release on April 2nd, 2025
  • Completed
    April 02, 2026 at 12:00 PM
    Completed
    April 02, 2026 at 12:00 PM
    Maintenance has completed successfully
  • In progress
    April 02, 2026 at 8:00 AM
    In progress
    April 02, 2026 at 8:00 AM
    Maintenance is now in progress
  • Planned
    April 02, 2026 at 8:00 AM
    Planned
    April 02, 2026 at 8:00 AM

    The planned deployment is scheduled for Thursday, April 2nd, 2026, from 10 a.m. to 2 p.m. CET. No service interruption is expected.

    This release introduces several updates and improvements:

    Features and enhancements

    • Device search module 

      • New module to locate any device on the network using filters: Device Name, IP Address, Hostname, Device Brand, DHCP Lease Status, Locked IP, MAC Address.

    • MAC-Based authentication - Huawei NCE iMaster 

      • Cloudi-Fi now supports MAC-based authentication with Huawei NCE iMaster. See dedicated KB article.

    • VPN IPSec logs for DHCP tunnels

      • Administrators can view and search IPSec tunnel negotiation logs directly from the admin interface, in a human-readable format. 

    • User accounts page - Beta 

      • Centralized view of all registered users, with:

        • Consolidated user list with account info and status

        • Advanced search and filtering by multiple criteria

        • Reset password directly from a user's account

        • Change profile for any user

        To enable: Profile icon → My Account → Interface version → Beta → Save changes.

    • Subscription messaging 

      • Revised alerts now distinguish between a limit being reached vs. genuinely exceeded, replacing the ambiguous "You exceed your subscription" message.

    • Security monitoring enhancements 

      • Improved detection and tracking of suspicious activity patterns across the platform.

    • NAC provider – Entra ID group filtering 

      • Administrators can now filter and restrict groups imported from Microsoft Entra ID, simplifying group management.

    Bug fixes

    • NAC providers were not displaying correctly due to a missing display name field. This has been corrected, and all NAC providers now appear as expected in the interface.

    • When a search or filter operation returns no results, a clear and descriptive message is now shown to inform the administrator that no matching records were found, eliminating any ambiguity.

    For more details about the release, please visit our Release Information Page.

Pre-release deployment adjustment
  • Completed
    April 01, 2026 at 9:00 PM
    Completed
    April 01, 2026 at 9:00 PM
    Maintenance has completed successfully
  • In progress
    April 01, 2026 at 7:00 PM
    In progress
    April 01, 2026 at 7:00 PM
    Maintenance is now in progress
  • Planned
    April 01, 2026 at 7:00 PM
    Planned
    April 01, 2026 at 7:00 PM

    We will be performing a planned maintenance operation on Wednesday from 9:00 PM to 11:00 PM.

    What's happening?

    A pre-release deployment adjustment as part of our ongoing DevOps improvements.

    Impact:

    No service interruption is expected during this time.

    We are working to ensure a smooth and seamless update.

    If you have any questions, please contact our support team.

Mar 2026

Routing Update for Hong Kong Captive Portal Traffic
Scheduled for March 19, 2026 at 1:00 PM – 1:00 PM less than a minute
  • Planned
    March 19, 2026 at 1:00 PM
    Planned
    March 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

DHCP Service Disruption Impacting Network Connectivity
  • Postmortem
    Postmortem

    Incident Summary

    On 17 March 2026, an incident impacted a subset of dedicated servers hosted on a specific rack, resulting in temporary service unavailability for affected customers. The issue was identified, contained, and resolved within a short time window.

    Timeline (UTC)

    • Start Time: 05:35 UTC

    • Incident Identified: Shortly after detection, the issue was traced to a specific rack.

    • Resolution Time: 06:20 UTC

    • Total Duration: ~45 minutes

    Impact Assessment

    • Affected Services: Dedicated servers located on a specific rack.

    • Customer Impact:

      • Temporary loss of access to impacted servers

      • No data loss or security impact identified

    • Scope: Limited to servers within the specified rack; no broader infrastructure impact observed

    Root Cause

    The incident was caused by an electrical equipment issue affecting the power supply to the specified rack, resulting in temporary service disruption.

    Detection & Response

    • The issue was detected through monitoring alerts indicating service unavailability

    • Engineering teams promptly investigated and isolated the issue to the affected rack

    • Immediate remediation actions were initiated to restore power and stabilize affected systems

    Resolution

    • Power-related issues were addressed at the rack level

    • Systems were progressively restored and validated

    • Full service was confirmed restored by 06:20 UTC

    Preventive & Corrective Actions

    To reduce the likelihood of recurrence, the following actions are being undertaken:

    • Infrastructure Review: Inspection and validation of electrical components associated with the affected rack

    • Preventive Maintenance: Reinforcement of periodic checks for power equipment across racks

    • Monitoring Enhancements: Improved alerting for early detection of power anomalies

    • Operational Readiness: Review of incident response procedures to ensure continued rapid resolution

    Conclusion

    The incident was contained within a limited scope and resolved promptly. We remain committed to maintaining high availability standards and are taking proactive measures to further strengthen infrastructure resilience.


  • Resolved
    Resolved

    The issue impacting the DHCP service has now been resolved. Devices are successfully receiving IP address allocations, and network connectivity has been restored.

    We have also confirmed that associated services, including VPN connectivity, are functioning normally.

    Our team will continue to monitor the environment to ensure stability. Thank you for your patience.

  • Investigating
    Investigating

    An incident has been identified where the DHCP Node is currently unavailable, impacting the Cloudi-Fi VPNs and the automatic assignment of IP addresses to connected devices.

    As a result, new devices may fail to connect, and existing sessions may experience disruptions. Our engineering team is actively investigating the root cause and working on remediation.

Feb 2026 to Apr 2026

Next