Log in
AI Model Hub - Service Degradations
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 04, 2026 - 14:34 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 Partial Outage
Backup Service Operational
CloudDNS Operational
Database as a Service (DBaaS) Partial Outage
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

Provisioning Maintenance Jul 20, 2026 08:00-09:30 UTC

We are conducting maintenance on our provisioning engine. During the maintenance, customers might see delays in provisioning during a time period of approximately 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 to operate normally. Availability and accessibility of your already provisioned resources will remain unaffected

Affected services: Activity Log API, Billing API, Cloud API, Data Center Designer (DCD), Provisioning, Reseller API
Location: APIs and Frontends, Location DE/FRA, Location DE/TXL, Location FR/PAR, Location GB/GLO, Location US/EWR, Location US/MCI
Posted on Jul 17, 2026 - 08:13 UTC

Provisioning Maintenance Jul 23, 2026 05:30-06:30 UTC

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.
Posted on Jul 14, 2026 - 06:53 UTC

Automated DBaaS PostgreSQL v1 to v2 Infrastructure Migration Aug 3, 2026 09:00 - Aug 6, 2026 17:00 UTC

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
Posted on Jul 16, 2026 - 13:34 UTC
Jul 17, 2026
Cloud Support: Upcoming Limited Phone Support Availability
Resolved - Phone coverage is currently normal
Jul 17, 16:55 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.

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!
Jul 15, 10:15 UTC
Jul 16, 2026

No incidents reported.

Jul 15, 2026
Disabling PostgreSQL Cluster Creation via API v1
Completed - The scheduled maintenance has been completed.
Jul 15, 12:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 15, 10:00 UTC
Scheduled - Details:
During this scheduled maintenance window, we will permanently disable the creation of new DBaaS PostgreSQL clusters via API v1. This is a mandatory step in our transition to the upgraded PostgreSQL v2 infrastructure, which offers enhanced I/O performance, reduced management latency, and native observability tools.

What does this mean for you?
New Deployments: Any automated scripts attempting to provision new PostgreSQL clusters using API v1 after this window will receive an error and fail.
Existing Clusters: There is no impact on existing PostgreSQL v1 clusters during this maintenance. They will remain fully operational and accessible.

Required Actions
If you manage your database infrastructure programmatically, please perform the following steps to ensure uninterrupted operations:
Migrate to API v2: Update your deployment workflows, scripts, and IaC configurations to use API v2 for all future PostgreSQL cluster provisions. API v2: https://api.ionos.com/docs/postgresql/v2/
Switch to Token Authentication: PostgreSQL v2 does not support Basic Authentication. To maintain management access, ensure your tools are updated to use Token Authentication. (Note: Token authentication is already supported on v1 and can be implemented immediately).

Looking Ahead: Automatic Cluster Migrations
Existing PostgreSQL v1 clusters will be automatically migrated to the v2 infrastructure by IONOS in the near future. This maintenance window only blocks the creation of new v1 clusters. You will receive a separate, official email communication detailing your specific cluster migration window and what to expect.

Affected services: Database as a Service (DBaaS)
Location: APIs and Frontends, Global Services
Jun 19, 09:44 UTC
Jul 14, 2026

No incidents reported.

Jul 13, 2026
Resources in an Unknown state - FRA
Resolved - The incident has been resolved, the VMs are back working again.
Jul 13, 13:44 UTC
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.
Jul 13, 12:00 UTC
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.
Jul 13, 11:51 UTC
Update - We are continuing to investigate this issue.
Jul 13, 11:17 UTC
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.
Jul 13, 11:16 UTC
VMs and managed services availability in FRA degraded
Resolved - This was a duplicate.
Jul 13, 11:21 UTC
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.
Jul 13, 11:18 UTC
Jul 12, 2026

No incidents reported.

Jul 11, 2026

No incidents reported.

Jul 10, 2026
Power Infrastructure Incident in VIT
Resolved - We are marking this incident as resolved. The Root Cause Analysis will be published here once compiled.
Jul 10, 07:59 UTC
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.
Jul 10, 00:41 UTC
Update - 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.
Jul 10, 00:28 UTC
Update - Most affected hosts have been brought back into service. We are working on restoring the remaining components.
Jul 9, 22:47 UTC
Identified - Power has been restored and site support systems are back in operational state. We have started recovering infrastructure components to fully restore service.
Jul 9, 22:29 UTC
Investigating - We are currently responding to an incident in our VIT datacenter. We will regularly update this status page with information.
Jul 9, 22:16 UTC
Jul 9, 2026
Jul 8, 2026
Partial Connectivity Degradation to Control Plane Affecting Kubernetes Operations
Resolved - This incident has been resolved. We are working on the RCA and will publish it here asap
Jul 8, 09:33 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jul 5, 17:27 UTC
Update - We are continuing to work on a fix for this issue.
Jul 5, 16:02 UTC
Identified - We are currently experiencing increased processing times for provisioning orders initiated via the Data Center Designer (DCD) or API. Additionally, intermittent connectivity issues may occur when accessing the Data Center Designer or API.
Please note that this issue is not limited to Managed Kubernetes services and may impact all cloud workloads involving new provisioning or modifications.

