THIS IS A SCHEDULED EVENT Oct <var data-var='date'>19</var>, <var data-var='time'>16:00</var> - <var data-var='time'>18:00</var> UTC Sep <var data-var='date'>21</var>, <var data-var='time'>08:26</var> UTC Scheduled - Starting October 19, 2026, DBaaS will no longer allow provisioning of new PostgreSQL 14 clusters, ahead of PostgreSQL 14's upstream End of Life in November 2026. What this means for you: - From October 19, 2026, requests to create new PostgreSQL 14 clusters will be rejected. - Existing PostgreSQL 14 clusters are not affected — they remain fully functional and updatable until upgraded to a newer version. - Restoring a backup of an existing 14 cluster will continue to work and will still produce a PostgreSQL 14 cluster. - To provision new clusters after this date, please select a currently supported PostgreSQL version. No action is required for existing clusters. If you have automation that provisions PostgreSQL 14 clusters, please update it to target a supported version before October 19, 2026. Affected services: Database as a Service (DBaaS) Location: Global Services

Disabling New PostgreSQL 14 Cluster Creation

THIS IS A SCHEDULED EVENT Oct <var data-var='date'>12</var>, <var data-var='time'>16:00</var> - <var data-var='time'>18:00</var> UTC Sep <var data-var='date'>21</var>, <var data-var='time'>08:26</var> UTC Scheduled - Starting October 12, 2026, DBaaS will no longer allow provisioning of new MariaDB 10.6 clusters. MariaDB 10.6 reached its upstream End of Life in July 2026. What this means for you: - From October 12, 2026, requests to create new MariaDB 10.6 clusters will be rejected. - Existing MariaDB 10.6 clusters are not affected and remain fully supported — no forced upgrade. - You can continue to scale, reconfigure, and restore existing 10.6 clusters as before. - Restoring a backup of an existing 10.6 cluster will continue to work and will still produce a MariaDB 10.6 cluster. - To provision new clusters after this date, please select a currently supported MariaDB version. No action is required for existing clusters. If you have automation that provisions MariaDB 10.6 clusters, please update it to target a supported version before October 12, 2026. Affected services: Database as a Service (DBaaS) Location: Global Services

Disabling New MariaDB 10.6 Cluster Creation

THIS IS A SCHEDULED EVENT Oct <var data-var='date'>6</var>, <var data-var='time'>20:00</var> - <var data-var='time'>23:30</var> UTC Sep <var data-var='date'>29</var>, <var data-var='time'>07:55</var> UTC Scheduled - We will be conducting this maintenance to reduce the latency of publicly-routed traffic within our Berlin data center. Due to the systems' redundancy, no outage is expected, however there could be minimal packet loss as the routes re-convergence. Affected services: Network Location: Location DE/TXL

Update the routing of public traffic

Oct <var data-var='date'> 2</var>, <var data-var='time'>21:28</var> UTC Resolved - This incident has been resolved. Oct <var data-var='date'> 2</var>, <var data-var='time'>20:16</var> UTC Investigating - The DCD is currently unavailable. We are currently investigating this issue and will keep you updated.

DCD is Currently Unavailable

Oct <var data-var='date'> 2</var>, <var data-var='time'>13:55</var> UTC Identified - There may be periods of increased waiting times when calling IONOS Cloud Support by phone. We ask Customers and Partners to contact Cloud Support via the DCD Form or Email, instead. Thank you.

Cloud Support: Telephone Support reduced capacity

Sep <var data-var='date'>29</var>, <var data-var='time'>14:09</var> UTC Resolved - This incident has been resolved. Sep <var data-var='date'>29</var>, <var data-var='time'>11:07</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Sep <var data-var='date'>29</var>, <var data-var='time'>09:47</var> UTC Update - Our engineering team has identified the root cause of the Kubernetes service degradation and is actively working to restore full functionality. Customer workloads in affected locations may be experiencing disruptions, including unavailability of running services. Cluster management operations -- deploying, scaling, and accessing the Kubernetes API -- are also impacted. We will provide another update within 30 minutes. Sep <var data-var='date'>29</var>, <var data-var='time'>09:42</var> UTC Update - Our engineering team has identified the root cause of the Kubernetes service degradation and is actively working to restore full functionality. Customer workloads in affected locations may be experiencing disruptions, including unavailability of running services. Cluster management operations -- deploying, scaling, and accessing the Kubernetes API -- are also impacted. We will provide another update within 60 minutes. Sep <var data-var='date'>29</var>, <var data-var='time'>07:48</var> UTC Identified - Customers may experience connection problems to the control plane and degraded functionality of kubernetes

