Managed Kubernetes - Intermittent Control Plane Unavailability
Monitoring - Memory limit adjustments have been fully rolled out across all control plane clusters and are showing positive effects. We have significantly expanded the underlying infrastructure capacity and migration of customer workloads is progressing well.
We are observing substantial improvements in control plane stability and performance. The recurring disruption patterns described in earlier updates are no longer present.
Migration work will continue throughout the day. We will provide an update once migrations are completed or if any changes in status occur.
Aug 06, 2026 - 08:04 UTC
Update - Memory limit adjustments and migration have had positive effects on the first control plane cluster. Customer situated in the first control plane cluster should already see substantial improvements in performance and stability.

We have started to roll out memory adjustments in the remaining control plane cluster, as well. Rolling out the memory limits can lead to temporary unavailability of affected control planes. These interruptions should be brief and will not affect running workloads.

After memory limit adjustments are fully rolled out on the second control plane cluster, horizontal scaling and migrations will resume on both control plane clusters for the next hours until workload is distributed optimally.
Aug 05, 2026 - 20:43 UTC
Update - Migration has been picked up again. We already see encouraging results after completion of first batches. In the next hours we focus on completing the migration and horizontal scaling.
During the migration, single etcds can be temporarily unavailable for time periods lasting around 30 seconds.
We expect further performance and stability improvements for all customers during and after the migration.
Aug 05, 2026 - 10:07 UTC
Identified - Migration of the first batches has been completed. The Kubernetes Team has identified a remaining issue preventing further migration. We are setting this incident back to active until the issue is resolved and the migration completed.
Aug 05, 2026 - 06:23 UTC
Monitoring - Memory adjustments have been rolled out and show positive effects.
We are starting the migrations planned to further improve control plane performance for all our customers.
We estimate that the migration will be completed in the next hours.
Control Plane performance is expected to improve already during the migration.

We are setting this incident into Monitoring status and will provide an update once the migration is completed.
Aug 04, 2026 - 21:11 UTC
Update - Our plans for further horizontal scaling of the control plane are progressing. We expect to be able to do a dry run and further testing within the next hours, before we proceed with migrations.
We aim to finish work on horizontal scaling until EOD.
We are rolling out memory configuration improvements in parallel.
Aug 04, 2026 - 16:23 UTC
Update - We are currently rolling out memory scaling measures to address recurring stability issues during compaction operations on the affected etcd clusters. Additionally, we are planning to roll out further horizontal scaling for the affected clusters today.

We will provide another update once these measures have been applied and we can assess their impact.
Aug 04, 2026 - 14:37 UTC
Update - During a service rollout today, a subset of control planes experienced temporary restarts. Affected customers may notice brief API unavailability while these control planes recover. The team is monitoring the recovery.

Separately, work on improving infrastructure capacity and load distribution continues as described in our initial update.

We will post another update once the affected control planes have fully stabilized.
Aug 04, 2026 - 13:14 UTC
Identified - We are aware of intermittent control plane unavailability affecting a subset of Managed Kubernetes customers. Affected customers may experience API call failures, deployment timeouts, and temporary disruption of cluster management operations.

Our engineering team is actively working on both immediate mitigations and longer-term architectural improvements.

Several mitigations have already been deployed, including maintenance schedule optimization, compaction regression fixes, and storage performance improvements. Additional measures - including infrastructure migration, dedicated event etcd clusters, improved load balancing, and horizontal scaling - are in progress.

We are providing regular updates on this page. Customers experiencing issues are encouraged to subscribe to this incident for timely notifications.
Aug 04, 2026 - 10:24 UTC
Managed Kubernetes - Automated Maintenance disabled
Identified - We were able to reactivate the MK8s maintenances in all clusters in our TXL datacenter
Jun 23, 2026 - 08:21 UTC
Investigating - Due to exceptionally high demand in two clusters in our TXL and FRA datacenters, we have temporarily paused Managed Kubernetes Automated Maintenance.

To ensure that clusters remain operational without interruption during updates, Automated Maintenance requires temporary cluster "cloning", which increases resource consumption. As most maintenance windows are scheduled to run over the weekend, resource demand peaks sharply during these periods.

To protect cluster stability and prevent service degradation, we have paused maintenance for the affected clusters. Any maintenance scheduled from today onward will not run until we resume.

We know automated Kubernetes maintenance is an important feature of our platform, and we did not take this decision lightly. We are expanding capacity in the affected clusters as a high priority and will update this page as soon as maintenance resumes.
Jun 22, 2026 - 19:07 UTC
GPU Server Provisioning: Supply currently limited
Identified - We are currently experiencing exceptionally high demand for GPU servers, which has temporarily limited our available capacity. As a result, you may encounter provisioning errors when attempting to create a new GPU server or start an existing one.

