[RBX7][Dedicated Servers] - Rack R715B19 incident notification
Dedicated Servers in rack R715B19 in RBX7 had a temporary availability problem, and some servers were unavailable. OVHcloud reports that the incident is resolved. The outage lasted about 58 minutes, from 22:25 to 23:23 UTC, and OVHcloud states that a cooling system issue caused it.
State
Resolved
Started
Lasted
34 min
Worst impact
Partial outage
Timeline
2 updatesInvestigating
34 min 100%
Updates
Times in UTCAs posted by OVHcloud
We are pleased to inform you that the incident affecting our Dedicated Servers offering has been resolved. Start time : 20/11/2026 22:25 UTC End time : 20/11/2026 23:23 UTC Root Cause : This incident was caused by a cooling system issue. We apologize for any inconvenience caused and appreciate your understanding.
We are currently investigating an incident affecting our Dedicated Servers offering, which is causing temporary availability issue in the rack R715B19 in RBX7. Here are some supplementary details : Start time : 20/11/2026 22:25 UTC Impacted Service(s) : Some servers in the rack R715B19 are temporarily unavailable. Customers Impact : Some customers are temporarily unable to access their servers located on the specified rack. Ongoing Actions : Our teams are investigating to determine the origin of the incident and 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
173
Days with an incident
90
Median duration
1 h 44 min
This incident
67% shorter than the median
Other OVHcloud incidents
All incidentsOVHcloud·[RBX2][Dedicated Servers] - Rack 22A04 Incident Notification
Dedicated Servers in Rack 22A04 in the RBX region are unavailable. The provider OVHcloud reports a network equipment issue. OVHcloud states that the incident is resolved and that it lasted about 110 minutes.
OVHcloud·[RBX-A][Public Cloud] - Compute Instance incident notification
We would like to inform you that an incident affected our Public Cloud offering in the RBX-A region. This incident has since been resolved. Please find the details of this incident below : Start time : 21/11/2026 06:19 UTC End time : 21/11/2026 06:46 UTC Impacted Service(s) : Some instances in the RBX-A region were temporarily unavailable. Customers Impact : Customers were temporarily unable to access their instances located in the specified region. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We thank you for your understanding and patience throughout this incident.
OVHcloud·[US-WEST-LZ-LAX][LocalZones] - VPS Incident Notification
We had an incident on our Virtual Private Servers offer which has now been resolved. Here are some supplementary details : Start time : 20/11/2026 15:59 UTC End time : 20/11/2026 18:53 UTC Impacted Service(s) : Some VPS in the Los Angeles Local Zone experienced partial connectivity issues. Customers Impact : Customers may have experienced connectivity issues when accessing their VPS located in the specified Local Zone. Root Cause : A service disruption occurred due to an unexpected infrastructure malfunction. We thank you for your understanding and patience throughout this incident.
OVHcloud·[RBX3][Dedicated Servers] - Rack 46N07 Incident Notification
Some Dedicated Servers in Rack 46N07 in the RBX region do not work. OVHcloud reports that the incident is resolved. The incident lasted 41 minutes, from 17:32 UTC to 18:13 UTC.
OVHcloud·[US][Backbone] - Backbone Incident Notification
We had an incident on our Backbone infrastructure which has now been resolved. Here are some supplementary details : Start time : 20/11/2026 14:52 UTC End time : 20/11/2026 15:16 UTC Impacted Service(s) : Packet loss and increased latency occurred on our backbone infrastructure in the US region. Customers Impact : Customers may have experienced packet loss and increased latency when accessing their services in the US region. Root Cause : This incident was caused by our provider. We thank you for your understanding and patience throughout this incident.
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