THIS IS A SCHEDULED EVENT Jul <var data-var='date'>16</var>, <var data-var='time'>14:00</var> - <var data-var='time'>16:00</var> UTC Jul <var data-var='date'> 3</var>, <var data-var='time'>10:59</var> UTC Scheduled - We will test switching the provisioning to our geo‑redundant setup to ensure the standby location is fully functional. Expected impact: * Cloud API reduced availability for some minutes during the maintenance window * increased processing times for provisioning requests We apologize for the inconvenience. Affected services: Managed Kubernetes, Provisioning Location: APIs and Frontends, Global Services, Location DE/FKB, Location DE/FRA, Location DE/FRA/2, Location DE/TXL, Location ES/VIT, Location FR/PAR, Location GB/BHX, Location GB/GLO, Location GB/LHR, Location US/EWR, Location US/LAS, Location US/MCI

Switch to Berlin located provisioning stack

THIS IS A SCHEDULED EVENT Jul <var data-var='date'>15</var>, <var data-var='time'>10:00</var> - <var data-var='time'>12:00</var> UTC Jun <var data-var='date'>19</var>, <var data-var='time'>09:44</var> UTC Scheduled - Details: During this scheduled maintenance window, we will permanently disable the creation of new DBaaS PostgreSQL clusters via API v1. This is a mandatory step in our transition to the upgraded PostgreSQL v2 infrastructure, which offers enhanced I/O performance, reduced management latency, and native observability tools. What does this mean for you? New Deployments: Any automated scripts attempting to provision new PostgreSQL clusters using API v1 after this window will receive an error and fail. Existing Clusters: There is no impact on existing PostgreSQL v1 clusters during this maintenance. They will remain fully operational and accessible. Required Actions If you manage your database infrastructure programmatically, please perform the following steps to ensure uninterrupted operations: Migrate to API v2: Update your deployment workflows, scripts, and IaC configurations to use API v2 for all future PostgreSQL cluster provisions. API v2: https://api.ionos.com/docs/postgresql/v2/ Switch to Token Authentication: PostgreSQL v2 does not support Basic Authentication. To maintain management access, ensure your tools are updated to use Token Authentication. (Note: Token authentication is already supported on v1 and can be implemented immediately). Looking Ahead: Automatic Cluster Migrations Existing PostgreSQL v1 clusters will be automatically migrated to the v2 infrastructure by IONOS in the near future. This maintenance window only blocks the creation of new v1 clusters. You will receive a separate, official email communication detailing your specific cluster migration window and what to expect. Affected services: Database as a Service (DBaaS) Location: APIs and Frontends, Global Services

Disabling PostgreSQL Cluster Creation via API v1

Jul <var data-var='date'> 7</var>, <var data-var='time'>19:00</var> UTC Completed - The scheduled maintenance has been completed. Jul <var data-var='date'> 7</var>, <var data-var='time'>17:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jun <var data-var='date'>30</var>, <var data-var='time'>13:33</var> UTC Scheduled - We will perform a network optimization maintenance in which some filters will update. This is generally does not lead to customer facing service degradation, however in some cases - due to network convergence - there can be some packet loss for up to 2-3 seconds. If you have multiple workloads on different hosts, then this impact can be experienced multiple times. Affected services: Network Location: Location DE/FKB, Location ES/VIT, Location GB/BHX, Location GB/LHR

Network Maintenance

Jul <var data-var='date'> 7</var>, <var data-var='time'>10:09</var> UTC Resolved - This incident has been resolved. Jul <var data-var='date'> 1</var>, <var data-var='time'>19:07</var> UTC Monitoring - Incident involving degradation of the control plane has been resolved and we are monitoring the situation. Jun <var data-var='date'>30</var>, <var data-var='time'>22:55</var> UTC Update - The situation appears to have stabilized for the time being. An internal investigation into the exact root cause is ongoing. Jun <var data-var='date'>30</var>, <var data-var='time'>21:08</var> UTC Investigating - Customers may experience connection problems to the control plane and degraded functionality of kubernetes

Partial Control Plane Outage Affecting Kubernetes Operations

