{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreichyunk5eoirm2fv4lihvq7kv473ofnufhbggogp5b3dexlsn7ana",
    "uri": "at://did:plc:4v6p7jmcf7x6uhskfbaqfc25/app.bsky.feed.post/3moxx5zsbfka2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreiblq3wqbt5gewbqpvfd2dcif7lthr4xh6bn4ijrioze7qdcyvadm4"
    },
    "mimeType": "image/png",
    "size": 3910
  },
  "path": "/incidents/t7t03ygds59g",
  "publishedAt": "2026-06-23T08:21:04.000Z",
  "site": "https://status.ionos.cloud",
  "textContent": "Jun 23, 08:21 UTC\n**Identified** - We were able to reactivate the MK8s maintenances in all clusters in our TXL datacenter\n\nJun 22, 19:07 UTC\n**Investigating** - Due to exceptionally high demand in two clusters in our TXL and FRA datacenters, we have temporarily paused Managed Kubernetes Automated Maintenance.\n\nTo 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.\n\nTo 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.\n\nWe 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.",
  "title": "Managed Kubernetes - Automated Maintenance disabled",
  "updatedAt": "2026-06-23T08:21:04.000Z"
}