IONOS Cloud had 69 outages in the last 2 years totaling 1165h 8m of downtime — averaging 2.8 incidents per month.
There were 69 IONOS Cloud outages since October 24, 2025 totaling 1165h 8m of downtime. Each is summarised below — incident details, duration, and resolution information.
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.
IONOS Cloud Support is temporarily unavailable via phone. We ask Customers and Partners to contact Cloud Support via DCD Form and Email, instead.
Phone Support is now available again
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.
We are currently investigating service degradation for Control Planes of some Kubernetes clusters in the Frankfurt region (de/fra). This could impact K8s workload changes for several customers. Our teams are working on a fix.
A fix has been implemented and we are monitoring the results.
We are marking this incident as resolved. The root cause of the service degradation affecting Kubernetes Control Planes in FRA has been identified as a DDoS attack targeting customers hosted on our infrastructure. This incident has been documented here: https://status.ionos.cloud/incidents/kknrz6284jl0 The identified bottleneck led to the observed intermittent reachability issues and increased latency between Kubernetes etcd nodes for the affected customers.
We are writing to inform you that we have been experiencing sporadic connection issues and substantial delays on packet delivery. Network technicians have started working on the occurrence immediately after detection and will isolate the problem and solve the issue as quick as possible. However, it is possible that there will be a certain degradation in connection quality affecting individual virtual resources. We will inform you as soon as the functionality has been restored.
A fix has been implemented and we are monitoring the results.
We are marking this incident as resolved. The Root Cause of the incident was a DDOS attack on customers hosted in our infrastructure. While the attack was largely successfully mitigated by our countermeasures a intermittent saturation of an affected link resulted in an increase of package loss. Our network team has evaluated the countermeasures' effectiveness and the identified bottleneck and is currently working on technical and organizational improvements to further decrease detection time for comparable events.
As documented in the updates to the recent Storage Incident in our Karlsruhe DC, several Virtual Data Centers (VDCs) are currently restricted from issuing new provisioning jobs while redundancy is being restored for affected VMs. Original Incident: https://status.ionos.cloud/incidents/p6pjqxzgkh1g With this announcement we want to increase awareness about this current limitation. Impact Scope: Only customers and VDCs impacted by the original storage incident are affected by these provisioning limitations. Symptoms: Users may encounter error code VDC-5-12 when attempting to create or modify resources. Existing Workloads: All currently running VMs remain operational We will close this announcement once redundancy, as well as provisioning functionality, is fully restored.
Redundancy has been fully restored and no limitations related to provisioning should remain.
We are aware that, starting this morning, multiple customers have received an automated email from our Accounting Team advising that their Umsatzsteuer- / VAT ID numbers could not be verified. We are currently investigating this issue, and expect to send out follow-up emails to the affected customers once we know more.
We can confirm that these emails were sent out in error. There are no customer 'to-do's / calls-to-action, and we will send out an informational update to all affected customers as soon as possible.
This incident has been resolved, and all affected customers have been contacted directly via email.
Some customers may experience connection problems to the control plane and degraded functionality of kubernetes
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We currently face outages of a high number of K8s control planes, mainly in Frankfurt. This could impact K8s workload changes for several customers. Our Teams are working on a fix.
The team identified the issue and applied a fix, control planes are back now. We keep monitoring the situation.
The incident is over, all K8s control planes were back and operational yesterday. No further issues occurred.
We are currently investigating a general problem with our Object Storage Access Key creation. Currently, all new key creations are failing, so new keys can not be used. Old working keys are not affected, they are working as usual. Please be aware that the DCD frontend doesn't always reflect the key state properly, so to request the correct key status, please use the API.
Object Storage key creation is back working, you can create new access keys now. However, we keep monitoring the behaviour.
The Object Storage key creation is fixed, so new keys can be created and used.
We are currently investigating network latency irregularities in our TXL datacenter.
Our network team is currently investigating the issue. We are seeing increased error rates on the AI Modelhub and including the service as potentially affected.
Our Network Team has identified the likely cause of the performance degradation and has deployed a mitigation. We are currently monitoring bandwidth and latency metrics to ensure stability.
As no further anomalies have been spotted throughout peak times, we are closing this incident. A Root Cause Analysis will be provided here, once compiled
We are currently investigating a routing issue affecting our Cloud Support telephone system. Customers might experience disconnects or calls not being routed correctly. If you are unable to reach IONOS Cloud Support via the numbers listed in the DCD or our documentation, please use the following validated line: Direct Dial: +49 30 577 00 820
We are resolving this incident as the underlying cause has been identified and fixed. We are sorry for the inconvenience caused. All our documented support numbers should now work again as expected. https://docs.ionos.com/cloud/support/general-information/contact-information
As communicated in an email notification earlier this year, we are finalizing the retirement of the legacy SYNCHRONOUS replication mode. To ensure continued stability, all remaining PostgreSQL clusters will be automatically migrated during their first scheduled maintenance window after May 4, 2026. What is changing? - Automatic Migration: Your cluster will be transitioned to ASYNCHRONOUS mode. - Impact: You will experience a brief restart during the maintenance window. While you may see improved write performance, please note that ASYNCHRONOUS mode prioritizes speed over strict data acknowledgment. Action Required for Strong Consistency If your workload requires a zero-data-loss guarantee, you must manually upgrade to STRICTLY_SYNCHRONOUS via the API no later than May 1, 2026: - Scale Replicas: Increase your cluster to 3 or more replicas. - Update API: Set the synchronization mode to STRICTLY_SYNCHRONOUS. Affected services: Database as a Service (DBaaS) Location: Global Services
Scheduled maintenance is currently in progress. We will provide updates as necessary.
We are currently investigating increased error rates for S3 buckets located in eu-central-1 Affected services: Object Storage Location: Location DE/FRA
We are continuing to investigate this issue.
Our engineering team has identified a localized resource contention issue on several storage nodes, which is resulting in increased latency for some users. Maintenance is underway across the affected storage cluster to restore optimal performance levels.
We are currently seeing error rates dropping and are monitoring the situation closely.
As error rates have dropped and no more anomalies are being observed, we are marking this incident as resolved. Our Object Storage team is preparing a Root Cause Analysis that will be published here once it is finalized
We are conducting maintenance on our provisioning engine. During the maintenance customers might see delays in provisioning. In rare cases provisioning errors can be experienced upon which requests need to be repeated. There will be no impact on existing, already provisioned resources. Affected services: Provisioning Location: Location DE/FKB, Location DE/FRA, Location DE/FRA/2, Location DE/TXL, Location ES/VIT, Location FR/PAR, Location GB/BHX, Location GB/GLO, Location GB/LHR, Location US/EWR, Location US/LAS, Location US/MCI
Scheduled maintenance is currently in progress. We will provide updates as necessary.
We have identified a networking issue affecting one specific host in FRA. Other hosts in this region remain unaffected.
Our Network Team has identified a potential issue related to a previous package update. They have deployed a mitigation. We are currently monitoring the host for further anomalies. Network connectivity on the affected host should be restored.
We are marking this incident as resolved. The root cause was inconsistencies in a database that was modified during a prior package update. A Root Cause analysis will be provided here once compiled.