[RBX8][Dedicated Servers] - Rack RBX0840B05B incident notification
OVHcloud reports an incident with Dedicated Servers and the network in rack RBX0840B05B in the RBX region. The vRack network is temporarily unavailable in that rack. OVHcloud identified the cause and states a cooling system issue.
State
Identified
Started
Ongoing for
1 h 12 min
Worst impact
Partial outage
Timeline
1 updateIdentified
1 h 12 min 100%
Updates
Times in UTCAs posted by OVHcloud
We are currently experiencing an incident affecting our Dedicated Servers offering in the rack RBX0840B05B. The root cause has been identified. Please find the details of this incident below : Start time : 15/11/2026 14:20 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.
Affected components
2OVHcloud in the last 90 days
Full historyIncidents in 90 days
260
Days with an incident
90
Median duration
1 h 41 min
This incident
29% shorter than the median
Other OVHcloud incidents
All incidentsOVHcloud·[RBX8][Dedicated Servers] - Rack R820R14 incident notification
All servers in rack R820R14 were temporarily unavailable. The incident affected Dedicated Servers in the RBX region. OVHcloud reports that the incident is resolved. It lasted about 3 hours and 29 minutes and was caused by a cooling system issue.
OVHcloud·[BHS][Virtual Private Servers] - VPS incident notification
Some Virtual Private Servers in the BHS region did not work. OVHcloud states that the incident is resolved. The incident lasted from 06:34 UTC to 07:07 UTC.
OVHcloud·[BHS1/3/5][Public Cloud] - Compute Instance incident notification
OVHcloud reports that some Compute instances were unavailable in the BHS1, BHS3, and BHS5 regions. OVHcloud identified the cause and worked on a fix. The incident is resolved and lasted 33 minutes, from 06:34 UTC to 07:07 UTC.
OVHcloud·[Global][DNS] - .TN DNS Hosting incident notification
The ns1.tn.ovh.net DNS server was not available. This affected .TN domains that use only this server, and DNS resolution failed for them. OVHcloud reports that the incident is resolved. It lasted from 01:19 UTC to 02:30 UTC on 15/11/2026.
OVHcloud·[SGP1][Storage] - Block Storage incident notification
OVHcloud Block Storage volumes in the SGP1 region had degraded performance. OVHcloud reports that the incident is resolved. The incident lasted 58 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.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