Partial Connectivity Degradation to Control Plane Affecting Kubernetes Operations

Sep <var data-var='date'>29</var>, <var data-var='time'>14:08</var> UTC Resolved - This incident has been resolved. Sep <var data-var='date'>29</var>, <var data-var='time'>11:35</var> UTC Identified - The AI Model Hub API is currently unavailable. We are working on restoring the service.

AI Model Hub API Unavailable

Sep <var data-var='date'>29</var>, <var data-var='time'>11:07</var> UTC Resolved - This incident has been resolved. Sep <var data-var='date'>29</var>, <var data-var='time'>09:58</var> UTC Identified - The AI Model Hub inference API is currently unavailable. API requests are returning 503 errors across all model endpoints (chat, embedding, rerank, image). This is related to the ongoing Kubernetes infrastructure issue in Frankfurt. Our team is actively working on restoration. We will provide another update within 30 minutes.

Sep <var data-var='date'>28</var>, <var data-var='time'>16:00</var> UTC Completed - The scheduled maintenance has been completed. Sep <var data-var='date'>28</var>, <var data-var='time'>14:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Aug <var data-var='date'>24</var>, <var data-var='time'>14:41</var> UTC Scheduled - Overview Following the successful automated migration of all DBaaS PostgreSQL clusters to our v2 infrastructure earlier this month, IONOS Cloud is proceeding with the final decommissioning of the legacy PostgreSQL API v1. The API v1 endpoints will be permanently disabled. Once disabled, any programmatic requests made to the v1 API will be rejected. Impact & Required Actions Because your underlying clusters have already been migrated, your databases will experience zero downtime during this API shutdown. However, you must ensure your management tools are updated to avoid disruption to your deployment workflows: - Endpoint Update: Ensure all scripts, Terraform configurations, and SDKs are pointing exclusively to the regional API v2 endpoints. - Authentication Switch: PostgreSQL API v2 does not support BASIC authentication. If you have not done so already, you must immediately switch your API and SDK authentication to TOKEN authentication. API v2 Benefits Reminder Migrating your tooling to API v2 grants you access to the new platform features: - Regional Endpoints: Lower-latency API access routed directly to your specific region. - Observability Integration: Access to forward cluster logs and metrics directly to IONOS Logging and Monitoring. - SSD Premium Infrastructure: Full management capabilities for the upgraded, high-performance SSD Premium storage tier. Affected services: Database as a Service (DBaaS) Location: Global Services

DBaaS PostgreSQL API v1 Decommissioning

Sep <var data-var='date'>26</var>, <var data-var='time'>11:11</var> UTC Resolved - After hours of monitoring incident the DCD is fully stable and operation Sep <var data-var='date'>26</var>, <var data-var='time'>03:04</var> UTC Update - We are continuing to monitor for any further issues. Sep <var data-var='date'>26</var>, <var data-var='time'>02:57</var> UTC Monitoring - The DCD is now available again, and we are monitoring the situation. Sep <var data-var='date'>26</var>, <var data-var='time'>00:25</var> UTC Investigating - The DCD is currently unavailable, displaying an endless "Loading DCD..." page. We are currently investigating this issue, and will keep you updated.

Sep <var data-var='date'>24</var>, <var data-var='time'>14:33</var> UTC Resolved - This incident has been resolved. Sep <var data-var='date'>24</var>, <var data-var='time'>11:57</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Sep <var data-var='date'>24</var>, <var data-var='time'>08:58</var> UTC Update - On top of the network issue in TXL, there may be delays in provisioning. Sep <var data-var='date'>24</var>, <var data-var='time'>08:43</var> UTC Investigating - We are writing to inform you that we have been experiencing sporadic connection issues and substantial delays on packet delivery. Network technicians have started working on the occurrence immediately after detection and will isolate the problem and solve the issue as quick as possible. However, it is possible that there will be a certain degradation in connection quality affecting individual virtual resources. We will inform you as soon as the functionality has been restored.

