[DE1][Network] - Load balancer incident notification
The load balancer delivery service does not work in the DE1 region. OVHcloud reports that the incident is identified and teams work to restore service. OVHcloud gives no workaround.
State
Identified
Started
Ongoing for
1 h 19 min
Worst impact
Notice
Timeline
1 updateIdentified
1 h 19 min 100%
Updates
Times in UTCAs posted by OVHcloud
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Network offer on the specific DE1. Here are some supplementary details : Start time : 03/11/2026 17:00 UTC Impacted Service(s) : The load balancer delivery service in the DE1 region is temporarily unavailable. Customers Impact : Customers are temporarily unable to have their load balancer services delivered in the DE1 region. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
OVHcloud in the last 90 days
Full historyIncidents in 90 days
232
Days with an incident
90
Median duration
1 h 37 min
This incident
18% shorter than the median
Other OVHcloud incidents
All incidentsOVHcloud·[GLOBAL][Dedicated Servers] - Administrative network task incident notification
OVHcloud reports that administrative changes to public and private network settings do not work on Dedicated Servers in many regions, including BHS, GRA, RBX and SBG. The problem affects RISE and SCALE servers delivered after 03 November 2026 at 09:00 UTC. OVHcloud identified a software issue and teams work to restore service.
OVHcloud·[GRA11][Network] - Network API incident notification
OVHcloud reports temporary API errors in the GRA11 region. The incident affects the public network API, the private network (vRack) API, and the Managed Kubernetes Service. OVHcloud reports that the incident is resolved. The incident lasted 55 minutes.
OVHcloud·[Global][Dedicated Servers] - Delivery incident notification
OVHcloud reports delays to suspension and reactivation request processing for Dedicated Servers in the Europe, APAC, and Canada zones. OVHcloud says the incident is resolved. It lasted about 7 hours and 25 minutes.
OVHcloud·[RBX][Storage and Backups] - NAS HA Cluster11003 incident notification
We would like to inform you that an incident affected our NAS HA offering on the Cluster11003 in the RBX region. This incident has since been resolved. Please find the details of this incident below : Start time : 03/11/2026 10:10 UTC End time : 03/11/2026 10:24 UTC Impacted Service(s) : Some NAS HA services on the Cluster11003 were temporarily unavailable. Customers Impact : Customers were temporarily unable to access their data located on the Cluster11003. Root Cause : This incident was caused by a hardware issue. We thank you for your understanding and patience throughout this incident.
OVHcloud·[DE1][Network] - Network API incident notification
OVHcloud reports that the Network API for the public network and the private network (vRack) in the DE1 region does not work correctly. The Managed Kubernetes Service in DE1 is also affected. OVHcloud reports that the incident is resolved, and it lasted 4 hours and 43 minutes.
Follow OVHcloud
Your coding agent knows when OVHcloud is down, and tells you when a failure is theirs, not yours. You can also get OVHcloud incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "ovhcloud" and tell me if OVHcloud has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=ovhcloud/feed subscribe https://outages.cc/feed.xml?providers=ovhcloudFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane