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

Sep 15, 2026

No incidents reported today.

Sep 14, 2026

No incidents reported.

Sep 13, 2026

No incidents reported.

Sep 12, 2026

No incidents reported.

Sep 11, 2026

No incidents reported.

Sep 10, 2026

No incidents reported.

Sep 9, 2026

Unresolved incident: TXL - Network Connectivity.

Sep 8, 2026

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

Sep 7, 2026

Sep 6, 2026

No incidents reported.

Sep 5, 2026

No incidents reported.

Sep 4, 2026

Sep 3, 2026

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

Sep 2, 2026

No incidents reported.

Sep 1, 2026

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