Jul <var data-var='date'> 7</var>, <var data-var='time'>09:36</var> UTC Update - Still, the global provisioning system is not working properly. Therefore, all other dependencies, like K8s and managed products, are affected, too. We know this is affecting customer setups, and that urgent changes are not processed properly, and we apologize for the inconvenience. We identified possible distractors, but fixing this is a complex task, with need to involve and coordinate several technical teams. We are working with highest prio to get the provisioning back working, and we will let you know asap on any progress. Jul <var data-var='date'> 6</var>, <var data-var='time'>10:14</var> UTC Identified - We are currently investigating instances of performance degradation in job processing. Our Provisioning Team is currently working on fixing the root cause of these events.

Provisioning: Degraded Performance in Job Processing

Jul <var data-var='date'> 5</var>, <var data-var='time'>17:27</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Jul <var data-var='date'> 5</var>, <var data-var='time'>16:02</var> UTC Update - We are continuing to work on a fix for this issue. Jul <var data-var='date'> 5</var>, <var data-var='time'>14:47</var> UTC Identified - We are currently experiencing increased processing times for provisioning orders initiated via the Data Center Designer (DCD) or API. Additionally, intermittent connectivity issues may occur when accessing the Data Center Designer or API. Please note that this issue is not limited to Managed Kubernetes services and may impact all cloud workloads involving new provisioning or modifications. Important: The availability, stability, and accessibility of your existing running virtual data center resources remain entirely unaffected. Our engineering teams are actively working to resolve the issue. We will provide a further update as soon as full functionality has been restored.

Partial Connectivity Degradation to Control Plane Affecting Kubernetes Operations

Jul <var data-var='date'> 5</var>, <var data-var='time'>11:50</var> UTC Resolved - The provisioning queue looks healthy again, and all services have been reactivated. Jul <var data-var='date'> 5</var>, <var data-var='time'>11:32</var> UTC Update - We are currently seeing progress in provisioning, and the DCD maintenance page has been removed from the DCD. Jul <var data-var='date'> 5</var>, <var data-var='time'>08:31</var> UTC Update - We are continuing to investigate this issue. Jul <var data-var='date'> 5</var>, <var data-var='time'>08:14</var> UTC Update - We are continuing to investigate this issue. Jul <var data-var='date'> 5</var>, <var data-var='time'>08:12</var> UTC Update - We are continuing to investigate this issue. Jul <var data-var='date'> 5</var>, <var data-var='time'>08:08</var> UTC Update - For Investigation we set mk8s api to maintenance mode (read-only) Jul <var data-var='date'> 5</var>, <var data-var='time'>08:04</var> UTC Update - We are continuing to investigate this issue. Jul <var data-var='date'> 5</var>, <var data-var='time'>08:01</var> UTC Investigating - We are currently investigating instances of performance degradation in job processing. Our Provisioning Team is currently investigating the root cause of these events.

Jul <var data-var='date'> 3</var>, <var data-var='time'>09:16</var> UTC Resolved - Our Provisioning went back operational yesterday around 16:30 UTC. Further monitoring showed no issues anymore, so this incident was resolved. Jul <var data-var='date'> 2</var>, <var data-var='time'>13:51</var> UTC Identified - We found the root cause and implemented mitigation measures. We expect the errors to decrease significantly now. We will let you know asap when we consider the situation being back to normal. Jul <var data-var='date'> 2</var>, <var data-var='time'>08:30</var> UTC Investigating - Currently we are facing increased provisioning problems resulting in error code [VDC-5-0]. We understand the impact, and our teams are investigating the root cause to get this fixed asap. Please postpone your provisioning until we resolve the issue, we will inform you of any updates.

Provisioning issues in FRA and TXL

Jul <var data-var='date'> 2</var>, <var data-var='time'>13:50</var> UTC Resolved - Phone Support is now available again Jul <var data-var='date'> 2</var>, <var data-var='time'>07:01</var> UTC Update - We are continuing to investigate this issue. Jul <var data-var='date'> 2</var>, <var data-var='time'>07:00</var> UTC Investigating - IONOS Cloud Support is temporarily unavailable via phone. We ask Customers and Partners to contact Cloud Support via the DCD Form or Email, instead.

Cloud Support: Telephone Support temporarily unavailable

