IONOS Cloud Outage History

We see indications of a recurrence of the issue and are setting the status page to active. Our Network Team is investigating and we will share updates here as they become available. The issue is currently negatively affecting Compute, Provisioning and Network Components.

We are continuing to work on a fix for this issue.

Our Network Team has identified an issue related to a recent router replacement and applied a mitigation. Compute and Storage systems are showing signs of recovery. We are actively monitoring the environment until all services are fully restored

We are currently investigating potential residual impact on DBaaS Services. Compute and Block Storage have reported full recovery.

While phone support will generally be available, our Support capacity is reduced due to multiple cases of sick leave. We want to inform you that our phone support will be limited during the following time slots, leading to increased response times on the phone channel. In these cases, please reach out per email. Thank you.

For our partners with subcontracts: We found that subcontracts cannot access the new Frankfurt location "de/fra/1". We are currently working on a fix to make this available, we will keep you informed when it's done.

The issue has been identified and a fix is being implemented.

IONOS Cloud Support is temporarily unavailable via phone. We ask Customers and Partners to contact Cloud Support via the DCD Form or Email, instead.

The situation is still unchanged, so best would be to please reach out via email.

We are currently reports of error VDC-14-1836 during provisioning operations. Our provisioning team is informed and is preparing a hotfix.

We have identified a likely culprit. The Provisioning Team has implemented a mitigation. We see the performance of the service stabilizing.

We are still seeing residual 500 errors from the Cloud API and are working towards resolving the remaining service degradation.

IONOS Cloud Support is temporarily not always available via phone. We ask Customers and Partners to contact Cloud Support via the DCD Form or Email, instead.

We have identified an issue with DNS. Our DBaaS Team is currently analyzing the service. A potential culprit has been identified. We will provide another update here latest 14:15

While phone support will generally be available, our capacity is reduced due to multiple cases of sick leave. We want to inform you that our phone support will be limited during the following time slots, leading to increased response times on the phone channel. 15.07.2026: 21:00 – 05:00 UTC 16.07.2026: 21:00 – 05:00 UTC If possible, we ask that you submit tickets using the DCD Form or via email. Thank you for your understanding!

Our teams identified some affected hardware servers that caused the unavailability. We are now in process of migrating the affected VMs to different HW servers, so please check your VMs. We are still working on the root cause investigation.

We are currently investigating instances of performance degradation in job processing. Our Provisioning Team is currently working on fixing the root cause of these events.

Still, the global provisioning system is not working properly. Therefore, all other dependencies, like K8s and managed products, are affected, too. We know this is affecting customer setups, and that urgent changes are not processed properly, and we apologize for the inconvenience. We identified possible distractors, but fixing this is a complex task, with need to involve and coordinate several technical teams. We are working with highest prio to get the provisioning back working, and we will let you know asap on any progress.

Customers may experience connection problems to the control plane and degraded functionality of kubernetes, this incident affected: - APIs and Frontends (Data Center Designer (DCD)), - Location FR/PAR (Managed Kubernetes, Provisioning), - Location US/MCI (Managed Kubernetes, Provisioning), - Location DE/TXL (Managed Kubernetes, Provisioning), - Location DE/FRA (Managed Kubernetes, Provisioning), - Location DE/FKB (Managed Kubernetes, Provisioning), - Location GB/LHR (Managed Kubernetes, Provisioning), - Location US/EWR (Managed Kubernetes, Provisioning), - Location US/LAS (Managed Kubernetes, Provisioning), - Location ES/VIT (Managed Kubernetes, Provisioning), - Location GB/BHX (Managed Kubernetes, Provisioning), - Location DE/FRA/2 (Managed Kubernetes, Provisioning).

We are continuing to work on a fix for this issue.

We found the root cause and implemented mitigation measures. We expect the errors to decrease significantly now. We will let you know asap when we consider the situation being back to normal.