IONOS Cloud Outage History

IONOS Cloud degraded · 2 active incidents View live status →

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

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

Source: https://status.ionos.cloud

Notice January 9, 2026

S3 TXL - Increased Error Count

Detected by Pingoru
Jan 09, 2026, 03:42 PM UTC
Resolved
Jan 10, 2026, 11:55 AM UTC
Duration
20h 13m
Affected: Object Storage
Timeline · 3 updates
  1. investigating Jan 09, 2026, 03:42 PM UTC

    We are currently investigating increased error rate in our TXL site

  2. monitoring Jan 09, 2026, 04:41 PM UTC

    We have traced the increased error rate to a node that ran into problems during an OS update and is being repaired. We are downgrading the impact and will resolve the incident once the work is completed.

  3. resolved Jan 10, 2026, 11:55 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 18, 2025

Kubernetes Performance Degradation

Detected by Pingoru
Dec 18, 2025, 04:51 PM UTC
Resolved
Dec 18, 2025, 07:31 PM UTC
Duration
2h 39m
Affected: Managed KubernetesManaged KubernetesManaged KubernetesManaged KubernetesManaged KubernetesManaged KubernetesManaged KubernetesManaged KubernetesManaged KubernetesManaged KubernetesManaged Kubernetes
Timeline · 4 updates
  1. investigating Dec 18, 2025, 04:51 PM UTC

    We are currently investigating degraded performance in our Kubernetes service.

  2. identified Dec 18, 2025, 05:03 PM UTC

    We have traced the issue back to a specific control plane cluster. Customers using the affected control plane cluster will currently be unable to deploy changes. Our Kubernetes Team is working towards restoring the affected cluster.

  3. monitoring Dec 18, 2025, 05:20 PM UTC

    We have restored the affected control plane cluster. We are now restarting related API servers and then monitoring the system for any anomalies before marking the incident as resolved.

  4. resolved Dec 18, 2025, 07:31 PM UTC

    We are marking this incident as resolved. All services behave normally.

Read the full incident report →

Minor December 18, 2025

Connectivity issues in TXL/FRA2

Detected by Pingoru
Dec 18, 2025, 02:30 PM UTC
Resolved
Dec 18, 2025, 03:53 PM UTC
Duration
1h 22m
Affected: NetworkNetwork
Timeline · 4 updates
  1. investigating Dec 18, 2025, 02:30 PM UTC

    We are currently investigating connectivity issues in our TXL and FRA2 datacenter.

  2. identified Dec 18, 2025, 03:08 PM UTC

    We are currently investigating a service degradation in our internal monitoring setup in TXL. We do not currently see evidence for customer facing issues in TXL, so we are making TXL as operational again for now. We are currently investigating a potential DNS issue in FRA2 and will keep you informed about it here.

  3. monitoring Dec 18, 2025, 03:28 PM UTC

    We are marking FRA2 as operational. Services that were marked as affected (IAM) report full availability again. We are investigating the incident as two separate incidents that happened at the same time. A internal monitoring system degradation in TXL with no customer facing impact, as well as a suspected DNS issue in FRA2 that temporarily affected IAM services. We consider both incidents resolved and are monitoring all involved systems for anomalies.

  4. resolved Dec 18, 2025, 03:53 PM UTC

    We are marking this incident as resolved. We will share a root cause analysis as soon as it is compiled.

Read the full incident report →

Minor December 17, 2025

Compute Service Degradation in TXL

Detected by Pingoru
Dec 17, 2025, 11:26 AM UTC
Resolved
Dec 17, 2025, 05:33 PM UTC
Duration
6h 7m
Affected: Compute
Timeline · 3 updates
  1. investigating Dec 17, 2025, 11:26 AM UTC

    We are currently investigating a service degradation for our compute service in TXL

  2. monitoring Dec 17, 2025, 11:38 AM UTC

    We have received note from our compute team that the issue has been mitigated. We are currently monitoring the situation while the investigation is ongoing.

  3. resolved Dec 17, 2025, 05:33 PM UTC

    We are marking the incident as resolved. We will provide an RCA once it is compiled.

Read the full incident report →

Major December 12, 2025

AI Model Hub

Detected by Pingoru
Dec 12, 2025, 07:27 PM UTC
Resolved
Dec 12, 2025, 10:43 PM UTC
Duration
3h 15m
Affected: AI Model Hub
Timeline · 5 updates
  1. investigating Dec 12, 2025, 07:27 PM UTC

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

  2. investigating Dec 12, 2025, 08:09 PM UTC

    Error rate has increased. Our Model Hub Team is working towards restoring normal operations.

  3. identified Dec 12, 2025, 08:24 PM UTC

    The team has identified the issue affecting the {{baseUrl}}/v1/models endpoint and is working towards a resolution. Other Hub Endpoints should be unaffected.

  4. monitoring Dec 12, 2025, 10:15 PM UTC

    The team has successfully mitigated the incident. We are currently monitoring latency to ensure that the service is fully restored.

  5. resolved Dec 12, 2025, 10:43 PM UTC

    We are marking this incident as resolved. We will publish a RCA as soon as it is compiled.