Jun <var data-var='date'>30</var>, <var data-var='time'>19:00</var> UTC Completed - The scheduled maintenance has been completed. Jun <var data-var='date'>30</var>, <var data-var='time'>17:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jun <var data-var='date'>24</var>, <var data-var='time'>07:55</var> UTC Scheduled - We are performing a phased upgrade of our network configuration across all locations. This update includes firewall and cluster configuration changes required to integrate new frontend nodes. There should be no impact, but on rare occasions a brief packet loss of a few seconds may occur. Affected services: Network Location: Location DE/FRA, Location DE/FRA/2, Location DE/TXL

Scheduled Network Configuration Update

Jun <var data-var='date'>29</var>, <var data-var='time'>19:00</var> UTC Completed - The scheduled maintenance has been completed. Jun <var data-var='date'>29</var>, <var data-var='time'>17:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jun <var data-var='date'>24</var>, <var data-var='time'>07:51</var> UTC Scheduled - We are performing a phased upgrade of our network configuration across all locations. This update includes firewall and cluster configuration changes required to integrate new frontend nodes. There should be no impact, but on rare occasions a brief packet loss of a few seconds may occur. Affected services: Network Location: Location DE/FKB, Location ES/VIT, Location FR/PAR, Location GB/BHX, Location GB/GLO, Location GB/LHR

Jun <var data-var='date'>23</var>, <var data-var='time'>14:26</var> UTC Resolved - This incident has been resolved. Jun <var data-var='date'>23</var>, <var data-var='time'>11:33</var> UTC Monitoring - A fix has been implemented and we are monitoring the service. Jun <var data-var='date'>23</var>, <var data-var='time'>10:26</var> UTC Update - We are continuing to investigate this issue. Jun <var data-var='date'>23</var>, <var data-var='time'>10:24</var> UTC Investigating - Due to an internal network issue that is currently being investigated, all models are currently unavailable.

AI Model Hub - All models currently unavailable

Jun <var data-var='date'>23</var>, <var data-var='time'>11:00</var> UTC Completed - The scheduled maintenance has been completed. Jun <var data-var='date'>23</var>, <var data-var='time'>08:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jun <var data-var='date'>18</var>, <var data-var='time'>12:12</var> UTC Scheduled - We will perform a network optimization maintenance in which some filters will update. This is generally does not lead to customer facing service degradation, however in some cases - due to network convergence -, there can be some packet loss for 2-3 seconds. If you have multiple workloads on different hosts, then this impact can be experienced multiple times. Affected services: Network Location: Location US/EWR, Location US/LAS, Location US/MCI

Jun <var data-var='date'>22</var>, <var data-var='time'>19:30</var> UTC Completed - The scheduled maintenance has been completed. Jun <var data-var='date'>22</var>, <var data-var='time'>18:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jun <var data-var='date'>19</var>, <var data-var='time'>09:43</var> UTC Scheduled - We are performing a routine network optimization for our Database Quota Service—the system that manages resource limits for your database environments. To do this, we are updating the "digital maps" (technically known as BGP) that guide traffic to our servers. This ensures your service remains fast and reliable by directing your requests through the most efficient paths. We are proceeding with network routing updates for the Database Quota Service across the following locations: Germany: Berlin (txl), Frankfurt[fra] Impact & Mitigation: This update is designed to run in the background. Your service will remain online throughout the process. Potential Latency: You may notice a brief, minor increase in response time (a "latency spike") for a few seconds. Risk Assessment: While we expect a seamless transition, there is a very small chance of a minimal interruption if the automatic connection setup requires manual adjustment. Affected services: Network Location: Location DE/FRA, Location DE/TXL

New BGP sessions for DB service

Jun <var data-var='date'>23</var>, <var data-var='time'>08:21</var> UTC Identified - We were able to reactivate the MK8s maintenances in all clusters in our TXL datacenter Jun <var data-var='date'>22</var>, <var data-var='time'>19:07</var> UTC Investigating - Due to exceptionally high demand in two clusters in our TXL and FRA datacenters, we have temporarily paused Managed Kubernetes Automated Maintenance. To ensure that clusters remain operational without interruption during updates, Automated Maintenance requires temporary cluster "cloning", which increases resource consumption. As most maintenance windows are scheduled to run over the weekend, resource demand peaks sharply during these periods. To protect cluster stability and prevent service degradation, we have paused maintenance for the affected clusters. Any maintenance scheduled from today onward will not run until we resume. We know automated Kubernetes maintenance is an important feature of our platform, and we did not take this decision lightly. We are expanding capacity in the affected clusters as a high priority and will update this page as soon as maintenance resumes.