Network packet loss in TXL / Provisioning delays

Sep <var data-var='date'>24</var>, <var data-var='time'>05:43</var> UTC Resolved - The incident has been mitigated successfully at approx. 19:00 UTC, 23.09.2026. The teams involved are currently investigating the root cause and we will publish a report here once it is compiled. Sep <var data-var='date'>23</var>, <var data-var='time'>18:32</var> UTC Identified - We have successfully identified and mitigated a high-latency condition in our core storage infrastructure that temporarily impacted the responsiveness of the Kubernetes control plane. Our engineering team is currently executing a phased reconciliation and rollout process to gracefully restart the management instances and restore full functionality. Existing application workloads continue to run normally and remain unaffected. Sep <var data-var='date'>23</var>, <var data-var='time'>17:15</var> UTC Investigating - We are currently experiencing control plane instability affecting our managed Kubernetes clusters. While existing application workloads continue to run normally, administrative and management capabilities are currently degraded. Our engineering team is actively working on a resolution, and we will provide updates as new information becomes available.

Managed Kubernetes - Intermittent Control Plane Unavailability

Sep <var data-var='date'>21</var>, <var data-var='time'>08:31</var> UTC Resolved - Additional GPU capacity has been successfully provisioned, and standard availability is now restored. We are removing this note. Jun <var data-var='date'>18</var>, <var data-var='time'>15:04</var> UTC Identified - We are currently experiencing exceptionally high demand for GPU servers, which has temporarily limited our available capacity. As a result, you may encounter provisioning errors when attempting to create a new GPU server or start an existing one. What You Can Do - Try again later: We cannot provide an exact timeline for when capacity will be added. However, we are monitoring the situation closely and will update this status page once substantial free capacity becomes available. - Provision a smaller GPU server: Because availability fluctuates rapidly, we cannot guarantee which specific sizes are currently open. Attempting to provision a smaller instance may increase your chances of success. - If you currently have a provisioned and running GPU server, do not shut it down. Due to the low supply, freed resources may be immediately allocated to other customers, and you will likely be unable to restart your server. Next Steps & Resolution Resolving this resource constraint has high priority. Our teams are working to increase capacity to meet demand as quickly as possible. We sincerely appreciate your patience and understanding.

GPU Server Provisioning: Supply currently limited

Sep <var data-var='date'>21</var>, <var data-var='time'>07:24</var> UTC Resolved - We are marking this incident as resolved Sep <var data-var='date'> 9</var>, <var data-var='time'>02:19</var> UTC Monitoring - DBaaS service has recovered, as well. We are setting the incident into Monitoring status, while the teams are ensuring that all affected services operate normally. Sep <var data-var='date'> 9</var>, <var data-var='time'>01:07</var> UTC Update - We are currently investigating potential residual impact on DBaaS Services. Compute and Block Storage have reported full recovery. Sep <var data-var='date'> 9</var>, <var data-var='time'>00:20</var> UTC Update - Our Network Team has identified an issue related to a recent router replacement and applied a mitigation. Compute and Storage systems are showing signs of recovery. We are actively monitoring the environment until all services are fully restored Sep <var data-var='date'> 8</var>, <var data-var='time'>23:59</var> UTC Update - We are continuing to work on a fix for this issue. Sep <var data-var='date'> 8</var>, <var data-var='time'>23:56</var> UTC Identified - We see indications of a recurrence of the issue and are setting the status page to active. Our Network Team is investigating and we will share updates here as they become available. The issue is currently negatively affecting Compute, Provisioning and Network Components. Sep <var data-var='date'> 8</var>, <var data-var='time'>23:43</var> UTC Monitoring - We are currently investigating network connectivity alerts related to our TXL datacenter. While connectivity appears to be restored already, we are actively monitoring the situation to ensure stability. We will provide updates as new information becomes available.

