Log in
Cloud Support: Telephone Support reduced capacity
Update - The situation is still unchanged, so best would be to please reach out via email.
Aug 17, 2026 - 13:31 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.
Aug 14, 2026 - 14:50 UTC
Automated DBaaS PostgreSQL v1 to v2 Infrastructure Migration
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 17, 2026 - 05:00 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
Aug 17, 2026 05:00 - Aug 31, 2026 17:00 UTC
Managed Kubernetes - Automated Maintenance disabled
Identified - We were able to reactivate the MK8s maintenances in all clusters in our TXL datacenter
Jun 23, 2026 - 08:21 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.
Jun 22, 2026 - 19:07 UTC
GPU Server Provisioning: Supply currently limited
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.
Jun 18, 2026 - 15:04 UTC
Provisioning of MongoDB Playground and Business Edition Clusters unavailable
Investigating - MongoDB Playground and Business Edition clusters are currently not available for provisioning in de/fra/2 (Frankfurt East). This is due to a capacity limitation in that location that prevents these cluster types from being created reliably, and it is expected to persist for the time being. We will update this status page as soon as this limitation is lifted.

As an alternative, you can:
- Provision your Playground or Business Edition cluster in another available location, or
- Use MongoDB Enterprise Edition, which remains available in Frankfurt East.
Jun 12, 2026 - 15:46 UTC
Cloud Support Degraded Performance
Location DE/FKB Operational
Compute Operational
Storage Operational
Network Operational
Managed Kubernetes Operational
Supporting Services Operational
Provisioning Operational
Private Cloud Operational
Logging Service Operational
Monitoring Service Operational
Location DE/FRA Operational
Compute Operational
Cubes Operational
Storage Operational
Network Operational
Managed Kubernetes Operational
Supporting Services Operational
Provisioning Operational
Object Storage Operational
Logging Service Operational
Monitoring Service Operational
Location DE/FRA/2 Operational
Compute Operational
Cubes Operational
Storage Operational
Network Operational
Managed Kubernetes Operational
Supporting Services Operational
Provisioning Operational
Object Storage Operational
Logging Service Operational
Monitoring Service Operational
Location DE/TXL Operational
Compute Operational
Cubes Operational
Storage Operational
Network Operational
Managed Kubernetes Operational
Supporting Services Operational
Provisioning Operational
Object Storage Operational
Private Cloud Operational
Logging Service Operational
Monitoring Service Operational
Location ES/VIT Operational
Compute Operational
Cubes Operational
Storage Operational
Network Operational
Managed Kubernetes Operational
Supporting Services Operational
Provisioning Operational
Object Storage Operational
Logging Service Operational
Monitoring Service Operational
Location FR/PAR Operational
Compute Operational
Storage Operational
Cubes Operational
Managed Kubernetes Operational
Provisioning Operational
Supporting Services Operational
Network Operational
Logging Service Operational
Monitoring Service Operational
Location GB/BHX Operational
Compute Operational
Cubes Operational
Storage Operational
Network Operational
Managed Kubernetes Operational
Supporting Services Operational
Provisioning Operational
Logging Service Operational
Monitoring Service Operational
Location GB/GLO Operational
Private Cloud Operational
Location GB/LHR Operational
Compute Operational
Cubes Operational
Storage Operational
Network Operational
Managed Kubernetes Operational
Supporting Services Operational
Provisioning Operational
Logging Service Operational
Monitoring Service Operational
Location US/EWR Operational
Compute Operational
Storage Operational
Network Operational
Managed Kubernetes Operational
Supporting Services Operational
Provisioning Operational
Logging Service Operational
Monitoring Service Operational
Location US/LAS Operational
Compute Operational
Storage Operational
Network Operational
Managed Kubernetes Operational
Supporting Services Operational
Provisioning Operational
Logging Service Operational
Monitoring Service Operational
Location US/MCI Operational
Compute Operational
Storage Operational
Network Operational
Managed Kubernetes Operational
Provisioning Operational
Supporting Services Operational
Logging Service Operational
Monitoring Service Operational
APIs and Frontends Operational
Data Center Designer (DCD) Operational
Cloud API Operational
Billing API Operational
Reseller API Operational
Activity Log API Operational
Global Services Operational
Backup Service Operational
CloudDNS Operational
Database as a Service (DBaaS) Operational
Monitoring as a Service (MaaS) Operational
Content Delivery Network (CDN) Operational
AI Model Hub Operational
IAM Operational
Container Registry Operational
Accounts and Billing Operational
GPU Server Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance

Scheduled Maintenance

Automated Migration to IONOS MariaDB API v2 Aug 24, 2026 14:00 - Aug 28, 2026 06:00 UTC

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
Posted on Aug 13, 2026 - 10:13 UTC

Action Required: IONOS In-Memory DB API v1 Full Deprecation Aug 31, 2026 14:00-16:00 UTC

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
Posted on Aug 13, 2026 - 12:32 UTC

