[RBX8][Dedicated Servers] - Rack R808L04 incident notification
The vRack network for Dedicated Servers was unavailable in rack R808L04 in the RBX region. OVHcloud identified a cooling system issue as the cause. OVHcloud reports that the incident is resolved. It lasted about 2 hours and 10 minutes.
State
Resolved
Started
Lasted
2 h 10 min
Worst impact
Partial outage
Timeline
3 updatesInvestigating
26 min 20%
Identified
1 h 44 min 80%
Updates
Times in UTCAs posted by OVHcloud
We would like to inform you that the incident affecting our Dedicated Servers offering has now been resolved. Please find the details of this incident below : Start time : 05/11/2026 23:47 UTC End time : 06/11/2026 01:57 UTC Impacted Service(s) : vRack network was temporarily unavailable in the specified rack. Customers Impact : Customers were temporarily unable to access and use their servers through vRack network. Root Cause : This incident was caused by a cooling system issue. We thank you for your understanding and patience throughout this incident.
We are currently experiencing an incident affecting our Dedicated Servers offering in the rack R808L04. The root cause has been identified. Please find the details of this incident below : Start time : 05/11/2026 23:47 UTC Impacted Service(s) : vRack network is temporarily unavailable in the specified rack. Customers Impact : Customers are temporarily unable to access and use their servers through vRack network. Root Cause : This incident is caused by a cooling system issue. Ongoing Actions : Our teams are actively working 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 Dedicated Servers offering, which is causing temporary availability issues in the rack R808L04. Please find the details of this incident below : Start time : 05/11/2026 23:47 UTC Impacted Service(s) : vRack network is temporarily unavailable in the specified rack. Customers Impact : Customers are temporarily unable to access and use their servers through vRack network. 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
2OVHcloud in the last 90 days
Full historyIncidents in 90 days
241
Days with an incident
90
Median duration
1 h 39 min
This incident
1.3× the median
Other OVHcloud incidents
All incidentsOVHcloud·[BHS6][Dedicated Servers] - Rack T06F27 incident notification
The vRack network is temporarily unavailable in rack T06F27 in the BHS region. This affects Dedicated Servers network in BHS. OVHcloud identified the root cause as a network equipment issue and replaces the faulty equipment.
OVHcloud·[GRA6][Virtual Private Servers] - VPS incident notification
OVHcloud reports that backup and image management features for Virtual Private Servers were unstable in the GRA6 region, affecting GRA, EU-WEST-GRA, operating system, and additional services components. The incident is resolved. It lasted about 1 hour 9 minutes, from 15:26 UTC to 18:35 UTC.
OVHcloud·[GRA6][Storage] - Instance Backup incident notification
OVHcloud reports that Instance Backup and image management did not work correctly in the GRA6 region. OVHcloud resolved the incident after 99 minutes.
OVHcloud·[EU-WEST-PAR-B][Storage] - Block Storage incident notification
Block Storage in the EU-WEST-PAR-B region has degraded performance. Some volumes in this region have increased latency and reduced performance. OVHcloud reports that the incident is under investigation.
OVHcloud·[EU-WEST-PAR-A][Storage] - Block Storage incident notification
OVHcloud reports degraded performance on some Block Storage volumes in the EU-WEST-PAR-A region. Customers may see increased latency and reduced performance on their volumes in that region. OVHcloud is investigating and its teams work to improve storage performance.
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