Log in
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
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
Cloud Support Operational
Location DE/FKB Degraded Performance
Compute Operational
Storage Operational
Network Operational
Managed Kubernetes Operational
Supporting Services Operational
Provisioning Degraded Performance
Private Cloud Operational
Logging Service Operational
Monitoring Service Operational
Location DE/FRA Degraded Performance
Compute Operational
Cubes Operational
Storage Operational
Network Operational
Managed Kubernetes Operational
Supporting Services Operational
Provisioning Degraded Performance
Object Storage Operational
Logging Service Operational
Monitoring Service Operational
Location DE/FRA/2 Degraded Performance
Compute Operational
Cubes Operational
Storage Operational
Network Operational
Managed Kubernetes Operational
Supporting Services Operational
Provisioning Degraded Performance
Object Storage Operational
Logging Service Operational
Monitoring Service Operational
Location DE/TXL Degraded Performance
Compute Operational
Cubes Operational
Storage Operational
Network Operational
Managed Kubernetes Operational
Supporting Services Operational
Provisioning Degraded Performance
Object Storage Operational
Private Cloud Operational
Logging Service Operational
Monitoring Service Operational
Location ES/VIT Degraded Performance
Compute Operational
Cubes Operational
Storage Operational
Network Operational
Managed Kubernetes Operational
Supporting Services Operational
Provisioning Degraded Performance
Object Storage Operational
Logging Service Operational
Monitoring Service Operational
Location FR/PAR Degraded Performance
Compute Operational
Storage Operational
Cubes Operational
Managed Kubernetes Operational
Provisioning Degraded Performance
Supporting Services Operational
Network Operational
Logging Service Operational
Monitoring Service Operational
Location GB/BHX Degraded Performance
Compute Operational
Cubes Operational
Storage Operational
Network Operational
Managed Kubernetes Operational
Supporting Services Operational
Provisioning Degraded Performance
Logging Service Operational
Monitoring Service Operational
Location GB/GLO Operational
Private Cloud Operational
Location GB/LHR Degraded Performance
Compute Operational
Cubes Operational
Storage Operational
Network Operational
Managed Kubernetes Operational
Supporting Services Operational
Provisioning Degraded Performance
Logging Service Operational
Monitoring Service Operational
Location US/EWR Degraded Performance
Compute Operational
Storage Operational
Network Operational
Managed Kubernetes Operational
Supporting Services Operational
Provisioning Degraded Performance
Logging Service Operational
Monitoring Service Operational
Location US/LAS Degraded Performance
Compute Operational
Storage Operational
Network Operational
Managed Kubernetes Operational
Supporting Services Operational
Provisioning Degraded Performance
Logging Service Operational
Monitoring Service Operational
Location US/MCI Degraded Performance
Compute Operational
Storage Operational
Network Operational
Managed Kubernetes Operational
Provisioning Degraded Performance
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 Degraded Performance
Backup Service Operational
CloudDNS Operational
Database as a Service (DBaaS) Degraded Performance
Monitoring as a Service (MaaS) Operational
Content Delivery Network (CDN) Operational
AI Model Hub Degraded Performance
IAM Operational
Container Registry Operational
Accounts and Billing Operational
GPU Server Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance

Scheduled Maintenance

Scheduled Network Configuration Update Jun 22, 2026 10:00-15:00 UTC

We are performing a phased upgrade of our network configuration across all locations. This update includes firewall and cluster configuration changes required to integrate new frontend nodes. There should be no impact, but on rare occasions a brief packet loss of a few seconds may occur.

Affected services: Network
Location: 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 Jun 18, 2026 - 12:10 UTC

Network Maintenance Jun 23, 2026 08:00-11:00 UTC

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 2-3 seconds. If you have multiple workloads on different hosts, then this impact can be experienced multiple times.

Affected services: Network
Location: Location US/EWR, Location US/LAS, Location US/MCI
Posted on Jun 18, 2026 - 12:12 UTC
Jun 18, 2026
Provisioning Maintenance
Completed - The scheduled maintenance has been completed.
Jun 18, 06:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 18, 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. There will be no impact on existing, already provisioned resources. We recommend scheduling provisioning tasks outside of the maintenance window where possible.

Affected services: Provisioning
Location: APIs and Frontends, Cloud Support, Global Services, Location DE/FRA, Location DE/FRA/2, Location DE/TXL
Jun 12, 11:11 UTC
Jun 17, 2026
S3 High Error Rate - TXL
Resolved - The incident has now been resolved, and accessing S3 Buckets should now be working as expected.
Jun 17, 14:03 UTC
Investigating - We are currently experiencing a high error rate with S3 Object Storage in TXL - eu-central-3.
This is currently being investigated and we will continue to keep this page updated.
Jun 17, 11:40 UTC
Jun 16, 2026
MongoDB Enterprise: Enforce Connection Limits based on RAM Size
Completed - The scheduled maintenance has been completed.
Jun 16, 10:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 16, 08:30 UTC
Scheduled - Scheduled Maintenance: MongoDB Connection Limit Enforcement

