IONOS Cloud had 85 outages in the last 2 years totaling 1167h 4m of downtime — averaging 3.5 incidents per month.
There were 85 IONOS Cloud outages since October 24, 2025 totaling 1167h 4m of downtime. Each is summarised below — incident details, duration, and resolution information.
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 were able to assign additional personnel and will set this status page to resolved.
We are currently investigating a connectivity issue impacting our DBaaS (MongoDB) services. Our team is working to resolve the problem, and we will update you as soon as full functionality has been restored.
We are continuing to investigate this issue.
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
The DBaaS Team has performed a rollback of a change deployed prior that updated DNS services. We are seeing services recovering. We are monitoring the situation closely.
We are marking this incident as resolved as no further abnormalities could be detected. We will share an RCA as soon as it is compiled.
We are investigating alerts related to loss of redundancy on storage servers. There is currently no customer impact, our storage team is investigating and working to restore redundancy. We are suspecting a faulty networking component.
We have found a likely root cause. A management component was causing excessive memory consumption introducing instability on the affected storage servers. This has been mitigated. We are currently monitoring the environment and will close the incident if no further anomalies are observed.
No more anomalies were detected. The Root Cause of the loss of redundancy was identified as a memory leak in a management component. A durable mitigation was put in place to avoid recurrence. The memory leak will be addressed in an upcoming update to the management component.
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. In these cases, please reach out per email. Thank you.
Cloud Support availability is back. Thank you for your understanding.
We are currently investigating increased AI Model Hub error rates and latencies. More details will be shared as they become available. Affected services: AI Model Hub Location: Global Services
A fix has been implemented, which has reduced the number of 4xx and 5xx responses to nominal levels. We will continue to monitoring the results.
We are marking this incident as resolved. Our AI Modelhub Team has addressed the issue, which was caused by acute resource constraints. This was resolved by scaling out the bottlenecks.
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!
Phone coverage is currently normal
We are currently investigating problems accessing VMs and DBaaS service located in Frankfurt. We will inform you as soon as the functionality has been restored.
This was a duplicate.
We are currently experiencing an issue where resources in the FRA region are unreachable and showing an Unknown state. This issue is currently being investigated and we will keep you informed of any updates.
We are continuing to investigate this issue.
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.
Our tech teams were able to restore all VMs and products, so all are back available and running. However, we keep monitoring the situation for a while.
The incident has been resolved, the VMs are back working again.
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.
Our Provisioning Team has been closely tracking queue performance over the last few hours and has noted steady improvements. We are moving this incident to Monitoring status. We will continue to monitor queue processing closely and will update this page on any changes.
This incident has been resolved. We are working on the RCA and will publish it here asap
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.
A fix has been implemented and we are monitoring the results.
This incident has been resolved. We are working on the RCA and will publish it here asap
Currently we are facing increased provisioning problems resulting in error code [VDC-5-0]. We understand the impact, and our teams are investigating the root cause to get this fixed asap. Please postpone your provisioning until we resolve the issue, we will inform you of any updates.
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.
Our Provisioning went back operational yesterday around 16:30 UTC. Further monitoring showed no issues anymore, so this incident was resolved.
IONOS Cloud Support is temporarily unavailable via phone. We ask Customers and Partners to contact Cloud Support via the DCD Form or Email, instead.
We are continuing to investigate this issue.
Phone Support is now available again
Customers may experience connection problems to the control plane and degraded functionality of kubernetes
The situation appears to have stabilized for the time being. An internal investigation into the exact root cause is ongoing.
Incident involving degradation of the control plane has been resolved and we are monitoring the situation.
This incident has been resolved.
Due to an internal issue that is currently being investigated, the BGE-M3 model is unavailable.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the service.
This incident has been resolved.
We are currently investigating issues with the MK8s control plane
Control Planes are reachable again. Our MK8s Team is currently investigating the root cause for the service interruption.
We have observed another spike and are setting the incident back to active. Our MK8s Team is informed and are actively working the incident.
We have marked this incident as resolved. Several underlying VMs entered an unhealthy state, which increased the CPU load on the remaining healthy VMs supporting the service. This cascaded into the intermittent availability issues. All systems are now operating normally.
We are currently investigating increased error rate for S3 in our FRA DC
We are reducing the impact of the incident, as our Object Storage Team has traced back the increased error rates to mainly SlowDown codes, which affect only heavily loaded buckets.
Error rate has dropped. We are monitoring the situation further.
We are marking this incident as resolved, as no further abnormalities occurred.
We are currently experiencing a high error rate with S3 Object Storage in TXL - eu-central-3. This is currently being investigated and we will continue to keep this page updated.
The incident has now been resolved, and accessing S3 Buckets should now be working as expected.
We are currently investigating increased loading times and timeouts for the DCD.
Our DCD Team is currently investigating the incident. We have confirmed that Cloud API remains functional and available. Customers and Partners needing to deploy changes to their setup can still use ionosctl and cloudapi to do so.
We believe that the trigger for the incident has been mitigated. We are currently working on restoring all services related to the DCD.
The DCD is available again. We are monitoring the system closely and will set this incident to resolved once the environment is confirmed stable.
The system is stable. We are resolving this incident. The trigger of this incident will be shared once the analysis has been completed.
We are currently investigating increased error rate for S3 in eu-central-3
Our Object Storage Team has identified an issue connected with gateways in the affected region and is currently mitigating the problem. Customers may see connectivity issues and timeouts. We will keep you updated on the mitigation efforts.
The mitigation efforts have lead to first improvements. We have downgraded the incident severity. However, we still see elevated error rates and are working towards resolving the remaining issues.
Error rates have significantly decreased. We are monitoring the situation further and will resolve the incident if the situation stays as is.
We are closing the incident as no further error spikes were recorded. We will share the trigger of this incident once the analysis has been conducted.
Currently we face major availability problems in our Object Storage service in Frankfurt. You might encounter degraded access to your buckets and objects in de (eu-central-1). The team is investigating the issue and trying to fix it as soon as possible.
The team found the issue in a bad network setting / routing. This was fixed, so the service is back again. It happened 12:45 - 13:20 UTC today, but now all endpoints are available. We are monitoring the situation, and we will provide an analysis once the investigation was finished.
The Object Storage endpoints are stable now.
Currently, there is an increased processing time for provisioning orders that are initiated via Data Center Designer or API. Occasionally, connections may be lost in the direction of the Data Center Designer. Availability and accessibility of your virtual data center resources will remain unaffected. We will inform you as soon as the functionality has been restored.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating increased latency and error count in the AI Model Hub
We are currently experiencing significant load, which is affecting the response times of our Modelhub. Our team is working on removing performance bottlenecks.
The Mistral Small 24B Instruct model is currently experiencing a high load. For users experiencing timeouts, we recommend switching to an alternative model, such as GPT-OSS-120B. The slow response times previously observed in Collections are no longer occurring.
This incident has been resolved.
We are currently investigating a connectivity issue related to VPN Gateways
Our VPN Team has identified the issue and is currently mitigating. Affected gateways are already recovering. We are monitoring recovery progress and will update this page.
all affected Gateways have recovered. We are monitoring the behavior and will mark the incident as resolved.
We are marking this incident as resolved. Our team is currently investigating a link to a previous maintenance task on the VPN gateways. We will update the incident with the investigation results once they are available.