What You Can Do

- Try again later: We cannot provide an exact timeline for when capacity will be added. However, we are monitoring the situation closely and will update this status page once substantial free capacity becomes available.
- Provision a smaller GPU server: Because availability fluctuates rapidly, we cannot guarantee which specific sizes are currently open. Attempting to provision a smaller instance may increase your chances of success.
- If you currently have a provisioned and running GPU server, do not shut it down. Due to the low supply, freed resources may be immediately allocated to other customers, and you will likely be unable to restart your server.

Next Steps & Resolution
Resolving this resource constraint has high priority. Our teams are working to increase capacity to meet demand as quickly as possible.

We sincerely appreciate your patience and understanding.
Jun 18, 2026 - 15:04 UTC
Provisioning of MongoDB Playground and Business Edition Clusters unavailable
Investigating - MongoDB Playground and Business Edition clusters are currently not available for provisioning in de/fra/2 (Frankfurt East). This is due to a capacity limitation in that location that prevents these cluster types from being created reliably, and it is expected to persist for the time being. We will update this status page as soon as this limitation is lifted.

As an alternative, you can:
- Provision your Playground or Business Edition cluster in another available location, or
- Use MongoDB Enterprise Edition, which remains available in Frankfurt East.
Jun 12, 2026 - 15:46 UTC
Cloud Support Operational
Location DE/FKB Operational
Compute Operational
Storage Operational
Network Operational
Managed Kubernetes Operational
Supporting Services Operational
Provisioning Operational
Private Cloud Operational
Logging Service Operational
Monitoring Service Operational
Location DE/FRA Operational
Compute Operational
Cubes Operational
Storage Operational
Network Operational
Managed Kubernetes Operational
Supporting Services Operational
Provisioning Operational
Object Storage Operational
Logging Service Operational
Monitoring Service Operational
Location DE/FRA/2 Operational
Compute Operational
Cubes Operational
Storage Operational
Network Operational
Managed Kubernetes Operational
Supporting Services Operational
Provisioning Operational
Object Storage Operational
Logging Service Operational
Monitoring Service Operational
Location DE/TXL Operational
Compute Operational
Cubes Operational
Storage Operational
Network Operational
Managed Kubernetes Operational
Supporting Services Operational
Provisioning Operational
Object Storage Operational
Private Cloud Operational
Logging Service Operational
Monitoring Service Operational
Location ES/VIT Operational
Compute Operational
Cubes Operational
Storage Operational
Network Operational
Managed Kubernetes Operational
Supporting Services Operational
Provisioning Operational
Object Storage Operational
Logging Service Operational
Monitoring Service Operational
Location FR/PAR Operational
Compute Operational
Storage Operational
Cubes Operational
Managed Kubernetes Operational
Provisioning Operational
Supporting Services Operational
Network Operational
Logging Service Operational
Monitoring Service Operational
Location GB/BHX Operational
Compute Operational
Cubes Operational
Storage Operational
Network Operational
Managed Kubernetes Operational
Supporting Services Operational
Provisioning Operational
Logging Service Operational
Monitoring Service Operational
Location GB/GLO Operational
Private Cloud Operational
Location GB/LHR Operational
Compute Operational
Cubes Operational
Storage Operational
Network Operational
Managed Kubernetes Operational
Supporting Services Operational
Provisioning Operational
Logging Service Operational
Monitoring Service Operational
Location US/EWR Operational
Compute Operational
Storage Operational
Network Operational
Managed Kubernetes Operational
Supporting Services Operational
Provisioning Operational
Logging Service Operational
Monitoring Service Operational
Location US/LAS Operational
Compute Operational
Storage Operational
Network Operational
Managed Kubernetes Operational
Supporting Services Operational
Provisioning Operational
Logging Service Operational
Monitoring Service Operational
Location US/MCI Operational
Compute Operational
Storage Operational
Network Operational
Managed Kubernetes Operational
Provisioning Operational
Supporting Services Operational
Logging Service Operational
Monitoring Service Operational
APIs and Frontends Operational
Data Center Designer (DCD) Operational
Cloud API Operational
Billing API Operational
Reseller API Operational
Activity Log API Operational
Global Services Operational
Backup Service Operational
CloudDNS Operational
Database as a Service (DBaaS) Operational
Monitoring as a Service (MaaS) Operational
Content Delivery Network (CDN) Operational
AI Model Hub Operational
IAM Operational
Container Registry Operational
Accounts and Billing Operational
GPU Server Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance

Scheduled Maintenance

