https://approjects-vendor-status-watch.static.hf.space/v/ionos-cloud.htmlIncidents from Ionos Cloud's public status page, polled daily.Wed, 16 Sep 2026 12:28:20 +0000https://stspg.io/yhcpwhz191tzionos-cloud:2026-09-08T23:43:26.379ZTue, 08 Sep 2026 23:43:26 +0000DBaaS service has recovered, as well. We are setting the incident into Monitoring status, while the teams are ensuring that all affected services operate normally.https://stspg.io/w55tst6ln1txionos-cloud:2026-09-08T14:15:48.715ZTue, 08 Sep 2026 14:15:48 +0000We have people available now, Support is reachable as usual.https://stspg.io/lj94bvfrkk8yionos-cloud:2026-09-04T16:53:01.153ZFri, 04 Sep 2026 16:53:01 +0000We managed to fully re-establish our service, Support is back. thank you for your patience.https://stspg.io/wnv06cj6dsm0ionos-cloud:2026-09-01T13:36:02.407ZTue, 01 Sep 2026 13:36:02 +0000This incident has been resolved.https://stspg.io/313v8jdt0dm8ionos-cloud:2026-08-31T15:35:23.659ZMon, 31 Aug 2026 15:35:23 +0000# **Preliminary Root Cause Analysis** This Root Cause Analysis is preliminary as research is still being conducted to determine the technical root cause of the incident. ## **What happened?** On August 31, 2026, between 15:00 UTC and 15:43 ITC, and again between 16:32 UTC and 16:35 UTC, customers were unable to reach IONOS Cloud's Identity and Access Management \(IAM\) service and the Data Center Designer \(DCD\), which is dependent on this service. The disruption affected direct logins, partner and reseller portal access, and associated management consoles. The total customer-facing impact lasted approximately 48 minutes across both intervals. Cloud APIs \([api.ionos.com](http://api.ionos.com)\) remained fully operational throughout the incident. The underlying application services wehttps://stspg.io/5bfcrzmykmzlionos-cloud:2026-08-26T09:53:49.200ZWed, 26 Aug 2026 09:53:49 +0000# Root Cause Analysis ## What happened? Starting approximately 19:00 UTC on 24 August 2026, customers accessing S3 Object Storage in the Frankfurt \(FRA4\) data center experienced elevated latency across all operations - uploads, downloads, metadata requests, and deletions. Intermittent HTTP 503 Service Unavailable and 404 Not Found errors were observed on object read requests. The impact was measurable for all customer which had buckets in the both affected datacenters of the region, with some customers experiencing severe degradation depending on their bucket configuration and access patterns. The incident remained in progress with high priority from 25 August through 3 September 2026. The latency issue was mitigated at approximately 13:40 UTC on 3 September 2026. ## How was this poshttps://stspg.io/3z09mypzm01jionos-cloud:2026-08-23T12:47:45.805ZSun, 23 Aug 2026 12:47:45 +0000This incident has been resolved.https://stspg.io/zdfpn8nmwyfrionos-cloud:2026-08-21T07:52:17.299ZFri, 21 Aug 2026 07:52:17 +0000This incident has been resolved.https://stspg.io/6k509qzjs90dionos-cloud:2026-08-14T14:50:50.000ZFri, 14 Aug 2026 14:50:50 +0000We managed to get back to normal capacity, so Support is back to normal availability. Thank you for the patience.https://stspg.io/w7vmxbq4yp0wionos-cloud:2026-08-14T10:51:10.546ZFri, 14 Aug 2026 10:51:10 +0000This incident has been resolved.https://stspg.io/07wzf22f2x01ionos-cloud:2026-08-13T00:49:59.000ZThu, 13 Aug 2026 00:49:59 +0000We were able to resolve this issue, it's back to normal now.https://stspg.io/wcfk0n37812rionos-cloud:2026-08-11T16:05:26.026ZTue, 11 Aug 2026 16:05:26 +0000This incident has been resolved.https://stspg.io/lf7frx7rltr6ionos-cloud:2026-08-04T10:24:31.473ZTue, 04 Aug 2026 10:24:31 +0000We are marking this incident as resolved. The measures already put into place have had the desired effect on the service and have improved performance and stability. While this incident is marked as resolved, we are continuing executing on our action plan to improve the performance and reliability of our Managed Kubernetes Control Planes. Our current focus: - Further load balancing on our Control Plane Clusters - Migration of control planes to improved infrastructurehttps://stspg.io/jzcx35pb662qionos-cloud:2026-08-04T08:20:14.167ZTue, 04 Aug 2026 08:20:14 +0000We were able to assign additional personnel and will set this status page to resolved.https://stspg.io/f975x3t3ccwmionos-cloud:2026-07-28T13:46:30.000ZTue, 28 Jul 2026 13:46:30 +0000We are marking this incident as resolved as no further abnormalities could be detected. We will share an RCA as soon as it is compiled.https://stspg.io/jqd4pvg8q3k5ionos-cloud:2026-07-25T06:27:04.561ZSat, 25 Jul 2026 06:27:04 +0000No 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.https://stspg.io/qwkfzw8y09tyionos-cloud:2026-07-24T06:51:40.324ZFri, 24 Jul 2026 06:51:40 +0000Cloud Support availability is back. Thank you for your understanding.https://stspg.io/hv2d4dl7y6qdionos-cloud:2026-07-23T10:44:26.165ZThu, 23 Jul 2026 10:44:26 +0000We 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.https://stspg.io/wq43g68kdl4wionos-cloud:2026-07-18T13:33:01.430ZSat, 18 Jul 2026 13:33:01 +0000we are marking this incident as resolved as the underlying storage issue has been resolved. We will create a follow up incident for Managed Kubernetes performance and stability issues to avoid confusion.https://stspg.io/hjc15ymvgrm5ionos-cloud:2026-07-15T10:15:02.696ZWed, 15 Jul 2026 10:15:02 +0000Phone coverage is currently normalhttps://stspg.io/njhsjsgd5wqlionos-cloud:2026-07-13T11:18:46.387ZMon, 13 Jul 2026 11:18:46 +0000This was a duplicate.https://stspg.io/p187f14ckjqzionos-cloud:2026-07-13T11:16:33.454ZMon, 13 Jul 2026 11:16:33 +0000The incident has been resolved, the VMs are back working again.https://stspg.io/tylz38855z6lionos-cloud:2026-07-09T22:16:02.859ZThu, 09 Jul 2026 22:16:02 +0000**What happened?** On July 9, 2026, the Logroño datacenter experienced a cascading power and cooling failure impacting customer workloads and services. The incident began at 21:59 CEST and required on-site manual intervention to restore service. Full power was restored at 23:05 CEST; complete service normalization concluded at 09:22 CEST on July 10. No customer data loss has been identified. **How was this possible? \(Root Cause\)** The outage was caused by a single electrical fault that triggered a cascading sequence of automated safety responses. At 21:59 CEST, a residual current device \(RCD breaker D1\) in the high-voltage control cabinet tripped. At this point, no visible outage occurred. However, the trip silently disabled the generator control system - the generators lost visibhttps://stspg.io/plt79161tg5gionos-cloud:2026-07-06T10:14:04.138ZMon, 06 Jul 2026 10:14:04 +0000This incident has been resolved. We are working on the RCA and will publish it here asaphttps://stspg.io/w0bmkc6bdyxhionos-cloud:2026-07-05T14:47:50.000ZSun, 05 Jul 2026 14:47:50 +0000This incident has been resolved. We are working on the RCA and will publish it here asaphttps://stspg.io/f4ft6txlk3d4ionos-cloud:2026-07-05T08:01:04.215ZSun, 05 Jul 2026 08:01:04 +0000The provisioning queue looks healthy again, and all services have been reactivated.https://stspg.io/6c5df54jsdl1ionos-cloud:2026-07-02T08:30:41.103ZThu, 02 Jul 2026 08:30:41 +0000Our Provisioning went back operational yesterday around 16:30 UTC. Further monitoring showed no issues anymore, so this incident was resolved.https://stspg.io/fnp7d253svq7ionos-cloud:2026-07-02T07:00:33.643ZThu, 02 Jul 2026 07:00:33 +0000Phone Support is now available againhttps://stspg.io/qlwl7yryfxgkionos-cloud:2026-06-30T21:08:11.735ZTue, 30 Jun 2026 21:08:11 +0000This incident has been resolved.https://stspg.io/d77qt9592dwsionos-cloud:2026-06-23T10:24:00.000ZTue, 23 Jun 2026 10:24:00 +0000This incident has been resolved.