Cloudi-Fi incident

Routing Update for Hong Kong Captive Portal Traffic

Minor Resolved View vendor source →
Started
Mar 19, 2026, 01:00 PM UTC
Resolved
Mar 19, 2026, 01:00 PM UTC
Duration
Detected by Pingoru
Mar 19, 2026, 01:00 PM UTC

Update timeline

  1. resolved Mar 19, 2026, 01:00 PM UTC

    Type: Maintenance Duration: 25 days, 18 hours and 40 minutes Affected Components: Captive Portals, DHCP, Admin Interface Apr 14, 07:39:41 GMT+0 - Completed - Maintenance has completed successfully. Mar 19, 13:00:00 GMT+0 - Identified - ### 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](http://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

Looking to track Cloudi-Fi downtime and outages?

Pingoru polls Cloudi-Fi's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Cloudi-Fi reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Cloudi-Fi alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Cloudi-Fi for free

5 free monitors · No credit card required