Read the full incident report →

Minor December 3, 2025

Increased error rate for Object Storage in FRA

Detected by Pingoru
Dec 03, 2025, 09:37 PM UTC
Resolved
Dec 04, 2025, 12:50 AM UTC
Duration
3h 13m
Affected: Object Storage
Timeline · 3 updates
  1. investigating Dec 03, 2025, 09:37 PM UTC

    We are currently investigating increased error rates for our Object Storage in FRA

  2. identified Dec 03, 2025, 10:11 PM UTC

    We have identified a performance issue regarding the metadata engine. The team is currently evaluating mitigation strategies to reduce the error count while maintaining system stability.

  3. resolved Dec 04, 2025, 12:50 AM UTC

    Error Rate is back to baseline. We are working on permanent performance improvements

Read the full incident report →

Minor November 27, 2025

Increased Error Count for S3 in FRA, TXL

Detected by Pingoru
Nov 27, 2025, 08:08 PM UTC
Resolved
Nov 28, 2025, 10:09 AM UTC
Duration
14h
Affected: Object StorageObject Storage
Timeline · 4 updates
  1. investigating Nov 27, 2025, 08:08 PM UTC

    We are currently investigating increased error count in two datacenters.

  2. identified Nov 27, 2025, 08:39 PM UTC

    Our Storage Team is currently working towards stabilizing the service in both data centers. Error rate in TXL has dropped.

  3. monitoring Nov 27, 2025, 09:30 PM UTC

    The Object Storage team has identified a likely culprit for the increased error rate and has restarted the service. We are currently monitoring the error rate in both data centers

  4. resolved Nov 28, 2025, 10:09 AM UTC

    We consider the incident resolved. The error rate has stayed at baseline levels over the last few hours. We will publish a Root Cause Analysis once it is completed.

Read the full incident report →

Minor November 27, 2025

Increased error rate in S3 FRA

Detected by Pingoru
Nov 27, 2025, 11:11 AM UTC
Resolved
Nov 27, 2025, 02:23 PM UTC
Duration
3h 11m
Affected: Object Storage
Timeline · 4 updates
  1. investigating Nov 27, 2025, 11:11 AM UTC

    We are currently investigating an increase in error rates for our S3 Service in FRA

  2. identified Nov 27, 2025, 11:33 AM UTC

    Issue traced to a faulty S3 node. Mitigation is currently in progress.

  3. monitoring Nov 27, 2025, 11:50 AM UTC

    We are seeing dropping error rates and believe that the migration worked. We will monitor the situation to ensure stable service.

  4. resolved Nov 27, 2025, 02:23 PM UTC

    This incident has been resolved. We will publish a Root Cause Analysis (RCA) once our internal investigation is complete.

Read the full incident report →

Minor November 24, 2025

S3 High Error Rate

Detected by Pingoru
Nov 24, 2025, 11:52 AM UTC
Resolved
Nov 24, 2025, 06:35 PM UTC
Duration
6h 42m
Affected: Object Storage
Timeline · 3 updates
  1. investigating Nov 24, 2025, 11:52 AM UTC

    We are investigating a potential issue in our S3 Object Storage

  2. monitoring Nov 24, 2025, 12:02 PM UTC

    We identified a single node experiencing degraded performance caused by a disk hardware issue. Mitigation steps have been applied. We are currently monitoring the environment to ensure all performance metrics return to expected levels.

  3. resolved Nov 24, 2025, 06:35 PM UTC

    Error rates remained low and are now below baseline. We mark this incident resolved. While the root cause - a disk failure - was addressed quickly, high concurrent traffic delayed the return to baseline error rates. We maintained an extended monitoring period to ensure full stability. We are also confident that our upcoming S3 service improvements will significantly mitigate prolonged recovery times in similar future incidents.

Read the full incident report →

Minor November 19, 2025

Power Incident in ES/VIT

Detected by Pingoru
Nov 19, 2025, 07:10 PM UTC
Resolved
Nov 19, 2025, 07:18 PM UTC
Duration
8m
Affected: ComputeCubesStorageNetworkManaged KubernetesSupporting ServicesProvisioningObject StorageLogging Service
Timeline · 3 updates
  1. investigating Nov 19, 2025, 07:10 PM UTC

    Our ES/VIT location is currently experiencing a power outage. We will keep you updated.

  2. investigating Nov 19, 2025, 07:15 PM UTC

    Our infrastructure team in Spain has reported a power outage. We are currently validating whether there is customer facing impact. We will publish another update at 19:45 UTC latest, or as soon as new information is available.

  3. resolved Nov 19, 2025, 07:18 PM UTC

    We received note from the responding team that there is no customer impact. All components operate normally. We are resolving this incident.

