IONOS Cloud Status

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.

15.07.2026: 21:00 – 05:00 UTC 16.07.2026: 21:00 – 05:00 UTC

If possible, we ask that you submit tickets using the DCD Form or via email.

Thank you for your understanding!

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.

Resolved: This was a duplicate.

Investigating: We are currently investigating problems accessing VMs and DBaaS service located in Frankfurt. We will inform you as soon as the functionality has been restored.

Resolved: The incident has been resolved, the VMs are back working again.

Monitoring: Our tech teams were able to restore all VMs and products, so all are back available and running. However, we keep monitoring the situation for a while.

Identified: Our teams identified some affected hardware servers that caused the unavailability. We are now in process of migrating the affected VMs to different HW servers, so please check your VMs. We are still working on the root cause investigation.

Investigating: We are continuing to investigate this issue.

Investigating: We are currently experiencing an issue where resources in the FRA region are unreachable and showing an Unknown state. This issue is currently being investigated and we will keep you informed of any updates.

Resolved: The incident has been resolved, the VMs are back working again.

Monitoring: Our tech teams were able to restore all VMs and products, so all are back available and running. However, we keep monitoring the situation for a while.

Identified: Our teams identified some affected hardware servers that caused the unavailability. We are now in process of migrating the affected VMs to different HW servers, so please check your VMs. We are still working on the root cause investigation.

Investigating: We are continuing to investigate this issue.

Investigating: We are currently experiencing an issue where resources in the FRA region are unreachable and showing an Unknown state. This issue is currently being investigated and we will keep you informed of any updates.

Resolved: The incident has been resolved, the VMs are back working again.

Monitoring: Our tech teams were able to restore all VMs and products, so all are back available and running. However, we keep monitoring the situation for a while.

Identified: Our teams identified some affected hardware servers that caused the unavailability. We are now in process of migrating the affected VMs to different HW servers, so please check your VMs. We are still working on the root cause investigation.

Investigating: We are continuing to investigate this issue.

Investigating: We are currently experiencing an issue where resources in the FRA region are unreachable and showing an Unknown state. This issue is currently being investigated and we will keep you informed of any updates.

Resolved: The incident has been resolved, the VMs are back working again.

Monitoring: Our tech teams were able to restore all VMs and products, so all are back available and running. However, we keep monitoring the situation for a while.

Identified: Our teams identified some affected hardware servers that caused the unavailability. We are now in process of migrating the affected VMs to different HW servers, so please check your VMs. We are still working on the root cause investigation.

Investigating: We are continuing to investigate this issue.

Investigating: We are currently experiencing an issue where resources in the FRA region are unreachable and showing an Unknown state. This issue is currently being investigated and we will keep you informed of any updates.

Identified: We were able to reactivate the MK8s maintenances in all clusters in our TXL datacenter

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.

Resolved: The incident has been resolved, the VMs are back working again.

Monitoring: Our tech teams were able to restore all VMs and products, so all are back available and running. However, we keep monitoring the situation for a while.

Identified: Our teams identified some affected hardware servers that caused the unavailability. We are now in process of migrating the affected VMs to different HW servers, so please check your VMs. We are still working on the root cause investigation.

Investigating: We are continuing to investigate this issue.

Investigating: We are currently experiencing an issue where resources in the FRA region are unreachable and showing an Unknown state. This issue is currently being investigated and we will keep you informed of any updates.

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.

Resolved: The incident has been resolved, the VMs are back working again.

Monitoring: Our tech teams were able to restore all VMs and products, so all are back available and running. However, we keep monitoring the situation for a while.

Identified: Our teams identified some affected hardware servers that caused the unavailability. We are now in process of migrating the affected VMs to different HW servers, so please check your VMs. We are still working on the root cause investigation.

Investigating: We are continuing to investigate this issue.

Investigating: We are currently experiencing an issue where resources in the FRA region are unreachable and showing an Unknown state. This issue is currently being investigated and we will keep you informed of any updates.

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.

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.

Identified: We were able to reactivate the MK8s maintenances in all clusters in our TXL datacenter

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.

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.

Resolved: We are marking this incident as resolved. The Root Cause Analysis will be published here once compiled.

Monitoring: The last host and VMs have been recovered. We are setting this incident into monitoring status.

Preliminary information on the Incident: Following a power grid outage, the site suffered a partial interruption of power, which impacted several datacenter support systems. The reason for this is under active investigation. This affected the availability of a subset of infrastructure components and hosts, subsequently impacting the VMs provisioned on them or dependent on those components.

A full Root Cause Analysis (RCA) is currently being compiled and will be shared here once completed.

Thank you for your patience.

Identified: All but one hosts are recovered. The remaining host suffered a hardware defect and needs to be replaced to recover the workload provisioned there. This is currently underway. We estimate that this work will be completed within the next minutes.