TXL - Network Connectivity

Sep <var data-var='date'> 8</var>, <var data-var='time'>21:57</var> UTC Resolved - We have people available now, Support is reachable as usual. Sep <var data-var='date'> 8</var>, <var data-var='time'>14:15</var> UTC Identified - While phone support will generally be available, our Support capacity is reduced due to multiple cases of sick leave. We want to inform you that our phone support will be limited during the following time slots, leading to increased response times on the phone channel. In these cases, please reach out per email. Thank you.

Cloud Support: Limited Phone Support Availability

Sep <var data-var='date'> 8</var>, <var data-var='time'>06:31</var> UTC Resolved - We managed to fully re-establish our service, Support is back. thank you for your patience. Sep <var data-var='date'> 7</var>, <var data-var='time'>06:16</var> UTC Identified - We still run short on coverage of service, and we are currently doing changes on our ticketing system. So we kindly ask for your understanding if Support responses are not as timely as you are accustomed to. Thank you. Sep <var data-var='date'> 4</var>, <var data-var='time'>16:53</var> UTC Investigating - While phone support will generally be available, our capacity is reduced due to multiple cases of sick leave. We want to inform you that our phone support will be limited during the following time slots, leading to increased response times on the phone channel. In these cases, please reach out per email. Thank you.

Sep <var data-var='date'> 3</var>, <var data-var='time'>13:39</var> UTC Resolved - The increased latency affecting S3 Object Storage in eu-central-1 has been resolved. Response times have returned to normal levels. We will continue to monitor the service. Sep <var data-var='date'> 3</var>, <var data-var='time'>08:27</var> UTC Monitoring - Response times for Object Storage in eu-central-1 have improved significantly and continue to stabilize. We are closely monitoring system performance. We will provide further updates as remediation progresses. Sep <var data-var='date'> 1</var>, <var data-var='time'>15:18</var> UTC Update - Our engineering teams have identified a path to remediation. Initial measures have been applied, improving the situation for some services. Customers using Object Storage in eu-central-1 may continue to experience elevated latency, which may vary in severity. Work continues on a comprehensive fix. We will provide further updates Aug <var data-var='date'>31</var>, <var data-var='time'>17:08</var> UTC Update - We see recurring latency spikes affecting our S3 service in eu-central-1. The Object Storage and Network teams are jointly investigating. Although a technical root cause remains undetermined at this time, our highest priority is implementing measures to mitigate the frequency and amplitude of the spikes. We appreciate your patience and will keep you informed. Aug <var data-var='date'>27</var>, <var data-var='time'>12:00</var> UTC Identified - The issue has been identified and a fix is being implemented. Aug <var data-var='date'>26</var>, <var data-var='time'>09:53</var> UTC Investigating - We are currently investigating increased latency affecting S3 Object Storage in the eu-central-1 region. Some customers may experience slow response times for read and write operations. Our engineering team is actively working on resolving the issue. We will provide updates as more information becomes available.

Object Storage - Increased latency in eu-central-1

Sep <var data-var='date'> 1</var>, <var data-var='time'>16:12</var> UTC Resolved - This incident has been resolved. Sep <var data-var='date'> 1</var>, <var data-var='time'>15:01</var> UTC Monitoring - Wir konnten das Problem beheben, sodass die neue Region nun für alle Verträge verfügbar ist. Wir monitoren, ob es dazu noch weitere Rückmeldungen gibt. Sep <var data-var='date'> 1</var>, <var data-var='time'>13:36</var> UTC Identified - For our partners with subcontracts: We found that subcontracts cannot access the new Frankfurt location "de/fra/1". We are currently working on a fix to make this available, we will keep you informed when it's done.

Partner Subcontracts can not access new location de/fra/1

Aug <var data-var='date'>31</var>, <var data-var='time'>17:03</var> UTC Resolved - We are marking this incident as resolved. Our network team is investigating negative impact on the IAM Services caused by a change rollout. We will update the Status Page once the root cause has been established. Aug <var data-var='date'>31</var>, <var data-var='time'>15:52</var> UTC Monitoring - The DCD is now available again, and we are monitoring the situation. Aug <var data-var='date'>31</var>, <var data-var='time'>15:35</var> UTC Investigating - The DCD is currently unavailable, displaying an endless "Loading DCD..." page. We are currently investigating this issue, and will keep you updated.