Network Maintenance Aug 11, 2026 17:00-19:00 UTC

We are performing network maintenance that includes updating routing filters. Generally this has no impact, but in some cases, due to routing convergence, this can cause an impact of 5-10 seconds.

Affected services: Network
Location: Location DE/FRA
Posted on Aug 06, 2026 - 13:40 UTC

Switch provisioning setup Aug 12, 2026 15:00-17:00 UTC

We will be routing provisioning traffic to a new setup to improve stability and geo-redundancy for our customers.

As a result, provisioning services — including the Cloud API and Data Center Designer — may be temporarily unavailable for a few minutes. Since ionosctl, Terraform, and our SDKs depend on the Cloud API, these tools will also be affected during this time. Customer workloads will remain unaffected.

Please follow https://status.ionos.cloud/ for real-time updates.

Affected services: Cloud API, Data Center Designer (DCD), Provisioning
Location: APIs and Frontends, 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
Posted on Aug 05, 2026 - 09:03 UTC

Disabling MariaDB Cluster Creation via API v1 Aug 17, 2026 14:00-16:00 UTC

Effective Aug 17, 2026, IONOS Cloud will permanently disable the creation of new DBaaS MariaDB clusters via API v1. This is a preliminary step in our transition to the upgraded MariaDB v2 infrastructure.

What does this mean for you?
- New Cluster Provisions: Any automated scripts, CI/CD pipelines, SDKs, or IaC tools (e.g., Terraform) attempting to create new MariaDB clusters using API v1 after Aug 17, 2026, will be rejected.
- Existing Clusters: There is no impact on existing MariaDB v1 clusters. All running v1 instances will remain fully operational and accessible as usual.

Required Actions for New Deployments
To deploy new MariaDB clusters going forward, you must transition your provisioning automation to MariaDB v2:
- Update API Calls & Integrations: Switch your scripts, SDKs, and Terraform configurations to use the MariaDB v2 API and providers.
- Review Supported Versions: MariaDB v2 supports versions 10.11, 11.4, 11.8 and 12.3.

Looking Ahead: Automated Cluster Migrations
Existing MariaDB v1 clusters will be automatically migrated to the v2 infrastructure by IONOS with zero downtime. Connection endpoints will remain unchanged. You will receive separate status updates and communications as the migration rollout approaches.

If you have questions or need technical assistance updating your workflows to API v2, please contact our Customer Support team at support@cloud.ionos.com.

Affected services: Database as a Service (DBaaS)
Location: Global Services
Posted on Aug 06, 2026 - 13:39 UTC

Aug 6, 2026

Automated DBaaS PostgreSQL v1 to v2 Infrastructure Migration
Completed - The scheduled maintenance has been completed.
Aug 6, 17:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 3, 09:00 UTC
Scheduled - IONOS Cloud will perform an automated migration of all DBaaS PostgreSQL clusters from the v1 infrastructure to our upgraded v2 infrastructure. This upgrade introduces several key platform enhancements, including lower-latency regional API endpoints, optional native Observability integration (IONOS Logging and Monitoring), and mandatory SSD Premium storage for higher, consistent I/O performance.

What this means for you:
- Automated Migration: The migration is fully managed by IONOS Cloud. No manual migration steps are required for your database clusters.
- Expected Downtime: This brief downtime (typically lasting a few seconds) applies per individual cluster only during its specific migration window. It does not impact the availability of the entire DBaaS service. We recognize that even brief unavailability can affect your operations, and ensuring your service continuity remains our highest priority throughout this transition.
- Database Connections: Your cluster connection endpoints will remain unchanged. Your applications will automatically reconnect once the migration process finishes.

