This incident has been resolved. Earlier today, two worker nodes in our production Kubernetes cluster became unreachable, which temporarily affected some booking and search/indexing services and caused newly created hotel bookings not to appear immediately in the archive (and duplicate booking warnings in some cases). The faulty nodes were removed and replaced by healthy nodes, affected services were restarted, and the system has remained stable during the monitoring period. All bookings are now visible in the archive/admin tools, no booking data was lost, and all systems are operational.
No components marked as affected
Resolved
This incident has been resolved. Earlier today, two worker nodes in our production Kubernetes cluster became unreachable, which temporarily affected some booking and search/indexing services and caused newly created hotel bookings not to appear immediately in the archive (and duplicate booking warnings in some cases). The faulty nodes were removed and replaced by healthy nodes, affected services were restarted, and the system has remained stable during the monitoring period. All bookings are now visible in the archive/admin tools, no booking data was lost, and all systems are operational.
Monitoring
Earlier today, some users may have experienced issues where newly created hotel bookings did not immediately appear in the booking archive or search, and in some cases duplicate booking warnings were shown when trying to rebook. The underlying infrastructure issue in our production Kubernetes cluster has been mitigated. All affected services are now running normally, bookings are visible in the archive/admin tools, and we have verified that no booking data was lost. Current status: all systems are operational and we are in a monitoring phase.
This page is continuously updated to reflect the current status of our systems. If you notice anything unusual that’s not reported here, please let us know at support@cteleport.com.