IONOS Cloud Outage History

We have identified the source of the issue. Our Compute and MK8s Team have responded and are working on mitigation. We will keep this status page updated. We aim to publish the next update within 30 mins, or when we can share a significant update.

We are currently experiencing intermittent issues with our phone system, which may prevent our agents from connecting to incoming calls. We are actively working with our vendor to resolve this as quickly as possible. If you are unable to reach the team by phone, please open a ticket via email or the DCD Support form.

We have identified the source of the issue. Our Compute and MK8s Team have responded and are working on mitigation. We will keep this status page updated. We aim to publish the next update within 30 mins, or when we can share a significant update.

Mitigation is still progressing. We expect completion within next 30-45 minutes.

There may be periods of increased waiting times when calling IONOS Cloud Support by phone. We ask Customers and Partners to contact Cloud Support via the DCD Form or Email, instead. Thank you.

The AI Model Hub API is currently unavailable. We are working on restoring the service.

Customers may experience connection problems to the control plane and degraded functionality of kubernetes

Our engineering team has identified the root cause of the Kubernetes service degradation and is actively working to restore full functionality. Customer workloads in affected locations may be experiencing disruptions, including unavailability of running services. Cluster management operations -- deploying, scaling, and accessing the Kubernetes API -- are also impacted. We will provide another update within 60 minutes.

Our engineering team has identified the root cause of the Kubernetes service degradation and is actively working to restore full functionality. Customer workloads in affected locations may be experiencing disruptions, including unavailability of running services. Cluster management operations -- deploying, scaling, and accessing the Kubernetes API -- are also impacted. We will provide another update within 30 minutes.

We have successfully identified and mitigated a high-latency condition in our core storage infrastructure that temporarily impacted the responsiveness of the Kubernetes control plane. Our engineering team is currently executing a phased reconciliation and rollout process to gracefully restart the management instances and restore full functionality. Existing application workloads continue to run normally and remain unaffected.

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.

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!