IONOS Cloud Outage History

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.

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.

IONOS Cloud experienced a major incident where customers encountered connection problems to Kubernetes control planes and degraded functionality in their Managed Kubernetes service. The issue was caused by a defect in a configuration filtering mechanism that led to inadvertent configuration changes on affected resources. The incident lasted 65.3 hours and was resolved through a rollback of the identified changes, followed by monitoring to check for residual inconsistencies.

IONOS Cloud experienced a major outage affecting a high number of Managed Kubernetes control planes, primarily in the Frankfurt region, preventing customers from making workload changes to their K8s clusters. The incident lasted 13.9 hours before teams identified the root cause and applied a fix to restore all control planes. All services returned to normal operation with no further issues reported during the monitoring period.

IONOS Cloud's S3 Object Storage service experienced a 22.2-hour incident where all new access key creation failed, preventing users from generating new authentication credentials. Existing access keys continued to work normally throughout the incident, so users with previously created keys maintained access to their storage resources. The key creation functionality was restored and monitored before being fully resolved.

IONOS Cloud experienced a major incident affecting provisioning services, Data Center Designer, Cloud API, and Managed Kubernetes, causing increased processing times, timeouts, connection interruptions, and temporarily placing Kubernetes in read-only mode. The incident lasted 59.1 hours and required temporarily disabling provisioning services to implement fixes. The issue was resolved with provisioning functionality restored to normal operation, while existing virtual data center resources remained unaffected throughout the incident.

IONOS Cloud experienced network latency irregularities in their TXL datacenter that affected network services and caused increased error rates on the AI Modelhub. The network team identified the likely cause and deployed a mitigation after approximately 20 hours. The incident was resolved once no further anomalies were observed during peak usage times.

IONOS Cloud experienced a routing issue with their Cloud Support telephone system that caused customer calls to disconnect or route incorrectly. The incident affected customers' ability to reach support through documented phone numbers, requiring them to use an alternative direct dial number. The underlying cause was identified and fixed after 5.1 hours, restoring normal functionality to all documented support numbers.

IONOS Cloud experienced increased error rates and latency issues with S3 Object Storage buckets in the eu-central-1 region (DE/FRA location) for 9.4 hours. The problem was caused by localized resource contention on several storage nodes, which affected some users' access to object storage services. The engineering team performed maintenance on the affected storage cluster to resolve the resource contention, and the incident was resolved once error rates returned to normal levels.

IONOS Cloud experienced a network connectivity issue affecting one specific host in the FRA region for 50 minutes, while other hosts in the region remained operational. The problem was caused by database inconsistencies that occurred during a previous package update. The network team deployed a mitigation to restore connectivity and resolved the incident.