IONOS Cloud incident

Power Infrastructure Incident in VIT

Major Resolved View vendor source →

IONOS Cloud experienced a major incident on July 9, 2026 affecting Compute and Cubes and 1 more component, lasting 9h 43m. The incident has been resolved; the full update timeline is below.

Started
Jul 09, 2026, 10:16 PM UTC
Resolved
Jul 10, 2026, 07:59 AM UTC
Duration
9h 43m
Detected by Pingoru
Jul 09, 2026, 10:16 PM UTC

Affected components

ComputeCubesStorageNetworkProvisioning

Update timeline

  1. investigating Jul 09, 2026, 10:16 PM UTC

    We are currently responding to an incident in our VIT datacenter. We will regularly update this status page with information.

  2. identified Jul 09, 2026, 10:29 PM UTC

    Power has been restored and site support systems are back in operational state. We have started recovering infrastructure components to fully restore service.

  3. identified Jul 09, 2026, 10:47 PM UTC

    Most affected hosts have been brought back into service. We are working on restoring the remaining components.

  4. identified Jul 10, 2026, 12:28 AM UTC

    All but one hosts are recovered. The remaining host suffered a hardware defect and needs to be replaced to recover the workload provisioned there. This is currently underway. We estimate that this work will be completed within the next minutes.

  5. monitoring Jul 10, 2026, 12:41 AM UTC

    The last host and VMs have been recovered. We are setting this incident into monitoring status. Preliminary information on the Incident: Following a power grid outage, the site suffered a partial interruption of power, which impacted several datacenter support systems. The reason for this is under active investigation. This affected the availability of a subset of infrastructure components and hosts, subsequently impacting the VMs provisioned on them or dependent on those components. A full Root Cause Analysis (RCA) is currently being compiled and will be shared here once completed. Thank you for your patience.

  6. resolved Jul 10, 2026, 07:59 AM UTC

    We are marking this incident as resolved. The Root Cause Analysis will be published here once compiled.