[RBX8][Dedicated Servers] - Racks RBX0841A05A and RBX0841A05B incident notification
OVHcloud reports that some Dedicated Servers in racks RBX0841A05A and RBX0841A05B in the RBX region are unavailable. OVHcloud identified a cooling system issue. All servers in rack RBX0841A05B and many servers in rack RBX0841A05A now work.
State
Identified
Started
Ongoing for
2 h 23 min
Worst impact
Partial outage
Timeline
3 updatesInvestigating
20 min 14%
Identified
2 h 3 min 86%
Updates
Times in UTCAs posted by OVHcloud
Please find an update of this incident below : Update : All servers in the rack RBX0841A05B are now operational. A significant number of servers in the rack RBX0841A05A are now operational. 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 Dedicated Servers offering in the racks RBX0841A05A and RBX0841A05B. The root cause has been identified. Please find the details of this incident below : Start time : 12/11/2026 13:09 UTC Impacted Service(s) : All servers in the racks RBX0841A05A and RBX0841A05B are temporarily unavailable. Customers Impact : Customers are temporarily unable to access their servers located on the specified racks. 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 racks RBX0841A05A and RBX0841A05B. Please find the details of this incident below : Start time : 12/11/2026 13:09 UTC Impacted Service(s) : All servers in the racks RBX0841A05A and RBX0841A05B are temporarily unavailable. Customers Impact : Customers are temporarily unable to access their servers located on the specified racks. 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
258
Days with an incident
90
Median duration
1 h 41 min
This incident
1.4× the median
Other OVHcloud incidents
All incidentsOVHcloud·[GRA3][Dedicated Servers] - Rack GRA0326A03B incident notification
OVHcloud reports that the public network did not work in rack GRA0326A03B in the GRA region. This affected Dedicated Servers. The incident is resolved. It lasted from 10:37 UTC to 14:35 UTC.
OVHcloud·[RBX/GRA/SBG][Collaborative Solutions] - EmailPro, Hosted Exchange, Private Exchange, MX Plan incident notification
OVHcloud reports that some management operations, such as password changes and account deletions, did not work on EmailPro, Hosted Exchange, Private Exchange and MX Plan in the RBX, GRA and SBG datacenters. OVHcloud says the incident is resolved. It lasted 1 hour and 41 minutes.
OVHcloud·[Global][Databases & Data Analytics] - API incident notification
OVHcloud reports that the API of PostgreSQL, MySQL, Valkey, ClickHouse, Dashboards, Kafka, Kafka Connect, Kafka MirrorMaker and OpenSearch had slowness and errors in BHS, DE, GRA, EU-WEST-PAR, EU-SOUTH-MIL, AP-SOUTH-MUM, RBX, SBG, SGP, UK and WAW. OVHcloud resolved the incident. The incident lasted 53 minutes, from 09:15 UTC to 10:08 UTC on 12 November 2026.
OVHcloud·[RBX3][Dedicated Servers] - Rack 43N06 incident notification
OVHcloud reports that some Dedicated Servers in rack 43N06 in the RBX region were unavailable. OVHcloud identified an electrical equipment issue. OVHcloud resolved the incident, which lasted about 74 minutes.
OVHcloud·[GRA3][Dedicated Servers] - Rack GRA0326A03B incident notification
OVHcloud Dedicated Servers on rack GRA0326A03B in the GRA region had a partial outage. Some servers were temporarily unavailable. OVHcloud identified a cooling system issue. OVHcloud resolved the incident. The incident lasted about 2 hours and 24 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