Aug <var data-var='date'>31</var>, <var data-var='time'>17:00</var> UTC Completed - The scheduled maintenance has been completed. Aug <var data-var='date'>17</var>, <var data-var='time'>05:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Aug <var data-var='date'>12</var>, <var data-var='time'>12:34</var> UTC Scheduled - IONOS Cloud will perform an automated migration of all DBaaS PostgreSQL clusters from the v1 infrastructure to our upgraded v2 infrastructure. This upgrade introduces several key platform enhancements, including lower-latency regional API endpoints, optional native Observability integration (IONOS Logging and Monitoring), and mandatory SSD Premium storage for higher, consistent I/O performance. What this means for you: - Automated Migration: The migration is fully managed by IONOS Cloud. No manual migration steps are required for your database clusters. - Expected Downtime: This brief downtime (typically lasting a few seconds) applies per individual cluster only during its specific migration window. It does not impact the availability of the entire DBaaS service. We recognize that even brief unavailability can affect your operations, and ensuring your service continuity remains our highest priority throughout this transition. - Database Connections: Your cluster connection endpoints will remain unchanged. Your applications will automatically reconnect once the migration process finishes. Required Actions for API & Programmatic Users If you manage your PostgreSQL clusters programmatically via APIs, SDKs, or Infrastructure as Code (IaC) tools (e.g., Terraform), you must take action before the migration begins: - Switch to Token Authentication: PostgreSQL v2 does not support BASIC authentication for cluster management. You must switch your tools to use TOKEN authentication before the 14th of August, 2026, to prevent management access disruption. - Instructions for generating authentication tokens can be found in the IONOS Cloud Token Manager Documentation (see https://docs.ionos.com/cloud/set-up-ionos-cloud/management/identity-access-management/token-manager for more information). - Note: If you already use TOKEN authentication or do not manage your clusters programmatically, no action is required. Important Storage & Price Changes Notice Regarding Infrastructure Upgrades & Fees: To ensure peak performance, all PostgreSQL v2 clusters run exclusively on SSD Premium storage. - Clusters currently running on HDD or SSD Standard storage will be automatically upgraded to SSD Premium as part of this migration and will subsequently be billed at the standard SSD Premium rate. - Optional usage of the new IONOS Logging and Monitoring integration is billed separately. As these infrastructure updates constitute changes to the fees applicable to your service, you retain the right to terminate your contract without notice upon the effectiveness of these changes, in accordance with our General Terms and Conditions. For further technical details regarding the new infrastructure features, please consult the official IONOS Cloud DBaaS PostgreSQL documentation. Affected services: Database as a Service (DBaaS) Location: Global Services

Automated DBaaS PostgreSQL v1 to v2 Infrastructure Migration

Aug <var data-var='date'>31</var>, <var data-var='time'>16:00</var> UTC Completed - The scheduled maintenance has been completed. Aug <var data-var='date'>31</var>, <var data-var='time'>14:01</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Aug <var data-var='date'>24</var>, <var data-var='time'>14:41</var> UTC Scheduled - Overview IONOS is finalizing the transition from MariaDB API v1 to the new MariaDB API v2. The automated migration of your underlying database clusters is handled entirely by IONOS with zero downtime, and your existing connection strings remain unchanged. However, MariaDB API v1 will be completely deprecated on August 31, 2026. If you manage your infrastructure via our API, Terraform, or SDKs, you must update your tooling to the v2 endpoints before this date to prevent disruptions to your deployment and management workflows. Deprecation Timeline - Aug 17, 2026 v1 Cluster Creation Disabled - ✅ Passed - Aug 24-27, 2026 MariaDB API v1 to v2 Automatic Migration - Upcoming - August 31, 2026 MariaDB API v1 End of Life - ⚠️ Upcoming Required Customer Actions While your databases remain online and accessible during the platform upgrade, you must complete the following updates by August 31, 2026: - API Integrations: Transition all automated scripts and calls to the MariaDB v2 API endpoint.Infrastructure as Code: Update your Terraform configurations to utilize the new MariaDB v2 provider. - SDKs: Upgrade any custom application integrations to the latest MariaDB v2 SDK. - Database Version Upgrades: If you are currently running MariaDB 10.6, you must initiate an upgrade to a supported version (10.11, 11.4, 11.8, or 12.3) before the end of the month, as platform support for 10.6 is ending. Benefits of the v2 Platform - Extended Backups: Configure backup retention for up to 365 days, enabling long-term point-in-time recovery. - Latest Versions: Full support for MariaDB 11.4, 11.8 and 12.3. - IONOS Observability: Optional integration to closely monitor database performance metrics (Observability usage is billed separately). Affected services: Database as a Service (DBaaS) Location: Global Services

IONOS MariaDB API v1 Full Deprecation

Aug <var data-var='date'>31</var>, <var data-var='time'>16:00</var> UTC Completed - The scheduled maintenance has been completed. Aug <var data-var='date'>31</var>, <var data-var='time'>14:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Aug <var data-var='date'>13</var>, <var data-var='time'>12:32</var> UTC Scheduled - Overview We are officially transitioning IONOS In-Memory DB to a new, enhanced API v2 architecture. The new v2 platform is powered by Valkey (an open-source key/value datastore maintained by the Linux Foundation) and provides significant upgrades to snapshot retention and observability. Because of the architectural changes, automatic migration is not possible. All customers must manually migrate their data and update their endpoints to v2 before the end-of-life deadline to avoid service interruption. Deprecation Timeline v1 Cluster Creation Disabled - August 4, 2026 - It is no longer possible to provision new In-Memory DB v1 clusters. Existing clusters continue to operate normally. In-Memory DB v1 End of Life - August 31, 2026 - Critical Deadline: Full decommissioning of API v1. All remaining v1 instances will be permanently switched off on this date. New Snapshot Pricing Applies - September 1, 2026 - Standard pricing for the enhanced v2 snapshot features takes effect. (All v2 snapshots are included at no additional cost prior to this date). Required Migration Steps To ensure your applications continue to run smoothly, please complete the following migration procedure before August 31, 2026: 1. Provision a v2 Instance: API, DCD and SDK access available now - Create a new In-Memory DB v2 instance using the v2 API documentation. You can select Valkey versions 8, 8.1, or 9. 2. Migrate Your Data: Only if data persistence is required - Load your existing v1 data into the new v2 instance. Because Valkey is compatible with standard Redis clients and tools, you can use your existing toolset for this transfer. 3. Update Application Endpoints - Update your application connection strings to point to the new v2 instance. No application code changes are required, as Valkey acts as a drop-in replacement. What to Expect in In-Memory DB v2 - Powered by Valkey: Built on the robust, open-source datastore supported by the Linux Foundation. Fully compatible with standard Redis clients. - Enhanced Snapshots: Move from single-snapshot limitations to multi-snapshot retention. Keep backups for up to 365 days for long-term point-in-time recovery. (Note: New snapshot pricing applies starting Sept 1, 2026, reflecting the upgraded infrastructure). - IONOS Observability (Optional): Seamlessly integrate your database with IONOS Observability to track performance metrics and logs. This feature is entirely optional and billed separately upon enablement. If you require assistance with your migration plan or have any questions about the transition to Valkey, please refer to https://docs.ionos.com/cloud/databases/in-memory-db/how-tos/migrate-from-v1-v2 or contact our Customer Support team. Affected services: Database as a Service (DBaaS) Location: Global Services

Action Required: IONOS In-Memory DB API v1 Full Deprecation

Aug <var data-var='date'>28</var>, <var data-var='time'>06:00</var> UTC Completed - The scheduled maintenance has been completed. Aug <var data-var='date'>24</var>, <var data-var='time'>14:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Aug <var data-var='date'>13</var>, <var data-var='time'>10:13</var> UTC Scheduled - Overview We are rolling out an important upgrade to IONOS MariaDB. All existing MariaDB clusters utilizing API v1 will be automatically migrated to the new MariaDB API v2. This migration unlocks several new capabilities, including support for newer MariaDB versions, extended backup retention (up to 365 days for point-in-time recovery), and integration with IONOS Observability for performance monitoring. Customer Impact & Migration Process - Zero Downtime: Your databases will remain fully accessible throughout the entire migration process. - No Connection Changes: Your existing connection strings will continue to work without any modifications. - Automated: The migration of the cluster itself requires no manual intervention on your part. Key Dates & Milestones - August 17, 2026 - v1 Cluster Creation Disabled: It will no longer be possible to provision new MariaDB v1 clusters. - August 31, 2026 - MariaDB API v1 End of Life: API v1 will be fully deprecated. All integrations must be updated to v2. Action Required (Post-Migration) While the cluster migration is automated, you will need to update your integrations and tools to interface with the new v2 environment before the August 31, 2026 deadline: - API Integrations: Update your scripts and API calls to use the new MariaDB v2 API. - Infrastructure as Code: Update your Terraform configurations to utilize the MariaDB v2 provider. - SDKs: Upgrade any application integrations to the MariaDB v2 SDK. - Version Upgrades (If applicable): If you are currently running MariaDB 10.6, please plan an upgrade to a higher version (10.11, 11.4, 11.8, or 12.3) before the end of August 2026. What's New in MariaDB API v2? - New Version Support: Added support for MariaDB 11.4, 11.8 and 12.3 alongside 10.6 and 10.11. - Advanced Backups: Maintain backups with a retention period of up to 365 days, enabling long-term point-in-time recovery. - Observability Integration: Opt-in to connect MariaDB v2 with IONOS Observability for detailed performance metrics (Note: Observability usage is billed separately). If you experience any issues or have questions regarding this migration, please reach out to our support team at support@cloud.ionos.com. Affected services: Database as a Service (DBaaS) Location: Global Services

Automated Migration to IONOS MariaDB API v2

Aug <var data-var='date'>27</var>, <var data-var='time'>17:00</var> UTC Completed - The scheduled maintenance has been completed. Aug <var data-var='date'>27</var>, <var data-var='time'>14:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Aug <var data-var='date'>25</var>, <var data-var='time'>17:12</var> UTC Scheduled - As part of our ongoing initiative to enhance the scalability, performance, and stability of our Managed Kubernetes Control Plane, we are conducting additional maintenance today. During this window, you may experience brief periods of service degradation when accessing the Kubernetes API. These interruptions typically last under two minutes and should not exceed five minutes. Your worker nodes and running workloads will remain entirely unaffected. No action is required on your part. Affected services: Managed Kubernetes Location: Location DE/FRA

Scheduled maintenance: Managed Kubernetes

Aug <var data-var='date'>26</var>, <var data-var='time'>17:00</var> UTC Completed - The scheduled maintenance has been completed. Aug <var data-var='date'>26</var>, <var data-var='time'>14:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Aug <var data-var='date'>25</var>, <var data-var='time'>17:13</var> UTC Scheduled - As part of our ongoing initiative to enhance the scalability, performance, and stability of our Managed Kubernetes Control Plane, we are conducting additional maintenance today. During this window, you may experience brief periods of service degradation when accessing the Kubernetes API. These interruptions typically last under two minutes and should not exceed five minutes. Your worker nodes and running workloads will remain entirely unaffected. No action is required on your part. Affected services: Managed Kubernetes Location: Location DE/FRA

Is IONOS Cloud down?

IONOS Cloud status is DEGRADED

Components with issues

Lastest published events

DCD is Currently Unavailable

Cloud Support: Telephone Support reduced capacity

Partial Connectivity Degradation to Control Plane Affecting Kubernetes Operations

IONOS Cloud Services, Components and Regions

Recent IONOS Cloud events

Disabling New PostgreSQL 14 Cluster Creation

Disabling New MariaDB 10.6 Cluster Creation

Update the routing of public traffic

DCD is Currently Unavailable

Cloud Support: Telephone Support reduced capacity

Partial Connectivity Degradation to Control Plane Affecting Kubernetes Operations