Limited access to provisioning services
Incident
Report for IONOS Cloud
Resolved
This incident has been resolved.
Monitoring
A fix has been implemented and we are monitoring the results.
Identified
The issue has been identified and a fix is being implemented.
Monitoring
A fix has been implemented. We are monitoring the queue.
Note: If you receive a "429 Too Many Requests" return code, please slow down your requests or try again later.
Note: If you receive a "429 Too Many Requests" return code, please slow down your requests or try again later.
Identified
We have identified the issue and are taking steps to mitigate the impact of the incident.
We will let you know when the provisioning service is back to normal.
You may receive a response from the API such as "429 Too Many Requests".
If this is the case, please try your request at a later time or with a lower frequency.
As the provisioning service is affected, making changes to services such as Managed Kubernetes may also be affected — they require the provisioning service in the background for certain tasks.
We will let you know when the provisioning service is back to normal.
You may receive a response from the API such as "429 Too Many Requests".
If this is the case, please try your request at a later time or with a lower frequency.
As the provisioning service is affected, making changes to services such as Managed Kubernetes may also be affected — they require the provisioning service in the background for certain tasks.
Update
Please note:
You may receive a response from the API such as "429 Too Many Requests".
If this is the case, please try your request at a later time or with a lower frequency.
As the provisioning service is affected, other services such as Managed Kubernetes may also be affected — as they require the provisioning service in the background.
You may receive a response from the API such as "429 Too Many Requests".
If this is the case, please try your request at a later time or with a lower frequency.
As the provisioning service is affected, other services such as Managed Kubernetes may also be affected — as they require the provisioning service in the background.
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.
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.
This incident affected: APIs and Frontends (Data Center Designer (DCD), Cloud API), Location FR/PAR (Managed Kubernetes, Provisioning), Location US/MCI (Managed Kubernetes, Provisioning), Location DE/TXL (Managed Kubernetes, Provisioning), Location DE/FRA (Managed Kubernetes, Provisioning), Location DE/FKB (Managed Kubernetes, Provisioning), Location GB/LHR (Managed Kubernetes, Provisioning), Location US/EWR (Managed Kubernetes, Provisioning), Location US/LAS (Managed Kubernetes, Provisioning), and Location ES/VIT (Managed Kubernetes, Provisioning).