Important: The availability, stability, and accessibility of your existing running virtual data center resources remain entirely unaffected.
Our engineering teams are actively working to resolve the issue. We will provide a further update as soon as full functionality has been restored.
Jul 5, 14:47 UTC
Provisioning: Degraded Performance in Job Processing
Resolved - This incident has been resolved. We are working on the RCA and will publish it here asap
Jul 8, 09:31 UTC
Monitoring - Our Provisioning Team has been closely tracking queue performance over the last few hours and has noted steady improvements. We are moving this incident to Monitoring status.
We will continue to monitor queue processing closely and will update this page on any changes.
Jul 8, 06:57 UTC
Update - Still, the global provisioning system is not working properly.
Therefore, all other dependencies, like K8s and managed products, are affected, too.
We know this is affecting customer setups, and that urgent changes are not processed properly, and we apologize for the inconvenience.
We identified possible distractors, but fixing this is a complex task, with need to involve and coordinate several technical teams.
We are working with highest prio to get the provisioning back working,
and we will let you know asap on any progress.
Jul 7, 09:36 UTC
Identified - We are currently investigating instances of performance degradation in job processing. Our Provisioning Team is currently working on fixing the root cause of these events.
Jul 6, 10:14 UTC
Jul 7, 2026
Network Maintenance
Completed - The scheduled maintenance has been completed.
Jul 7, 19:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 7, 17:00 UTC
Scheduled - We will perform a network optimization maintenance in which some filters will update. This is generally does not lead to customer facing service degradation, however in some cases - due to network convergence - there can be some packet loss for up to 2-3 seconds. If you have multiple workloads on different hosts, then this impact can be experienced multiple times.


Affected services: Network
Location: Location DE/FKB, Location ES/VIT, Location GB/BHX, Location GB/LHR
Jun 30, 13:33 UTC
Partial Control Plane Outage Affecting Kubernetes Operations
Resolved - This incident has been resolved.
Jul 7, 10:09 UTC
Monitoring - Incident involving degradation of the control plane has been resolved and we are monitoring the situation.
Jul 1, 19:07 UTC
Update - The situation appears to have stabilized for the time being. An internal investigation into the exact root cause is ongoing.
Jun 30, 22:55 UTC
Investigating - Customers may experience connection problems to the control plane and degraded functionality of kubernetes
Jun 30, 21:08 UTC
Jul 6, 2026
Jul 5, 2026
Provisioning: Degraded Performance in Job Processing
Resolved - The provisioning queue looks healthy again, and all services have been reactivated.
Jul 5, 11:50 UTC
Update - We are currently seeing progress in provisioning, and the DCD maintenance page has been removed from the DCD.
Jul 5, 11:32 UTC
Update - We are continuing to investigate this issue.
Jul 5, 08:31 UTC
Update - We are continuing to investigate this issue.
Jul 5, 08:14 UTC
Update - We are continuing to investigate this issue.
Jul 5, 08:12 UTC
Update - For Investigation we set mk8s api to maintenance mode (read-only)
Jul 5, 08:08 UTC
Update - We are continuing to investigate this issue.
Jul 5, 08:04 UTC
Investigating - We are currently investigating instances of performance degradation in job processing. Our Provisioning Team is currently investigating the root cause of these events.
Jul 5, 08:01 UTC
Jul 4, 2026

No incidents reported.

Jul 3, 2026
Provisioning issues in FRA and TXL
Resolved - Our Provisioning went back operational yesterday around 16:30 UTC.
Further monitoring showed no issues anymore, so this incident was resolved.
Jul 3, 09:16 UTC
Identified - We found the root cause and implemented mitigation measures.
We expect the errors to decrease significantly now.
We will let you know asap when we consider the situation being back to normal.
Jul 2, 13:51 UTC
Investigating - Currently we are facing increased provisioning problems resulting in error code [VDC-5-0].
We understand the impact, and our teams are investigating the root cause to get this fixed asap.
Please postpone your provisioning until we resolve the issue, we will inform you of any updates.
Jul 2, 08:30 UTC
← Incident History Powered by Atlassian Statuspage