OVHcloud Public Cloud Status
Current status
Legend
- Operational
- Degraded performance
- Partial Outage
- Major Outage
- Under maintenance
[Global][Public Cloud] API Load balancer incident notification
Incident
Report for Public Cloud
Resolved
We would like to inform you that the incident on our Public cloud offering has now been resolved.
Here is detail for this incident :
Start time : 17/06/2025 09:30 UTC
End time : 19/06/2025 09:17 UTC
Root Cause : This incident was caused by a software issue.
We thank you for your understanding and patience throughout this incident.
Here is detail for this incident :
Start time : 17/06/2025 09:30 UTC
End time : 19/06/2025 09:17 UTC
Root Cause : This incident was caused by a software issue.
We thank you for your understanding and patience throughout this incident.
Identified
We have new information regarding the incident that affected your service(s).
Please find below an update on the situation:
Update : The incident has been identified and our teams are mobilised to restore service as quickly as possible.
Workaround : We recommend as workaround, doing the creation in two steps. The load balancer then the listerners.
We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.
Please find below an update on the situation:
Update : The incident has been identified and our teams are mobilised to restore service as quickly as possible.
Workaround : We recommend as workaround, doing the creation in two steps. The load balancer then the listerners.
We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.
Investigating
We are currently experiencing an incident affecting our Public cloud offering, which is causing temporary Availability issues in Global.
Here is detail for this incident :
Start time : 17/06/2025 09:30 UTC
Service Impact : Creation of a load balancer with a listener on the same API call will return a 500 error.
We recommend as workaround, doing the creation in two steps. The load balancer then the listerners.
Ongoing Actions : Our teams are investigating to determine the origin of the incident to fix it.
Our teams are fully engaged and working to resolve the issue as quickly as possible.
We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.
Here is detail for this incident :
Start time : 17/06/2025 09:30 UTC
Service Impact : Creation of a load balancer with a listener on the same API call will return a 500 error.
We recommend as workaround, doing the creation in two steps. The load balancer then the listerners.
Ongoing Actions : Our teams are investigating to determine the origin of the incident to fix it.
Our teams are fully engaged and working to resolve the issue as quickly as possible.
We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.
This incident affected: Network || Load Balancer (BHS1, BHS3, BHS5, DE1, GRA1, GRA3, GRA5, GRA7, GRA9, GRA11, SBG5, SBG7, SGP1, SYD1, SYD3, UK1, WAW1, US-EAST-VA-1, US-WEST-OR-1, EU-WEST-PAR-A, EU-WEST-PAR-B, EU-WEST-PAR-C, AP-SOUTH-MUM-1).