Managed Kubernetes - Automated Maintenance disabled

Jun <var data-var='date'>22</var>, <var data-var='time'>18:42</var> UTC Resolved - We are marking this incident as resolved, as no further abnormalities occurred. Jun <var data-var='date'>19</var>, <var data-var='time'>09:03</var> UTC Monitoring - Error rate has dropped. We are monitoring the situation further. Jun <var data-var='date'>19</var>, <var data-var='time'>06:57</var> UTC Identified - We are reducing the impact of the incident, as our Object Storage Team has traced back the increased error rates to mainly SlowDown codes, which affect only heavily loaded buckets. Jun <var data-var='date'>19</var>, <var data-var='time'>06:35</var> UTC Investigating - We are currently investigating increased error rate for S3 in our FRA DC

S3: Increased Error Rate

Jun <var data-var='date'>22</var>, <var data-var='time'>15:00</var> UTC Completed - The scheduled maintenance has been completed. Jun <var data-var='date'>22</var>, <var data-var='time'>10:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jun <var data-var='date'>18</var>, <var data-var='time'>12:10</var> UTC Scheduled - We are performing a phased upgrade of our network configuration across all locations. This update includes firewall and cluster configuration changes required to integrate new frontend nodes. There should be no impact, but on rare occasions a brief packet loss of a few seconds may occur. Affected services: Network Location: Location DE/FKB, Location DE/FRA, Location DE/FRA/2, Location DE/TXL, Location ES/VIT, Location FR/PAR, Location GB/BHX, Location GB/GLO, Location GB/LHR, Location US/EWR, Location US/LAS, Location US/MCI

Jun <var data-var='date'>22</var>, <var data-var='time'>11:04</var> UTC Resolved - We have marked this incident as resolved. Several underlying VMs entered an unhealthy state, which increased the CPU load on the remaining healthy VMs supporting the service. This cascaded into the intermittent availability issues. All systems are now operating normally. Jun <var data-var='date'>22</var>, <var data-var='time'>08:35</var> UTC Identified - We have observed another spike and are setting the incident back to active. Our MK8s Team is informed and are actively working the incident. Jun <var data-var='date'>22</var>, <var data-var='time'>08:15</var> UTC Monitoring - Control Planes are reachable again. Our MK8s Team is currently investigating the root cause for the service interruption. Jun <var data-var='date'>22</var>, <var data-var='time'>08:01</var> UTC Investigating - We are currently investigating issues with the MK8s control plane

MK8s Control Plane: Partial Outage

Jun <var data-var='date'>19</var>, <var data-var='time'>16:32</var> UTC Resolved - We are resolving this incident as provisioning performance has fully normalized. Jun <var data-var='date'>18</var>, <var data-var='time'>17:46</var> UTC Monitoring - Provisioning is currently operating as expected, and we are closely monitoring the system. Our team is continuing to investigate the root cause of the earlier performance degradation. Jun <var data-var='date'>18</var>, <var data-var='time'>17:20</var> UTC Investigating - We are currently investigating instances of performance degradation in job processing. Our Provisioning Team is currently investigating the root cause of these events. Customers might see delays and errors in provisioning job processing.

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

Jun <var data-var='date'>18</var>, <var data-var='time'>06:00</var> UTC Completed - The scheduled maintenance has been completed. Jun <var data-var='date'>18</var>, <var data-var='time'>05:30</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jun <var data-var='date'>12</var>, <var data-var='time'>11:11</var> UTC Scheduled - We are conducting maintenance on our provisioning engine. During the maintenance customers might see delays in provisioning of up to 20 minutes — requests submitted via the Cloud API and the Data Center Designer (DCD) may take longer to process. In rare cases, provisioning errors may occur, requiring the request to be repeated. There will be no impact on existing, already provisioned resources. We recommend scheduling provisioning tasks outside of the maintenance window where possible. Affected services: Provisioning Location: APIs and Frontends, Cloud Support, Global Services, Location DE/FRA, Location DE/FRA/2, Location DE/TXL

Provisioning Maintenance

Jun <var data-var='date'>17</var>, <var data-var='time'>14:03</var> UTC Resolved - The incident has now been resolved, and accessing S3 Buckets should now be working as expected. Jun <var data-var='date'>17</var>, <var data-var='time'>11:40</var> UTC Investigating - We are currently experiencing a high error rate with S3 Object Storage in TXL - eu-central-3. This is currently being investigated and we will continue to keep this page updated.