Required Actions for API & Programmatic Users
If you manage your PostgreSQL clusters programmatically via APIs, SDKs, or Infrastructure as Code (IaC) tools (e.g., Terraform), you must take action before the migration begins:
- Switch to Token Authentication: PostgreSQL v2 does not support BASIC authentication for cluster management. You must switch your tools to use TOKEN authentication before July 29, 2026, to prevent management access disruption.
- Instructions for generating authentication tokens can be found in the IONOS Cloud Token Manager Documentation [https://docs.ionos.com/cloud/set-up-ionos-cloud/management/identity-access-management/token-manager].
- Note: If you already use TOKEN authentication or do not manage your clusters programmatically, no action is required.

Important Storage & Price Changes
Notice Regarding Infrastructure Upgrades & Fees:
To ensure peak performance, all PostgreSQL v2 clusters run exclusively on SSD Premium storage.
- Clusters currently running on HDD or SSD Standard storage will be automatically upgraded to SSD Premium as part of this migration and will subsequently be billed at the standard SSD Premium rate.
- Optional usage of the new IONOS Logging and Monitoring integration is billed separately.

As these infrastructure updates constitute changes to the fees applicable to your service, you retain the right to terminate your contract without notice upon the effectiveness of these changes, in accordance with our General Terms and Conditions.

For further technical details regarding the new infrastructure features, please consult the official IONOS Cloud DBaaS PostgreSQL documentation.

Affected services: Database as a Service (DBaaS)
Location: Global Services
Jul 16, 13:34 UTC

Aug 5, 2026

Aug 4, 2026

Cloud Support: Telephone Line Availability Degraded
Resolved - We were able to assign additional personnel and will set this status page to resolved.
Aug 4, 10:02 UTC
Identified - 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.
Aug 4, 08:20 UTC
MK8s - Connectivity Issue
Resolved - we 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.
Aug 4, 10:01 UTC
Update - The migration of storages has been completed, which should prevent further issues with attaching storage. Migration of snapshot data is currently ongoing, so snapshot related activities might still fail to complete successfully.
Jul 19, 12:21 UTC
Update - The first hardware replacement was unsuccessful. Another one is attempted. In the meanwhile a data migration is running to migrate data to another storage target. Due to the amount of data to be migrated the migration is estimated to take several hours.
Jul 18, 22:43 UTC
Update - Hardware replacement was completed. Restoration of redundancy is continuing.
Jul 18, 22:03 UTC
Update - Hardware replacement is being conducted. The team continues to mitigate acute storage provisioning issues until hardware replacement and recovery is completed to minimize customer impact.
Jul 18, 21:31 UTC
Update - The team has encountered a complication during the recovery of the second storage server in the pair. Hardware needs to be replaced. Our datacenter team is working on this task. For customers still affected we are working on implementing a mitigation to unblock storage operations in parallel.
Jul 18, 20:24 UTC
Update - Due to the ongoing restoration effort on the storage server customers might still see residual impact when attaching/detaching storage until redundancy is fully restored. We are resetting the impact of the service back to Degraded Performance.
Jul 18, 19:27 UTC
Monitoring - The incident should now be mitigated. The affected storage server is currently getting restored. Once this is completed, redundancy will be fully restored. We do not see any remaining provisioning issues any longer. We are monitoring the situation and the restoration and will then set the incident to resolved.
Jul 18, 17:54 UTC
Update - We have found an issue with one storage server belonging to a redundant storage server pair. Our team is implementing a mitigation.
Jul 18, 17:24 UTC
Update - While provisioning block could be resolved, we are investigating an increased number of storage related errors. We are directing attention to these remaining issues.
Customers could still see issues with attaching storages on Kubernetes.
Jul 18, 16:54 UTC
Update - Storage issue has successfully been resolved, however, job provisioning is currently not progressing successfully. Our provisioning team is investigating.
Jul 18, 15:51 UTC
Update - Our storage team has confirmed the suspected culprit. We are currently mitigating the issue and will monitor provisioning job execution afterwards.
Jul 18, 15:03 UTC
Update - We have narrowed down the issue and believe we have the culprit identified. We are currently confirming the finding.
Jul 18, 14:47 UTC
Identified - We have identified a spike in our provisioning engine queue that is a likely root cause for the issues observed. Our provisioning team is informed and has joined the response.
Jul 18, 14:26 UTC
Update - Initial investigation makes a network connectivity issue unlikely. The team is focusing investigation on Managed Kubernetes side.
Jul 18, 13:55 UTC
Investigating - We are currently investigating a suspected network connectivity issue influencing the MK8s service. We will keep the status page updated with new information as they become available.
Jul 18, 13:33 UTC

Aug 3, 2026

Disabling In-Memory DB Cluster Creation via API v1
Completed - The scheduled maintenance has been completed.
Aug 3, 14:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 3, 10:00 UTC
Scheduled - Effective Aug 3rd, 2026, IONOS Cloud will permanently disable the creation of new In-Memory DB clusters via API v1. This is a preliminary step in our transition to the upgraded In-Memory DB v2 infrastructure (powered by Valkey).

What does this mean for you?
- New Deployments: Any automated scripts, CI/CD pipelines, SDKs, or IaC tools attempting to provision new In-Memory DB clusters using API v1 after Aug 3rd, 2026, will be rejected.
- Existing Clusters: There is no impact on existing In-Memory DB v1 clusters. All running v1 instances will remain fully operational and accessible.

Required Actions for New Clusters
To deploy new In-Memory DB clusters going forward, you must transition your provisioning workflows to the In-Memory DB v2 API:
- v2 API Documentation: https://api.ionos.com/docs/in-memory-db/v2/
- Client Compatibility: In-Memory DB v2 is powered by Valkey and remains fully compatible with standard Redis clients and tools (no application code changes required).

Affected services: Database as a Service (DBaaS)
Location: Global Services
Jul 23, 13:33 UTC

Aug 2, 2026

No incidents reported.

Aug 1, 2026

No incidents reported.

Jul 31, 2026

No incidents reported.

Jul 30, 2026

No incidents reported.

Jul 29, 2026

No incidents reported.

Jul 28, 2026

Connectivity Issues with DBaaS (MongoDB)
Resolved - 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.
Jul 28, 16:36 UTC
Monitoring - 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.
Jul 28, 13:54 UTC
Identified - 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
Jul 28, 13:51 UTC
Update - We are continuing to investigate this issue.
Jul 28, 13:47 UTC
Investigating - 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.
Jul 28, 13:46 UTC
AI Model Hub - Service Degradations
Resolved - We are marking this incident as resolved. To address the described performance and stability concerns, we have made the following changes:
- Upgraded our AI Modelhub setup to increase overall model performance.
- Rolled out improved monitoring and response tooling for high-load scenarios.
- Replaced Llama 405B with Qwen 3.5 397B.
- Officially deprecated Collections.

We are confident these changes address these issues effectively and will help us provide an even better service moving forward.

Thank you for your patience!
Jul 28, 12:19 UTC
Identified - The AI Model Hub is currently experiencing high demand. As a shared infrastructure environment, this temporary surge in utilization may result in increased latency and varied performance across the platform.

Current Impacts

- Increased Latency (TTFT): High GPU utilization may cause delayed responses (Time to First Token) when initiating model requests. We are continuously managing platform resources to maximize availability across all concurrent workloads.

- Llama 405B Constraints: Due to its scale and high compute requirements, the Llama 405B model is particularly sensitive to traffic spikes, leading to potential timeouts or higher latency—we recommend switching to alternative models for time-critical workloads requiring faster response times.

- Collections: Collections can also be influenced negatively by high demand and utilization. Please see the notes on new deployments in our documentation: https://docs.ionos.com/cloud/ai/ai-model-hub/how-tos/document-collections

Recommendations:

- To mitigate temporarily performance or availability issues, we encourage our customers and partners to implement (exponential backoff) retry mechanisms in their projects and pipelines. Usage peaks that lead in timeouts and degraded performance are usually transient.
- We kindly ask our customers to not create additional Support Tickets for questions and reports related to the performance of models in the Model Hub. Our Product and Tech Teams are aware and are actively monitoring and working on improving the service to meet demand.
- We ask Llama 405B users that face issues to consider a switch to GTP-OSS-120B instead. In most real world use cases, the model is more cost efficient and delivers a more robust performance

Outlook

The following measures are currently underway to improve the performance of the AI Model Hub:

- Various (model specific) optimizations are rolled out on a regular basis
- Improved cross-GPU load balancing (ETA July)
- Adjustments to error codes (replacing HTTP 5xx with HTTP 429) to allow clients to better understand and react to situations
Jun 4, 14:34 UTC
AI Model Hub - Service Degradations
Resolved - 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.
Jul 28, 07:12 UTC
Monitoring - 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.
Jul 23, 11:25 UTC
Investigating - 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
Jul 23, 10:44 UTC

Jul 27, 2026

Cloud Support: Limited Phone Support Availability
Resolved - Cloud Support availability is back.
Thank you for your understanding.
Jul 27, 05:43 UTC
Identified - 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.
Jul 24, 06:51 UTC

Jul 26, 2026

No incidents reported.

Jul 25, 2026

LAS: Storage Loss of Redundancy
Resolved - 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.
Jul 25, 07:49 UTC
Monitoring - 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.
Jul 25, 06:44 UTC
Investigating - 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.
Jul 25, 06:27 UTC

Jul 24, 2026

Jul 23, 2026

Provisioning Maintenance
Completed - The scheduled maintenance has been completed.
Jul 23, 06:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 23, 05:30 UTC
Scheduled - We are conducting maintenance on our provisioning engine. During the maintenance customers might see delays in provisioning of up to 20 minutes — requests submitted via the Cloud API and the Data Center Designer (DCD) may take longer to process.

In rare cases, provisioning errors may occur, requiring the request to be repeated. As such, we recommend scheduling provisioning tasks outside of the maintenance window where possible.

All other services are expected continuing to operate normally. Availability and accessibility of your already provisioned resources will remain unaffected.
Jul 14, 06:53 UTC
← Incident History Powered by Atlassian Statuspage