In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 24, 2026 - 14:00 UTC
Aug 24, 2026 - 14:00 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
Aug 24, 2026 14:00 - Aug 28, 2026 06:00 UTC
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
Aug 24, 2026 14:00 - Aug 28, 2026 06:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 17, 2026 - 05:00 UTC
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
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
Identified - We were able to reactivate the MK8s maintenances in all clusters in our TXL datacenter
Jun 23, 2026 - 08:21 UTC
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
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
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
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
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
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
Operational
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
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
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
IONOS MariaDB API v1 Full Deprecation Aug 31, 2026 14:00-16:00 UTC
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
Posted on Aug 24, 2026 - 14:41 UTC
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
Posted on Aug 24, 2026 - 14:41 UTC
DBaaS PostgreSQL API v1 Decommissioning Sep 15, 2026 14:00-16:00 UTC
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
Posted on Aug 24, 2026 - 14:41 UTC
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
Posted on Aug 24, 2026 - 14:41 UTC