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
DBaaS PostgreSQL API v1 Decommissioning Sep 28, 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
Disabling New MariaDB 10.6 Cluster Creation Oct 12, 2026 16:00-18:00 UTC
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
Posted on Sep 21, 2026 - 08:26 UTC
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
Posted on Sep 21, 2026 - 08:26 UTC
Disabling New PostgreSQL 14 Cluster Creation Oct 19, 2026 16:00-18:00 UTC
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
Posted on Sep 21, 2026 - 08:26 UTC
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
Posted on Sep 21, 2026 - 08:26 UTC