I can only submit the screenshot of the mail they sent. At the time of writing this I haven’t found anything about this on their blog, and the status page (https://www.ionos-status.de) currently shows all services as green.
Here is the full text:
Customer Advisory: Capacity Constraints in FRA (de/fra) Datacenter
Dear IONOS user,
We are currently experiencing exceptionally high demand for resources in our FRA (de/fra) datacenter. You are receiving this notification because at least some of your resources are provisioned in a cluster in this datacenter that is facing acute capacity constraints as a result of the demand.
Because of these circumstances, attempts to provision additional resources may fail and then return the error code VDC-5-601.
What this means for you and your workloads:
- Existing Deployments: Your current clusters and resources are unaffected and will continue to operate normally without interruption.
- New Deployments & Scaling: Requests to provision new resources, scale out or rebuilding nodes may fail with the VDC-5-601 error.
- Managed Kubernetes Maintenance: Due to the situation, we are pausing Managed Kubernetes maintenance for this cluster
- Database as a Service Clusters Provisioning and Scaling: Depending on how the situation develops over the next few hours, we may need to temporarily limit provisioning and scaling of DBaaS clusters in this cluster. If these precautions become necessary, we will inform you in a separate email.
Estimated Timeline: We anticipate that the resource constraints in this cluster will improve over the next few days. Expanding capacity in the affected cluster is our highest priority. We will notify you once the situation improves.
What you can do:
- Where possible, avoid scaling operations to existing resources (e.g, adding cores/RAM)
- Use alternative datacenters: If your architecture permits, routing new workloads to other datacenters (e.g., de/txl) will bypass these constraints and allow you to continue scaling.
- Adjust resource requests: If your provisioning requests result in a VDC-5-601 error, please try requesting fewer resources. CPU cores and RAM are the primary bottlenecks right now. Also, requesting specific CPU types may make your request less likely to succeed. Thus, reducing your requested cores and RAM or using a different CPU type (or vCPUs) may allow your deployment to succeed.
A Note on Support:
- Please note that our Support Team cannot bypass capacity limits or directly resolve VDC-5-601 errors.
- A live migration of workloads across clusters is not currently possible. Our Support Team will not be able to move your VDCs to a different cluster in the datacenter.
- Due to the highly dynamic nature of resource consumption, our Support Team cannot currently suggest suitable combinations that are guaranteed to lead to successful provisioning.
We appreciate your patience and understanding as we work to expand our capacity and resolve this situation. We will proactively inform you about any changes related to this situation.
If you have any questions, please contact our IONOS Cloud Support via e-mail or telephone at any time.
> This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
does anyone know where these "detailed root cause analysis" reports are shared? is there maybe an archive?
i am using an x86 emulator - booting it up takes about twice as long though compared to WSA. Also being able to dynamically resize the Window as need was nice to test different sizes directly within WSA instead of having multiple emulators running
Also the foundation for MAUI, the native bindings for .NET are incomplete and broken. Back in the Xamarin days the promise was that "everything you can do natively you can do in .NET" - this hasn't been true for a long time. Most of the new frameworks, especially on the iOS side don't have a binding and Microsoft doesn't have a story for Swift based libraries at all
Here is the full text:
Customer Advisory: Capacity Constraints in FRA (de/fra) Datacenter
Dear IONOS user,
We are currently experiencing exceptionally high demand for resources in our FRA (de/fra) datacenter. You are receiving this notification because at least some of your resources are provisioned in a cluster in this datacenter that is facing acute capacity constraints as a result of the demand.
Because of these circumstances, attempts to provision additional resources may fail and then return the error code VDC-5-601.
What this means for you and your workloads: - Existing Deployments: Your current clusters and resources are unaffected and will continue to operate normally without interruption. - New Deployments & Scaling: Requests to provision new resources, scale out or rebuilding nodes may fail with the VDC-5-601 error. - Managed Kubernetes Maintenance: Due to the situation, we are pausing Managed Kubernetes maintenance for this cluster - Database as a Service Clusters Provisioning and Scaling: Depending on how the situation develops over the next few hours, we may need to temporarily limit provisioning and scaling of DBaaS clusters in this cluster. If these precautions become necessary, we will inform you in a separate email.
Estimated Timeline: We anticipate that the resource constraints in this cluster will improve over the next few days. Expanding capacity in the affected cluster is our highest priority. We will notify you once the situation improves.
What you can do: - Where possible, avoid scaling operations to existing resources (e.g, adding cores/RAM) - Use alternative datacenters: If your architecture permits, routing new workloads to other datacenters (e.g., de/txl) will bypass these constraints and allow you to continue scaling. - Adjust resource requests: If your provisioning requests result in a VDC-5-601 error, please try requesting fewer resources. CPU cores and RAM are the primary bottlenecks right now. Also, requesting specific CPU types may make your request less likely to succeed. Thus, reducing your requested cores and RAM or using a different CPU type (or vCPUs) may allow your deployment to succeed.
A Note on Support: - Please note that our Support Team cannot bypass capacity limits or directly resolve VDC-5-601 errors. - A live migration of workloads across clusters is not currently possible. Our Support Team will not be able to move your VDCs to a different cluster in the datacenter. - Due to the highly dynamic nature of resource consumption, our Support Team cannot currently suggest suitable combinations that are guaranteed to lead to successful provisioning.
We appreciate your patience and understanding as we work to expand our capacity and resolve this situation. We will proactively inform you about any changes related to this situation.
If you have any questions, please contact our IONOS Cloud Support via e-mail or telephone at any time.