Aug 19, 2026

No incidents reported today.

Aug 18, 2026

No incidents reported.

Aug 17, 2026

Disabling MariaDB Cluster Creation via API v1
Completed - The scheduled maintenance has been completed.
Aug 17, 16:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 17, 14:00 UTC
Scheduled - Effective Aug 17, 2026, IONOS Cloud will permanently disable the creation of new DBaaS MariaDB clusters via API v1. This is a preliminary step in our transition to the upgraded MariaDB v2 infrastructure.

What does this mean for you?
- New Cluster Provisions: Any automated scripts, CI/CD pipelines, SDKs, or IaC tools (e.g., Terraform) attempting to create new MariaDB clusters using API v1 after Aug 17, 2026, will be rejected.
- Existing Clusters: There is no impact on existing MariaDB v1 clusters. All running v1 instances will remain fully operational and accessible as usual.

Required Actions for New Deployments
To deploy new MariaDB clusters going forward, you must transition your provisioning automation to MariaDB v2:
- Update API Calls & Integrations: Switch your scripts, SDKs, and Terraform configurations to use the MariaDB v2 API and providers.
- Review Supported Versions: MariaDB v2 supports versions 10.11, 11.4, 11.8 and 12.3.

Looking Ahead: Automated Cluster Migrations
Existing MariaDB v1 clusters will be automatically migrated to the v2 infrastructure by IONOS with zero downtime. Connection endpoints will remain unchanged. You will receive separate status updates and communications as the migration rollout approaches.

If you have questions or need technical assistance updating your workflows to API v2, please contact our Customer Support team at support@cloud.ionos.com.

Affected services: Database as a Service (DBaaS)
Location: Global Services
Aug 6, 13:39 UTC

Aug 16, 2026

No incidents reported.

Aug 15, 2026

No incidents reported.

Aug 14, 2026

Provisioning: VDC-14-1836
Resolved - This incident has been resolved.
Aug 14, 13:34 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Aug 14, 12:42 UTC
Identified - We are currently reports of error VDC-14-1836 during provisioning operations. Our provisioning team is informed and is preparing a hotfix.
Aug 14, 10:51 UTC
AI Model Hub - Service Degradations
Resolved - We were able to resolve this issue, it's back to normal now.
Aug 14, 08:04 UTC
Investigating - We are currently investigating reports of increased AI Model Hub error rates and latencies. More details will be shared as they become available.
Aug 13, 00:49 UTC

Aug 13, 2026

Aug 12, 2026

Network maintenance
Completed - The scheduled maintenance has been completed.
Aug 12, 23:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 12, 20:00 UTC
Scheduled - We will be performing a network maintenance in DE/FRA and DE/FRA/2 that includes updating routing filters. While no impact is expected, in some cases, you might notice increased latency for 5-10 seconds due to routing convergence.

The availability of your virtual data center resources will remain unaffected.
Aug 11, 07:10 UTC
Switch provisioning setup
Completed - The scheduled maintenance has been completed.
Aug 12, 17:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 12, 15:00 UTC
Scheduled - We will be routing provisioning traffic to a new setup to improve stability and geo-redundancy for our customers.

As a result, provisioning services — including the Cloud API and Data Center Designer — may be temporarily unavailable for a few minutes. Since ionosctl, Terraform, and our SDKs depend on the Cloud API, these tools will also be affected during this time. Customer workloads will remain unaffected.

Please follow https://status.ionos.cloud/ for real-time updates.

Affected services: Cloud API, Data Center Designer (DCD), Provisioning
Location: APIs and Frontends, 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
Aug 5, 09:03 UTC
Limited access to provisioning services
Resolved - This incident has been resolved.
Aug 12, 11:52 UTC
Monitoring - We confirm that the provisioning service has recovered and is operating normally. Our teams will continue to monitor the environment to ensure its stability and continued operation.
Aug 11, 19:24 UTC
Update - We are still seeing residual 500 errors from the Cloud API and are working towards resolving the remaining service degradation.
Aug 11, 16:37 UTC
Identified - We have identified a likely culprit. The Provisioning Team has implemented a mitigation. We see the performance of the service stabilizing.
Aug 11, 16:23 UTC
Investigating - Currently, there is an increased processing time for provisioning orders that are initiated via Data Center Designer or API.

Occasionally, connections may be lost in the direction of the Data Center Designer.

Availability and accessibility of your virtual data center resources will remain unaffected.
We will inform you as soon as the functionality has been restored.
Aug 11, 16:05 UTC

Aug 11, 2026

Network Maintenance
Completed - The scheduled maintenance has been completed.
Aug 11, 19:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 11, 17:00 UTC
Scheduled - We are performing network maintenance that includes updating routing filters. Generally this has no impact, but in some cases, due to routing convergence, this can cause an impact of 5-10 seconds.