Identified: Most affected hosts have been brought back into service. We are working on restoring the remaining components.

Identified: Power has been restored and site support systems are back in operational state. We have started recovering infrastructure components to fully restore service.

Investigating: We are currently responding to an incident in our VIT datacenter. We will regularly update this status page with information.

Resolved: We are marking this incident as resolved. The Root Cause Analysis will be published here once compiled.

Monitoring: The last host and VMs have been recovered. We are setting this incident into monitoring status.

Preliminary information on the Incident: Following a power grid outage, the site suffered a partial interruption of power, which impacted several datacenter support systems. The reason for this is under active investigation. This affected the availability of a subset of infrastructure components and hosts, subsequently impacting the VMs provisioned on them or dependent on those components.

A full Root Cause Analysis (RCA) is currently being compiled and will be shared here once completed.

Thank you for your patience.

Identified: All but one hosts are recovered. The remaining host suffered a hardware defect and needs to be replaced to recover the workload provisioned there. This is currently underway. We estimate that this work will be completed within the next minutes.

Identified: Most affected hosts have been brought back into service. We are working on restoring the remaining components.

Identified: Power has been restored and site support systems are back in operational state. We have started recovering infrastructure components to fully restore service.

Investigating: We are currently responding to an incident in our VIT datacenter. We will regularly update this status page with information.

Resolved: We are marking this incident as resolved. The Root Cause Analysis will be published here once compiled.

Monitoring: The last host and VMs have been recovered. We are setting this incident into monitoring status.

Preliminary information on the Incident: Following a power grid outage, the site suffered a partial interruption of power, which impacted several datacenter support systems. The reason for this is under active investigation. This affected the availability of a subset of infrastructure components and hosts, subsequently impacting the VMs provisioned on them or dependent on those components.

A full Root Cause Analysis (RCA) is currently being compiled and will be shared here once completed.

Thank you for your patience.

Identified: All but one hosts are recovered. The remaining host suffered a hardware defect and needs to be replaced to recover the workload provisioned there. This is currently underway. We estimate that this work will be completed within the next minutes.

Identified: Most affected hosts have been brought back into service. We are working on restoring the remaining components.

Identified: Power has been restored and site support systems are back in operational state. We have started recovering infrastructure components to fully restore service.

Investigating: We are currently responding to an incident in our VIT datacenter. We will regularly update this status page with information.

Resolved: We are marking this incident as resolved. The Root Cause Analysis will be published here once compiled.

Monitoring: The last host and VMs have been recovered. We are setting this incident into monitoring status.

Preliminary information on the Incident: Following a power grid outage, the site suffered a partial interruption of power, which impacted several datacenter support systems. The reason for this is under active investigation. This affected the availability of a subset of infrastructure components and hosts, subsequently impacting the VMs provisioned on them or dependent on those components.

A full Root Cause Analysis (RCA) is currently being compiled and will be shared here once completed.

Thank you for your patience.

Identified: All but one hosts are recovered. The remaining host suffered a hardware defect and needs to be replaced to recover the workload provisioned there. This is currently underway. We estimate that this work will be completed within the next minutes.

Identified: Most affected hosts have been brought back into service. We are working on restoring the remaining components.

Identified: Power has been restored and site support systems are back in operational state. We have started recovering infrastructure components to fully restore service.

Investigating: We are currently responding to an incident in our VIT datacenter. We will regularly update this status page with information.

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.

Resolved: We are marking this incident as resolved. The Root Cause Analysis will be published here once compiled.

Monitoring: The last host and VMs have been recovered. We are setting this incident into monitoring status.

Preliminary information on the Incident: Following a power grid outage, the site suffered a partial interruption of power, which impacted several datacenter support systems. The reason for this is under active investigation. This affected the availability of a subset of infrastructure components and hosts, subsequently impacting the VMs provisioned on them or dependent on those components.

A full Root Cause Analysis (RCA) is currently being compiled and will be shared here once completed.

Thank you for your patience.

Identified: All but one hosts are recovered. The remaining host suffered a hardware defect and needs to be replaced to recover the workload provisioned there. This is currently underway. We estimate that this work will be completed within the next minutes.

Identified: Most affected hosts have been brought back into service. We are working on restoring the remaining components.

Identified: Power has been restored and site support systems are back in operational state. We have started recovering infrastructure components to fully restore service.

Investigating: We are currently responding to an incident in our VIT datacenter. We will regularly update this status page with information.

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.

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.

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.

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.

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.

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.

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.

Resolved: This was a duplicate.

Investigating: We are currently investigating problems accessing VMs and DBaaS service located in Frankfurt. We will inform you as soon as the functionality has been restored.

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