Read the full incident report →

Minor November 18, 2025

Storage Service Degradation FRA

Detected by Pingoru
Nov 18, 2025, 07:54 AM UTC
Resolved
Nov 18, 2025, 02:09 PM UTC
Duration
6h 15m
Affected: ComputeStorageNetwork
Timeline · 4 updates
  1. investigating Nov 18, 2025, 07:54 AM UTC

    We are currently investigating further degradations in the performance. This may be related to an incident earlier in the night. We will provide all of our customers with regular updates.

  2. identified Nov 18, 2025, 08:58 AM UTC

    Our team is currently assessing the situation. While most customers are seeing performance return to nominal levels, we are still seeing some sporadic performance degradation. We will continue to update all of our customers as our teams work to resolved all issues as fast as possible

  3. monitoring Nov 18, 2025, 10:59 AM UTC

    Performance should be back to normal for all or most customers. Our team is currently working on an RCA, which we will publish here as soon as that is available.

  4. resolved Nov 18, 2025, 02:09 PM UTC

    All services are reporting normal. RCA to follow.

Read the full incident report →

Minor November 17, 2025

S3 High Latency in eu-central-3

Detected by Pingoru
Nov 17, 2025, 01:59 PM UTC
Resolved
Nov 17, 2025, 07:20 PM UTC
Duration
5h 20m
Affected: Object Storage
Timeline · 5 updates
  1. investigating Nov 17, 2025, 01:59 PM UTC

    We are currently investigating high latency for S3 Object Storage

  2. investigating Nov 17, 2025, 02:25 PM UTC

    We are currently investigating error rates above baseline in our S3 Object storage in our TXL (eu-central-3) location. Since the start of the incident, the error rate has dropped, but is still above threshold. We will update the status page every 30 minutes or when new important information becomes available. You can expect the next update at 15:00 UTC. Thank you for your patience as the team works towards a quick resolution.

  3. identified Nov 17, 2025, 02:59 PM UTC

    We have identified abnormal load levels for some buckets and are currently deploying mitigations to reduce the impact further.

  4. monitoring Nov 17, 2025, 03:17 PM UTC

    We have deployed mitigations and are currently monitoring the development of latency and error rate.

  5. resolved Nov 17, 2025, 07:20 PM UTC

    The performance and latency have been at acceptable levels. We will mark this incident as resolved. We will provide a Root Cause Analysis here once the investigation is completed.

Read the full incident report →

Minor November 6, 2025

Increased Error Rate on S3 Cloudian

Detected by Pingoru
Nov 06, 2025, 11:14 AM UTC
Resolved
Nov 10, 2025, 04:48 PM UTC
Duration
4d 5h
Affected: Object Storage
Timeline · 3 updates
  1. investigating Nov 06, 2025, 11:14 AM UTC

    We are currently investigating an increased error rate for requests to S3 Cloudian in DE/FRA.

  2. monitoring Nov 06, 2025, 12:14 PM UTC

    Error rate has dropped. We are closely monitoring the situation. We are compiling a root cause analysis.

  3. resolved Nov 10, 2025, 04:48 PM UTC

    We want to share the following Root Cause Analysis: What happened: On the 6th of November, our Monitoring Team alerted us to increased error rates for requests to S3 Cloudian in DE/FRA. The increased error rate was caused by a network-level issue related to MTU settings lower than standard, causing intermittent issues for some connections. What we are doing to prevent this from happening again: On 11.11.2025, a fix will be rolled out to the affected network, which will correct the MTU settings permanently.

Read the full incident report →

Minor November 1, 2025

DCD Intermittent Login Issues

Detected by Pingoru
Nov 01, 2025, 09:36 AM UTC
Resolved
Nov 01, 2025, 10:05 AM UTC
Duration
29m
Affected: Data Center Designer (DCD)
Timeline · 2 updates
  1. investigating Nov 01, 2025, 09:36 AM UTC

    We are currently investigating intermittent login issues on the DCD. Users may see the following message when attempting to log in: “Your login attempt timed out. Login will start from the beginning.” We will update this status page regularly as we continue our investigation.

  2. resolved Nov 01, 2025, 10:05 AM UTC

    We have identified an issue related to the synchronization behavior of our authentication platform that was caused by maintenance performed on the underlying managed Kubernetes system. This issue is now resolved. A permanent solution that ensures proper synchronization behavior during and after maintenance has been identified and will be implemented during the course of next week.

Read the full incident report →