{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreifyt2e5hxvp7wlbkjqkul5iromeqoydpw5prjxgsscji6hstgvqsm",
    "uri": "at://did:plc:7djy4r5ivvt6ia3rquazuc4u/app.bsky.feed.post/3mh7a53h7e4s2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreiblq3wqbt5gewbqpvfd2dcif7lthr4xh6bn4ijrioze7qdcyvadm4"
    },
    "mimeType": "image/png",
    "size": 3910
  },
  "path": "/incidents/h9x5s66m4r28",
  "publishedAt": "2026-03-16T19:34:20.000Z",
  "site": "https://status.ionos.cloud",
  "textContent": "Mar 16, 19:34 UTC\n**Update** - The changes applied to some control plane clusters have had positive effects. The team is continuing the rollout to other affected clusters.\n\nMar 16, 13:56 UTC\n**Update** - We are marking DBaaS as recovered.\nOur Kubernetes Team is currently working on stabilizing the Kubernetes Control Plane. We are focusing on mitigating recurring load spikes influencing stability.\n\nMar 16, 12:57 UTC\n**Update** - We are marking the Container Registry Service as recovered.\n\nMar 16, 12:22 UTC\n**Update** - We are closing the incident for the AI Model Hub. All metrics have recovered and the service should be up and running again normally.\n\nMar 16, 11:57 UTC\n**Update** - We are adding the Container Registry as an affected Service. Customers may currently experience issues pulling and pushing images from the Registry.\n\nMar 16, 11:37 UTC\n**Update** - Our Kubernetes Team has deployed a fix for the affected AI Model Hub Database Services. We currently see metrics improving and monitoring the situation closely.\n\nMar 16, 11:05 UTC\n**Update** - We are expanding the scope of this incident to include DBaaS and AI Model Hub. We have observed an increased error count originating from PostgresDB on Kubernetes. Additionally, to improve transparency, the previously reported separate incident regarding the AI Model Hub (https://status.ionos.cloud/incidents/rmgs845klm32) is being merged into this primary incident.\n\nMar 16, 10:04 UTC\n**Identified** - The team has identified the root cause as a resource constraint within the etcd database. Mitigation efforts are currently underway.\n\nMar 16, 08:24 UTC\n**Investigating** - Some customers may experience connection problems to the control plane and degraded functionality of kubernetes.\nOur teams are investigating and working on a resolution.",
  "title": "MK8s: Partial Connectivity Degradation to Control Planes",
  "updatedAt": "2026-03-16T19:34:20.000Z"
}