[SBG5][Network] - Rack SBG0506B08B vRack network equipment maintenance notification
Scheduled maintenance is currently in progress. We will provide updates as necessary.
The latest update from OVHcloud.
State
Resolved
Started
Lasted
1 h 2 min
Worst impact
Maintenance
Timeline
4 updatesIn progress
53 min 86%
Resolved
9 min 14%
Updates
Times in UTCAs posted by OVHcloud
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Affected components
2OVHcloud in the last 90 days
Full historyIncidents in 90 days
227
Days with an incident
90
Median duration
1 h 37 min
This incident
Not comparable
Other OVHcloud incidents
All incidentsOVHcloud·[GRA11][Network] - Network API incident notification
OVHcloud reports that the Network API for the public network and the private network (vRack) was unstable in the GRA11 region. The Managed Kubernetes Service in GRA11 was also affected. OVHcloud says that the incident is resolved and that it lasted about 6 hours and 18 minutes.
OVHcloud·[Global][Dedicated Servers] - Delivery incident notification
OVHcloud Dedicated Servers delivery was degraded. The processing of suspension and reactivation requests was delayed in Zone Europe, Zone APAC, and Zone Canada. OVHcloud reports that 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
The Network API for the public network and the private network (vRack) did not work in the DE1 region. The Managed Kubernetes Service in DE1 was also affected. OVHcloud reports that the incident is resolved. It lasted about 4 hours and 43 minutes.
OVHcloud·[EU-WEST-PAR][Storage] - Object Storage incident notification
OVHcloud Object Storage S3 in the EU-WEST-PAR region had increased response times. The service was fully restored at 09:53 UTC on 03/11/2026, and OVHcloud keeps monitoring in place.
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.live/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.live/feed.xml?providers=ovhcloud/feed subscribe https://outages.live/feed.xml?providers=ovhcloudFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane