IONOS Cloud Outage History

IONOS Cloud degraded · 2 active incidents View live status →

IONOS Cloud had 69 outages in the last 2 years totaling 262h 19m of downtime — averaging 2.8 incidents per month.

There were 69 IONOS Cloud outages since October 24, 2025 totaling 262h 19m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.ionos.cloud

Minor April 9, 2026

AI Modelhub: Performance Degradation

Detected by Pingoru
Apr 09, 2026, 06:28 AM UTC
Resolved
Apr 09, 2026, 03:46 PM UTC
Duration
9h 17m
Affected: AI Model Hub
Timeline · 3 updates
  1. investigating Apr 09, 2026, 06:28 AM UTC

    We are experiencing increased traffic volumes for specific models, including GPT-OSS 120B, which is currently causing capacity constraints. Users may encounter longer response times or intermittent timeouts. Our AI Modelhub Team is actively working to scale capacity and resolve these issues

  2. identified Apr 09, 2026, 10:06 AM UTC

    Our AI Model hub Team has identified a likely culprit for the increased load. The team is working towards increasing capacity to ensure that GPT-OSS 120B stays available for all customers. Customers may still experience intermittent timeouts.

  3. resolved Apr 09, 2026, 03:46 PM UTC

    Response times of the model have improved significantly. We are marking the incident as resolved.

Read the full incident report →

Minor March 31, 2026

Managed Kubernetes: Service Degradation for Control Planes in FRA

Detected by Pingoru
Mar 31, 2026, 12:22 PM UTC
Resolved
Apr 01, 2026, 08:18 PM UTC
Duration
1d 7h
Affected: Managed Kubernetes
Timeline · 3 updates
  1. investigating Mar 31, 2026, 12:22 PM UTC

    We are currently investigating service degradation for Control Planes of some Kubernetes clusters in the FRA DC.

  2. monitoring Mar 31, 2026, 01:10 PM UTC

    All affected Control Planes have recovered. We are currently monitoring the affected clusters for further anomalies.

  3. resolved Apr 01, 2026, 08:18 PM UTC

    We are marking the incident as resolved, as no further anomalies were detected. The root cause was a transient latency issue in one of the redundant CoreDNS pods, which led to kube-apiservers being unable to discover etcd instances in time. We are currently developing better mitigation options for the excessive NXDOMAIN requests observed during the incident.

Read the full incident report →

Minor March 25, 2026

Availability of API and DCD limited

Detected by Pingoru
Mar 25, 2026, 12:43 AM UTC
Resolved
Mar 25, 2026, 11:10 AM UTC
Duration
10h 27m
Affected: Data Center Designer (DCD)Cloud APIBilling APIReseller API
Timeline · 3 updates
  1. investigating Mar 25, 2026, 12:43 AM UTC

    We are currently investigating limitations in the availability of the Cloud-API and the data center designer (DCD). We will provide further information as soon as possible.

  2. monitoring Mar 25, 2026, 03:00 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Mar 25, 2026, 11:10 AM UTC

    This incident is resolved. We will publish a root cause analysis once it is compiled.

Read the full incident report →

Minor March 16, 2026

AI Model Hub - Increased Error Rate in Embeddings

