MongoDB Enterprise: Enforce Connection Limits based on RAM Size

THIS IS A SCHEDULED EVENT Jun 16, 08:30 - 10:30 UTC

Jun 11, 13:47 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