Network connectivity issues for some newly created, restarted or migrated Cloud Servers
Incident
Report for IONOS CLOUD
Subscribe to Updates
Update
We are rolling out a fleet-wide update to mitigate remaining instances of lost routes on VMs.
Because this issue is primarily triggered during VM creation and migrations between hosts, and the current mitigation does not completely eliminate the risk of recurrence, we are taking additional precautions.
To minimize VM migrations and further protect your workloads, we have temporarily paused routine maintenance for Kubernetes and MongoDB.
A permanent fix for the underlying issue is currently undergoing Quality Assurance.
Because this issue is primarily triggered during VM creation and migrations between hosts, and the current mitigation does not completely eliminate the risk of recurrence, we are taking additional precautions.
To minimize VM migrations and further protect your workloads, we have temporarily paused routine maintenance for Kubernetes and MongoDB.
A permanent fix for the underlying issue is currently undergoing Quality Assurance.
Identified
We have identified additional affected hosts. While the identified issues have been mitigated, we are working on preventative measures.
Monitoring
The hosts affected by this issue have been repaired and connectivity has been restored for the servers reported to us. The rollout of the component that caused the issue has been paused. We continue to monitor the platform and will update this notice once the corrected component is in place on all hosts.
Identified
We have identified an issue in the network configuration layer of our compute hosts. In a small share of cases, a Cloud Server that is newly created, restarted or migrated to another host comes up without inbound and/or outbound network connectivity, while the server itself runs normally.
Servers that have not been created, restarted or migrated since 22 October 2026 are not affected. Managed Kubernetes node pools can fail node maintenance or scaling for the same reason.
Our teams are repairing the affected hosts and preparing a fix for the underlying component; new occurrences are possible until the fix is deployed. If one of your servers shows this behaviour, a stop/start does not restore connectivity; please contact our support with the server ID.
Servers that have not been created, restarted or migrated since 22 October 2026 are not affected. Managed Kubernetes node pools can fail node maintenance or scaling for the same reason.
Our teams are repairing the affected hosts and preparing a fix for the underlying component; new occurrences are possible until the fix is deployed. If one of your servers shows this behaviour, a stop/start does not restore connectivity; please contact our support with the server ID.
This incident affects: Location DE/TXL (Compute, Managed Kubernetes), Location DE/FRA (Compute, Managed Kubernetes), Location DE/FKB (Compute, Managed Kubernetes), Location GB/LHR (Compute, Managed Kubernetes), Location US/EWR (Compute, Managed Kubernetes), Location US/LAS (Compute, Managed Kubernetes), Location ES/VIT (Compute, Managed Kubernetes), Location FR/PAR (Compute, Managed Kubernetes), Location US/MCI (Compute, Managed Kubernetes), Location GB/BHX (Compute, Managed Kubernetes), and Location DE/FRA/2 (Compute, Managed Kubernetes).