Detected by Pingoru
Mar 16, 2026, 08:28 AM UTC
Resolved
Mar 16, 2026, 11:08 AM UTC
Duration
2h 40m
Affected: AI Model Hub
Timeline · 3 updates
  1. investigating Mar 16, 2026, 08:28 AM UTC

    Our AI Model Hub Team is currently investigating increased error rates in the Embeddings functionality in the AI Model Hub.

  2. identified Mar 16, 2026, 10:01 AM UTC

    The team has traced the root cause to the ongoing Kubernetes incident (link). Both teams are currently working to restore service. (https://status.ionos.cloud/incidents/h9x5s66m4r28)

  3. resolved Mar 16, 2026, 11:08 AM UTC

    To improve visibility and streamline communication, we are merging this incident into the MK8s incident (tracked here: https://status.ionos.cloud/incidents/h9x5s66m4r28). Consequently, we will close this specific entry and provide all future updates via the referenced incident link.

Read the full incident report →

Minor February 26, 2026

Acronis Backup Service: Cloud Storage Access issues

Detected by Pingoru
Feb 26, 2026, 07:56 PM UTC
Resolved
Feb 27, 2026, 08:25 AM UTC
Duration
12h 29m
Affected: Backup Service
Timeline · 2 updates
  1. investigating Feb 26, 2026, 07:56 PM UTC

    We are currently investigating issues related to Acronis Backup Service. Error message: Failed to connect because access to the cloud storage was denied.

  2. resolved Feb 27, 2026, 08:25 AM UTC

    This incident is now closed. Analysis shows that a configuration change to Acronis Backup on 25.02 briefly affected connectivity, leading to delayed reporting from customers. The change was rolled back shortly after maintenance, resolving the issue.

Read the full incident report →

Minor February 6, 2026

IAM Service - Increased Error Rate

Detected by Pingoru
Feb 06, 2026, 11:41 AM UTC
Resolved
Feb 06, 2026, 04:43 PM UTC
Duration
5h 2m
Affected: Data Center Designer (DCD)
Timeline · 3 updates
  1. investigating Feb 06, 2026, 11:41 AM UTC

    We are currently investigating increased error rates in our IAM Service. We will update this incident shortly with more information

  2. monitoring Feb 06, 2026, 11:46 AM UTC

    The root cause could be identified quickly and the Infrastructure team reports that the issue should be resolved. We are monitoring the situation and will then resolve the incident.

  3. resolved Feb 06, 2026, 04:43 PM UTC

    We marking this incident as fully resolved

Read the full incident report →

Major February 4, 2026

AI Model Hub - Increased error rate

Detected by Pingoru
Feb 04, 2026, 06:12 PM UTC
Resolved
Feb 05, 2026, 07:53 AM UTC
Duration
13h 41m
Affected: AI Model Hub
Timeline · 3 updates
  1. investigating Feb 04, 2026, 06:12 PM UTC

    We are currently investigating an increase in error rate for our AI Model Hub

  2. monitoring Feb 04, 2026, 06:52 PM UTC

    We are seeing that error rate is dropping and are downgrading the incident. We are actively monitoring the situation further.

  3. resolved Feb 05, 2026, 07:53 AM UTC

    We are marking this incident as resolved as the metrics remained stable.

Read the full incident report →

Minor February 4, 2026

Provisioning service access limited

Detected by Pingoru
Feb 04, 2026, 11:13 AM UTC
Resolved
Feb 04, 2026, 03:30 PM UTC
Duration
4h 16m
Affected: Data Center Designer (DCD)Cloud API
Timeline · 3 updates
  1. investigating Feb 04, 2026, 11:13 AM UTC

    There is currently an increased processing time for provisioning requests initiated via the Data Center Designer or the API. The availability and accessibility of your virtual datacenter resources will remain unaffected.

  2. monitoring Feb 04, 2026, 12:43 PM UTC

    Processing time for provisioning requests has returned to normal. The service is currently being monitored

  3. resolved Feb 04, 2026, 03:30 PM UTC

    This incident has been resolved.

Read the full incident report →

Major February 3, 2026

Service Disruption: Billing API

Detected by Pingoru
Feb 03, 2026, 11:38 AM UTC
Resolved
Feb 05, 2026, 05:49 PM UTC
Duration
2d 6h
Affected: Billing API
Timeline · 2 updates
  1. identified Feb 03, 2026, 11:38 AM UTC

    A technical issue affecting invoice generation has been identified. We are currently implementing a resolution to restore service to the invoice endpoint. Access to these records is temporarily suspended.

  2. resolved Feb 05, 2026, 05:49 PM UTC

    We have received an update from our Billing team. The API is fully operational again and we are marking this incident as resolved.

Read the full incident report →

Minor January 30, 2026

Intermittent Issues with IONOS Cloud Telephon Support

Detected by Pingoru
Jan 30, 2026, 09:56 AM UTC
Resolved
Jan 30, 2026, 12:53 PM UTC
Duration
2h 57m
Affected: Cloud Support
Timeline · 3 updates
  1. investigating Jan 30, 2026, 09:56 AM UTC

    We are currently investigating intermittent issues with IONOS Cloud Support Telephone Line. While mostly outgoing calls are affected, we ask customers to use [email protected] if the team cannot be reached correctly via phone.

  2. monitoring Jan 30, 2026, 12:42 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jan 30, 2026, 12:53 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 29, 2026

AI Model Hub Service Degradation and Increased Error Rate

Detected by Pingoru
Jan 29, 2026, 11:40 AM UTC
Resolved
Jan 29, 2026, 05:10 PM UTC
Duration
5h 30m
Affected: AI Model Hub
Timeline · 3 updates
  1. investigating Jan 29, 2026, 11:40 AM UTC

    We are currently investigating increased error rate in our AI Model Hub.

  2. monitoring Jan 29, 2026, 01:00 PM UTC

    The team has successfully mitigated the incident. We are actively monitoring the service to ensure its full restoration.

  3. resolved Jan 29, 2026, 05:10 PM UTC

    Our AI Model Hub experienced a temporary degradation, resulting in an increase in 5xx errors when interacting with the service. The issue was identified as a spike in memory usage in the API components. Our teams implemented mitigation measures to stabilize the load, and the service has been fully restored. The incident is now considered resolved.

Read the full incident report →

Minor January 27, 2026

Object Storage Service Restrictions

Detected by Pingoru
Jan 27, 2026, 09:39 AM UTC
Resolved
Jan 27, 2026, 10:48 AM UTC
Duration
1h 9m
Affected: Object Storage
Timeline · 3 updates
  1. investigating Jan 27, 2026, 09:39 AM UTC

    We are currently investigating an increased number of upload and download errors in the use of our Object Storage at the Berlin site. It mainly affects user-owned buckets. Teams are working on it, we will keep you informed.

  2. monitoring Jan 27, 2026, 10:00 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jan 27, 2026, 10:48 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 23, 2026

S3: Increased Error Rates in TXL

Detected by Pingoru
Jan 23, 2026, 09:49 PM UTC
Resolved
Jan 24, 2026, 01:52 AM UTC
Duration
4h 2m
Affected: Object Storage
Timeline · 3 updates
  1. investigating Jan 23, 2026, 09:49 PM UTC

    We have registered an increase in error rate for our S3 service in TXL

  2. monitoring Jan 23, 2026, 11:08 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jan 24, 2026, 01:52 AM UTC

    This incident has been resolved.

Read the full incident report →

Major January 17, 2026

Provisioning Service Disruption in Las Vegas DC

Detected by Pingoru
Jan 17, 2026, 07:13 PM UTC
Resolved
Jan 18, 2026, 10:11 PM UTC
Duration
1d 2h
Affected: Provisioning
Timeline · 3 updates
  1. investigating Jan 17, 2026, 07:13 PM UTC

    Summary: We have identified a physical hardware failure within our firewall cluster at the Las Vegas data center. Impact: All provisioning jobs for new and existing Cloud instances in this region are currently failing. Please note that existing, active instances are not affected by this issue and operate normally. Current Status: Our team is on-site installing replacement hardware. We anticipate a delay in full restoration and will provide an updated ETA as soon as possible.

  2. monitoring Jan 17, 2026, 10:48 PM UTC

    A fix has been implemented on the affected physical device and normal provisioning services are back to running.

  3. resolved Jan 18, 2026, 10:11 PM UTC

    After extensive monitoring of final fix, continued stability has been restored

Read the full incident report →

Minor January 13, 2026

IPV6 issue in TXL

Detected by Pingoru
Jan 13, 2026, 03:37 PM UTC
Resolved
Jan 13, 2026, 05:16 PM UTC
Duration
1h 39m
Affected: Network
Timeline · 2 updates
  1. investigating Jan 13, 2026, 03:37 PM UTC

    The network team is currently investigating an issue with IPV6 addressing in TXL

  2. resolved Jan 13, 2026, 05:16 PM UTC

    The Degradation In IPV6 Addressing is now resolved.

Read the full incident report →