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
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.
- 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
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
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
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
Degraded Performance
Backup Service
Operational
CloudDNS
Operational
Database as a Service (DBaaS)
Degraded Performance
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 Posted on
Jun 11, 2026 - 13:47 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. 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 Posted on
Jun 12, 2026 - 11:11 UTC
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
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.
Completed -
The scheduled maintenance has been completed.
Jun 3, 15:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 3, 11:00 UTC
Scheduled -
We will be performing a scheduled upgrade of the network management software (SDN) for our server infrastructure. This maintenance will bring our systems to the latest stable version to ensure optimal performance. This maintenance might cause an interruption of network connectivity for up to 1 (one) minute per processed host server. Only network of Cubes component is affected. If you have Cubes or services that are hosted on various hosts, you might experience multiple instances of this service disruption.
Affected services: Network Location: Location DE/TXL
May 29, 08:05 UTC
Completed -
The scheduled maintenance has been completed.
Jun 3, 07:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 3, 05:00 UTC
Scheduled -
During this window, we will be testing our disaster recovery systems to ensure your data and services remain protected in the event of an unplanned outage. As part of this exercise, traffic will be briefly redirected to our secondary data center.
You may experience a short interruption of the provisioning service (typically less than 15 minutes) during the switchover. During this time period provisioning requests will not be processed, which will slow down provisioning. No action is required on your part, and no data will be lost.
Completed -
The scheduled maintenance has been completed.
Jun 2, 21:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 2, 17:00 UTC
Scheduled -
We will be performing a scheduled upgrade of the Network File Storage (NFS) for our server infrastructure. This maintenance will bring our systems to the latest stable version to ensure optimal performance. This maintenance might cause an interruption of NFS connectivity for up to 5 (five) minute per processed cluster.
Affected services: Storage Location: Location DE/TXL
Jun 1, 08:19 UTC
Completed -
The scheduled maintenance has been completed.
Jun 2, 15:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 2, 11:00 UTC
Scheduled -
We will be performing a scheduled upgrade of the network management software (SDN) for our server infrastructure. This maintenance will bring our systems to the latest stable version to ensure optimal performance. This maintenance might cause an interruption of network connectivity for up to 1 (one) minute per processed host server. Only the network of Cubes component is affected. If you have cubes that are hosted on various hosts, you might experience multiple instances of this service disruption.
Affected services: Network Location: Location DE/TXL
May 29, 08:06 UTC
Resolved -
This incident has been resolved.
Jun 2, 11:28 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Jun 1, 16:57 UTC
Investigating -
Currently, there is an increased processing time for provisioning orders that are initiated via Data Center Designer or API.
Occasionally, connections may be lost in the direction of the Data Center Designer.
Availability and accessibility of your virtual data center resources will remain unaffected. We will inform you as soon as the functionality has been restored.
Jun 1, 14:10 UTC
Completed -
The scheduled maintenance has been completed.
Jun 1, 21:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 1, 17:00 UTC
Scheduled -
We will be performing a scheduled upgrade of the Network File Storage (NFS) for our server infrastructure. This maintenance will bring our systems to the latest stable version to ensure optimal performance. This maintenance might cause an interruption of NFS connectivity for up to 5 (five) minute per processed cluster.
Affected services: Storage Location: Location DE/FRA
Jun 1, 08:20 UTC
Resolved -
This incident has been resolved.
Jun 1, 17:06 UTC
Monitoring -
The Mistral Small 24B Instruct model is currently experiencing a high load. For users experiencing timeouts, we recommend switching to an alternative model, such as GPT-OSS-120B.
The slow response times previously observed in Collections are no longer occurring.
May 29, 22:31 UTC
Identified -
We are currently experiencing significant load, which is affecting the response times of our Modelhub. Our team is working on removing performance bottlenecks.
May 29, 20:43 UTC
Investigating -
We are currently investigating increased latency and error count in the AI Model Hub
May 29, 20:23 UTC
Completed -
The scheduled maintenance has been completed.
Jun 1, 15:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 1, 11:00 UTC
Scheduled -
We will be performing a scheduled upgrade of the network management software (SDN) for our server infrastructure. This maintenance will bring our systems to the latest stable version to ensure optimal performance. This maintenance might cause an interruption of network connectivity for up to 1 (one) minute per processed host server. Only the network of Cubes component is affected. If you have cubes that are hosted on various hosts, you might experience multiple instances of this service disruption.
Affected services: Network Location: Location ES/VIT, Location GB/LHR
May 29, 08:06 UTC
Completed -
The scheduled maintenance has been completed.
Jun 1, 12:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 1, 10:00 UTC
Scheduled -
Starting May 31, 2026, MongoDB Playground clusters will be automatically and permanently deleted 30 days after their creation date, as outlined in our customer documentation. https://docs.ionos.com/cloud/databases/mongodb/overview
What is changing * Existing clusters created more than 30 days before May 31, 2026 will be deleted on May 31, 2026. * Existing clusters created less than 30 days before May 31, 2026 will be deleted 30 days after their creation date. * New clusters created on or after May 31, 2026 will be deleted 30 days after creation.
Playground clusters do not include automated backups, so any data not exported before deletion will be unrecoverable.
Action required * If you want to keep your data, please export it before your cluster's deletion date using mongodump. See MongoDB Backup & Recovery. * Need your cluster for longer than 30 days? MongoDB Business Edition removes the 30-day limit and adds automated daily backups, higher connection limits, and production-ready performance.