Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

IONOS Cloud Outage History

Every past IONOS Cloud outage tracked by IsDown, with detection times, duration, and resolution details.

There were 261 IONOS Cloud outages since September 2020. The 80 outages from the last 12 months are summarized below, with incident details, duration, and resolution information.

Minor June 1, 2026

June 2026: Limited access to provisioning services

Detected Jun 1, 2026 10:10 AM EDT · Resolved Jun 2, 2026 7:32 AM EDT · Duration about 21 hours

IONOS Cloud experienced a 21.4-hour incident affecting provisioning services, causing increased processing times for orders initiated via Data Center Designer or API, with occasional connection losses to the Data Center Designer. Existing virtual data center resources remained accessible and unaffected throughout the incident. The issue was resolved after implementing a fix and monitoring the results.

Minor May 29, 2026

May 2026: AI Model Hub: Increased Error Rate

Detected May 29, 2026 4:23 PM EDT · Resolved Jun 1, 2026 1:08 PM EDT · Duration 3 days

IONOS Cloud's AI Model Hub experienced increased latency and error rates due to significant load over a 68.8-hour period. The Mistral Small 24B Instruct model was particularly affected by high load, causing slow response times and timeouts for users. The team resolved the incident by removing performance bottlenecks and addressing the load issues.

Minor May 28, 2026

May 2026: Connectivity Degradation: VPN Gateways

Detected May 28, 2026 6:43 AM EDT · Resolved May 28, 2026 1:23 PM EDT · Duration about 7 hours

IONOS Cloud experienced a connectivity issue affecting VPN Gateways that lasted 6.7 hours. The VPN team identified and mitigated the problem, with all affected gateways recovering. The incident was resolved and is being investigated for potential links to previous maintenance work on the VPN gateways.

Major May 20, 2026

May 2026: Network Outage in Worcester

Detected May 20, 2026 8:19 AM EDT · Resolved May 20, 2026 5:39 PM EDT · Duration about 9 hours

IONOS Cloud experienced a major network outage in Worcester that caused multiple customer network interface cards (NICs) to go down, resulting in complete connectivity loss for affected instances. The technical team identified the root cause and resolved the issue by migrating several virtual machines to restore network connectivity. The incident lasted 9.4 hours before being fully resolved with continued monitoring for stability.

Minor May 15, 2026

May 2026: Partial Connectivity Degradation to Control Plane Affecting Kubernetes Operations in Frankfurt (de/fra)

Detected May 15, 2026 8:18 AM EDT · Resolved May 19, 2026 12:27 PM EDT · Duration 4 days

IONOS Cloud experienced partial connectivity degradation affecting Kubernetes control planes in the Frankfurt region, preventing workload changes for several customers over approximately 100 hours. The issue was caused by a DDoS attack targeting customers on their infrastructure, which created bottlenecks leading to intermittent reachability problems and increased latency between Kubernetes etcd nodes. The incident was resolved after implementing a fix and monitoring the results.

Minor May 15, 2026

May 2026: Network packet loss

Detected May 15, 2026 7:59 AM EDT · Resolved May 19, 2026 12:19 PM EDT · Duration 4 days

IONOS Cloud experienced network packet loss and connection delays caused by a DDoS attack on customer infrastructure, affecting individual virtual resources with degraded connection quality. The incident lasted approximately 100 hours while network technicians worked to isolate and resolve the issue. The problem was resolved after implementing countermeasures to mitigate the attack, though intermittent link saturation caused some packet loss during the response period.

Minor May 13, 2026

May 2026: Provisioning Service Degradation in FKB

Detected May 13, 2026 11:33 AM EDT · Resolved May 18, 2026 3:39 AM EDT · Duration 5 days

IONOS Cloud experienced provisioning service degradation in their Karlsruhe datacenter affecting Virtual Data Centers (VDCs) that were impacted by a previous storage incident. Users encountered error code VDC-5-12 when attempting to create or modify resources, while existing VMs remained operational throughout the incident. The issue was resolved after 112 hours once redundancy was fully restored and provisioning limitations were removed.

Minor May 12, 2026

May 2026: Suspected Issues with USt- / VAT ID verification

Detected May 12, 2026 4:50 AM EDT · Resolved May 13, 2026 2:58 AM EDT · Duration about 22 hours

IONOS Cloud's automated accounting system erroneously sent emails to multiple customers claiming their VAT/Umsatzsteuer ID numbers could not be verified. The incident was identified as a false alarm with no actual verification issues or required customer actions. All affected customers were contacted directly via email once the 22-hour incident was resolved.

Major May 12, 2026

May 2026: Availability of storage service partially limited in Karlsruhe

Detected May 12, 2026 2:15 AM EDT · Resolved May 18, 2026 3:51 AM EDT · Duration 6 days

IONOS Cloud experienced a major storage service outage in their Karlsruhe region lasting over 6 days, caused by defective hardware that required physical replacement and extensive data synchronization. The incident affected virtual machines and storage provisioning, with some VMs going into "shutoff" state and requiring manual restart requests through support tickets. The service was fully restored after hardware replacement, firmware updates, VM recovery, and complete storage redundancy restoration.

Minor May 11, 2026

May 2026: Partial Connectivity Degradation to Control Plane Affecting Kubernetes Operations

Detected May 11, 2026 1:53 PM EDT · Resolved May 11, 2026 5:19 PM EDT · Duration about 3 hours

IONOS Cloud experienced partial connectivity issues with their Managed Kubernetes control plane, causing degraded functionality for some customers. The incident affected Kubernetes operations and lasted approximately 3.4 hours. The issue was resolved after implementing a fix and monitoring the results.