S3 High Error Rate - TXL

Jun <var data-var='date'>16</var>, <var data-var='time'>10:30</var> UTC Completed - The scheduled maintenance has been completed. Jun <var data-var='date'>16</var>, <var data-var='time'>08:30</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jun <var data-var='date'>11</var>, <var data-var='time'>13:47</var> UTC Scheduled - Scheduled Maintenance: MongoDB Connection Limit Enforcement Effective Date: June 16, 2026 Affected Service: IONOS Managed MongoDB Enterprise Edition clusters To ensure ongoing platform stability and predictable performance, IONOS will begin strictly enforcing connection limits on Managed MongoDB clusters. Applications that open excessive concurrent connections may begin experiencing connection-limit errors after the effective date. Required Actions to Prevent Disruptions: Implement driver-based connection pooling. Reuse the MongoDB client and connection rather than creating a new client per request. Tune your driver's pool settings appropriately, focusing on variables like maxPoolSize, minPoolSize, and waitQueueTimeout. Validate your total connection footprint across all application instances and environments. Helpful Resources & Support Please review the IONOS MongoDB Sizing Guide to properly tune your connections and pools. If you anticipate needing additional connection capacity, please reach out to Support with your current connection usage patterns (number of instances, expected peak concurrency, and driver settings). Affected services: Database as a Service (DBaaS) Location: Global Services

MongoDB Enterprise: Enforce Connection Limits based on RAM Size

Jun <var data-var='date'>15</var>, <var data-var='time'>11:20</var> UTC Resolved - The system is stable. We are resolving this incident. The trigger of this incident will be shared once the analysis has been completed. Jun <var data-var='date'>15</var>, <var data-var='time'>10:41</var> UTC Monitoring - The DCD is available again. We are monitoring the system closely and will set this incident to resolved once the environment is confirmed stable. Jun <var data-var='date'>15</var>, <var data-var='time'>10:18</var> UTC Update - We believe that the trigger for the incident has been mitigated. We are currently working on restoring all services related to the DCD. Jun <var data-var='date'>15</var>, <var data-var='time'>09:23</var> UTC Identified - Our DCD Team is currently investigating the incident. We have confirmed that Cloud API remains functional and available. Customers and Partners needing to deploy changes to their setup can still use ionosctl and cloudapi to do so. Jun <var data-var='date'>15</var>, <var data-var='time'>09:03</var> UTC Investigating - We are currently investigating increased loading times and timeouts for the DCD.

Availability Issue DCD

Jun <var data-var='date'>13</var>, <var data-var='time'>21:13</var> UTC Resolved - Phone Support is now available again Jun <var data-var='date'>13</var>, <var data-var='time'>13:50</var> UTC Identified - IONOS Cloud Support is temporarily unavailable via phone. We ask Customers and Partners to contact Cloud Support via DCD Form and Email, instead.

Is IONOS Cloud down?

IONOS Cloud status is DEGRADED

Components with issues

Lastest published events

Network Maintenance

Partial Control Plane Outage Affecting Kubernetes Operations

Provisioning: Degraded Performance in Job Processing

IONOS Cloud Services, Components and Regions

Recent IONOS Cloud events

Switch to Berlin located provisioning stack

Disabling PostgreSQL Cluster Creation via API v1

Network Maintenance

Partial Control Plane Outage Affecting Kubernetes Operations

Provisioning: Degraded Performance in Job Processing

Partial Connectivity Degradation to Control Plane Affecting Kubernetes Operations

Get your FREE account now,
5 monitors included!

Is IONOS Cloud down?

IONOS Cloud status is DEGRADED

Components with issues

Lastest published events

Network Maintenance

Partial Control Plane Outage Affecting Kubernetes Operations

Provisioning: Degraded Performance in Job Processing

IONOS Cloud Services, Components and Regions

Recent IONOS Cloud events

Switch to Berlin located provisioning stack

Disabling PostgreSQL Cluster Creation via API v1

Network Maintenance

Partial Control Plane Outage Affecting Kubernetes Operations

Provisioning: Degraded Performance in Job Processing

Partial Connectivity Degradation to Control Plane Affecting Kubernetes Operations

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!