Effective Date: June 16, 2026
Affected Service: IONOS Managed MongoDB Enterprise Edition clusters

To ensure ongoing platform stability and predictable performance, IONOS will begin strictly enforcing connection limits on Managed MongoDB clusters. Applications that open excessive concurrent connections may begin experiencing connection-limit errors after the effective date.

Required Actions to Prevent Disruptions:
Implement driver-based connection pooling.
Reuse the MongoDB client and connection rather than creating a new client per request.
Tune your driver's pool settings appropriately, focusing on variables like maxPoolSize, minPoolSize, and waitQueueTimeout.
Validate your total connection footprint across all application instances and environments.

Helpful Resources & Support
Please review the IONOS MongoDB Sizing Guide to properly tune your connections and pools. If you anticipate needing additional connection capacity, please reach out to Support with your current connection usage patterns (number of instances, expected peak concurrency, and driver settings).

Affected services: Database as a Service (DBaaS)
Location: Global Services
Jun 11, 13:47 UTC
Jun 15, 2026
Availability Issue DCD
Resolved - The system is stable. We are resolving this incident. The trigger of this incident will be shared once the analysis has been completed.
Jun 15, 11:20 UTC
Monitoring - The DCD is available again. We are monitoring the system closely and will set this incident to resolved once the environment is confirmed stable.
Jun 15, 10:41 UTC
Update - We believe that the trigger for the incident has been mitigated. We are currently working on restoring all services related to the DCD.
Jun 15, 10:18 UTC
Identified - Our DCD Team is currently investigating the incident. We have confirmed that Cloud API remains functional and available. Customers and Partners needing to deploy changes to their setup can still use ionosctl and cloudapi to do so.
Jun 15, 09:23 UTC
Investigating - We are currently investigating increased loading times and timeouts for the DCD.
Jun 15, 09:03 UTC
Jun 14, 2026

No incidents reported.

Jun 13, 2026
Cloud Support: Telephone Support temporarily unavailable
Resolved - Phone Support is now available again
Jun 13, 21:13 UTC
Identified - IONOS Cloud Support is temporarily unavailable via phone. We ask Customers and Partners to contact Cloud Support via DCD Form and Email, instead.
Jun 13, 13:50 UTC
Jun 12, 2026
S3: eu-central-3 Increased Error Rate
Resolved - We are closing the incident as no further error spikes were recorded. We will share the trigger of this incident once the analysis has been conducted.
Jun 12, 13:49 UTC
Monitoring - Error rates have significantly decreased. We are monitoring the situation further and will resolve the incident if the situation stays as is.
Jun 12, 09:08 UTC
Update - The mitigation efforts have lead to first improvements. We have downgraded the incident severity.
However, we still see elevated error rates and are working towards resolving the remaining issues.
Jun 12, 08:07 UTC
Identified - Our Object Storage Team has identified an issue connected with gateways in the affected region and is currently mitigating the problem. Customers may see connectivity issues and timeouts. We will keep you updated on the mitigation efforts.
Jun 12, 07:54 UTC
Investigating - We are currently investigating increased error rate for S3 in eu-central-3
Jun 12, 07:44 UTC
Jun 11, 2026

No incidents reported.

Jun 10, 2026

No incidents reported.

Jun 9, 2026

No incidents reported.

Jun 8, 2026
Object Storage unavailable in Frankfurt
Resolved - The Object Storage endpoints are stable now.
Jun 8, 14:33 UTC
Monitoring - The team found the issue in a bad network setting / routing.
This was fixed, so the service is back again.
It happened 12:45 - 13:20 UTC today, but now all endpoints are available.
We are monitoring the situation, and we will provide an analysis once the investigation was finished.
Jun 8, 13:33 UTC
Investigating - Currently we face major availability problems in our Object Storage service in Frankfurt.
You might encounter degraded access to your buckets and objects in de (eu-central-1).
The team is investigating the issue and trying to fix it as soon as possible.
Jun 8, 13:21 UTC
Jun 7, 2026

No incidents reported.

Jun 6, 2026

No incidents reported.

Jun 5, 2026

No incidents reported.

Jun 4, 2026

Unresolved incident: AI Model Hub - Service Degradations.

← Incident History Powered by Atlassian Statuspage