{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreia4fpinuvaqo4rzoeqkt6ybnqllm5k3emguykfes2l5afvajvt6ly",
    "uri": "at://did:plc:4v6p7jmcf7x6uhskfbaqfc25/app.bsky.feed.post/3mnzqwri2ouh2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreiblq3wqbt5gewbqpvfd2dcif7lthr4xh6bn4ijrioze7qdcyvadm4"
    },
    "mimeType": "image/png",
    "size": 3910
  },
  "path": "/incidents/p8zny380zcnk",
  "publishedAt": "2026-06-16T08:30:00.000Z",
  "site": "https://status.ionos.cloud",
  "textContent": "**THIS IS A SCHEDULED EVENT Jun 16, 08:30 - 10:30 UTC**\n\nJun 11, 13:47 UTC\n**Scheduled** - Scheduled Maintenance: MongoDB Connection Limit Enforcement\n\nEffective Date: June 16, 2026\nAffected Service: IONOS Managed MongoDB Enterprise Edition clusters\n\nTo 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.\n\nRequired Actions to Prevent Disruptions:\nImplement driver-based connection pooling.\nReuse the MongoDB client and connection rather than creating a new client per request.\nTune your driver's pool settings appropriately, focusing on variables like maxPoolSize, minPoolSize, and waitQueueTimeout.\nValidate your total connection footprint across all application instances and environments.\n\nHelpful Resources & Support\nPlease 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).\n\nAffected services: Database as a Service (DBaaS)\nLocation: Global Services",
  "title": "MongoDB Enterprise: Enforce Connection Limits based on RAM Size",
  "updatedAt": "2026-06-11T13:47:41.000Z"
}