[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 is unstable. The Managed Kubernetes Service in DE1 is also affected. OVHcloud is investigating the cause and reports this status as of 11:27 UTC.
State
Investigating
Started
Ongoing for
1 h 26 min
Worst impact
Degraded
Timeline
2 updatesInvestigating
1 h 26 min 100%
Updates
Times in UTCAs posted by OVHcloud
Please find an update of this incident below : Update : Managed Kubernetes Service in the DE1 region is also impacted by this incident. Customers may experience API errors when creating, modifying or managing their Kubernetes clusters. Ongoing Actions : 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.
We are currently experiencing an incident affecting our Network offering, which is causing temporary availability issues in the DE1 region. Please find the details of this incident below : Start time : 03/11/2026 08:10 UTC Impacted Service(s) : The Network API for public network and private network (vRack) is temporarily unstable in the specified region. Customers Impact : Customers may experience API errors when creating, modifying or managing their public and private network (vRack) configurations. Ongoing Actions : Our teams are investigating to determine the origin of the incident to fix it. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
Affected components
4OVHcloud in the last 90 days
Full historyIncidents in 90 days
230
Days with an incident
90
Median duration
1 h 37 min
This incident
About the median
Other OVHcloud incidents
All incidentsOVHcloud·[Global][Dedicated Servers] - Delivery incident notification
OVHcloud reports delays in the processing of suspension and reactivation requests for Dedicated Servers. The issue affects Zone Europe, Zone APAC, and Zone Canada. OVHcloud is investigating the origin of the incident.
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·[EU-WEST-PAR][Storage] - Object Storage incident notification
OVHcloud Object Storage S3 has increased response times in the EU-WEST-PAR region. This affects the EU-WEST-PAR-A, EU-WEST-PAR-B, and EU-WEST-PAR-C components. OVHcloud reports that the service was fully restored at 09:53 UTC on 03/11/2026, and monitoring continues.
OVHcloud·[Global][AI & Machine Learning] - AI Notebooks, AI Training, AI Deploy incident notification
We would like to inform you that an incident affected our AI & Machine Learning offering. This incident has since been resolved. Please find the details of this incident below : Start time : 31/10/2026 07:08 UTC End time : 31/10/2026 07:58 UTC Impacted Service(s) : AI Notebooks, AI Training and AI Deploy services were temporarily unavailable. Customers Impact : Customers were temporarily unable to create, manage or access their notebooks, training jobs and AI applications. Root Cause : This incident was caused by a software issue. We thank you for your understanding and patience throughout this incident.
OVHcloud·[BHS5][Dedicated Servers] - Racks T05B28, T05B29 incident notification
OVHcloud reports that some Dedicated Servers in racks T05B28 and T05B29 in BHS5 were temporarily unavailable. OVHcloud states that the incident is resolved. It lasted about 60 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