Affected services: Network
Location: Location DE/FRA
Aug 6, 13:40 UTC

Aug 10, 2026

Managed Kubernetes - Intermittent Control Plane Unavailability
Resolved - We are marking this incident as resolved.
The measures already put into place have had the desired effect on the service and have improved performance and stability.
While this incident is marked as resolved, we are continuing executing on our action plan to improve the performance and reliability of our Managed Kubernetes Control Planes. Our current focus:
- Further load balancing on our Control Plane Clusters
- Migration of control planes to improved infrastructure
Aug 10, 19:58 UTC
Update - Migration of customer workloads on the first control plane cluster has been completed ahead of schedule. Customer clusters have been redistributed across expanded infrastructure and all migrated workloads are running without issues. We continue to observe stable control plane performance with no new disruptions reported.
Aug 7, 05:06 UTC
Monitoring - Memory limit adjustments have been fully rolled out across all control plane clusters and are showing positive effects. We have significantly expanded the underlying infrastructure capacity and migration of customer workloads is progressing well.
We are observing substantial improvements in control plane stability and performance. The recurring disruption patterns described in earlier updates are no longer present.
Migration work will continue throughout the day. We will provide an update once migrations are completed or if any changes in status occur.
Aug 6, 08:04 UTC
Update - Memory limit adjustments and migration have had positive effects on the first control plane cluster. Customer situated in the first control plane cluster should already see substantial improvements in performance and stability.

We have started to roll out memory adjustments in the remaining control plane cluster, as well. Rolling out the memory limits can lead to temporary unavailability of affected control planes. These interruptions should be brief and will not affect running workloads.

After memory limit adjustments are fully rolled out on the second control plane cluster, horizontal scaling and migrations will resume on both control plane clusters for the next hours until workload is distributed optimally.
Aug 5, 20:43 UTC
Update - Migration has been picked up again. We already see encouraging results after completion of first batches. In the next hours we focus on completing the migration and horizontal scaling.
During the migration, single etcds can be temporarily unavailable for time periods lasting around 30 seconds.
We expect further performance and stability improvements for all customers during and after the migration.
Aug 5, 10:07 UTC
Identified - Migration of the first batches has been completed. The Kubernetes Team has identified a remaining issue preventing further migration. We are setting this incident back to active until the issue is resolved and the migration completed.
Aug 5, 06:23 UTC
Monitoring - Memory adjustments have been rolled out and show positive effects.
We are starting the migrations planned to further improve control plane performance for all our customers.
We estimate that the migration will be completed in the next hours.
Control Plane performance is expected to improve already during the migration.

We are setting this incident into Monitoring status and will provide an update once the migration is completed.
Aug 4, 21:11 UTC
Update - Our plans for further horizontal scaling of the control plane are progressing. We expect to be able to do a dry run and further testing within the next hours, before we proceed with migrations.
We aim to finish work on horizontal scaling until EOD.
We are rolling out memory configuration improvements in parallel.
Aug 4, 16:23 UTC
Update - We are currently rolling out memory scaling measures to address recurring stability issues during compaction operations on the affected etcd clusters. Additionally, we are planning to roll out further horizontal scaling for the affected clusters today.

We will provide another update once these measures have been applied and we can assess their impact.
Aug 4, 14:37 UTC
Update - During a service rollout today, a subset of control planes experienced temporary restarts. Affected customers may notice brief API unavailability while these control planes recover. The team is monitoring the recovery.

Separately, work on improving infrastructure capacity and load distribution continues as described in our initial update.

We will post another update once the affected control planes have fully stabilized.
Aug 4, 13:14 UTC
Identified - We are aware of intermittent control plane unavailability affecting a subset of Managed Kubernetes customers. Affected customers may experience API call failures, deployment timeouts, and temporary disruption of cluster management operations.

Our engineering team is actively working on both immediate mitigations and longer-term architectural improvements.

Several mitigations have already been deployed, including maintenance schedule optimization, compaction regression fixes, and storage performance improvements. Additional measures - including infrastructure migration, dedicated event etcd clusters, improved load balancing, and horizontal scaling - are in progress.

We are providing regular updates on this page. Customers experiencing issues are encouraged to subscribe to this incident for timely notifications.
Aug 4, 10:24 UTC

Aug 9, 2026

No incidents reported.

Aug 8, 2026

No incidents reported.

Aug 7, 2026

Aug 6, 2026

Automated DBaaS PostgreSQL v1 to v2 Infrastructure Migration
Completed - The scheduled maintenance has been completed.
Aug 6, 17:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 3, 09:00 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 July 29, 2026, to prevent management access disruption.
- Instructions for generating authentication tokens can be found in the IONOS Cloud Token Manager Documentation [https://docs.ionos.com/cloud/set-up-ionos-cloud/management/identity-access-management/token-manager].
- 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
Jul 16, 13:34 UTC

Aug 5, 2026

← Incident History Powered by Atlassian Statuspage