[RBX8][Cooling System] - Multiple racks maintenance notification
As part of our continuous improvement plan, we will be carrying out a maintenance on our cooling infrastructure. Start time: 16/11/2026 07:00 UTC End time: 16/11/2026 16:00 UTC List of concerned racks: - R820R13 - R822R15 - R809R03 - R808R01 Service impact: During this maintenance, the cooling system's efficiency may be temporarily reduced for some servers, potentially lowering performance. Despite ongoing mitigation efforts, customers could still experience a temporary reboot or shutdown in the worst case. Service improvement: As part of our continuous improvement policy, we will be doing a maintenance on our cooling infrastructure. Thank you for your understanding.
The latest update from OVHcloud.
State
Scheduled
Starts
Ongoing for
Not started
Worst impact
Maintenance
Updates
Times in UTCAs posted by OVHcloud
As part of our continuous improvement plan, we will be carrying out a maintenance on our cooling infrastructure. Start time: 16/11/2026 07:00 UTC End time: 16/11/2026 16:00 UTC List of concerned racks: - R820R13 - R822R15 - R809R03 - R808R01 Service impact: During this maintenance, the cooling system's efficiency may be temporarily reduced for some servers, potentially lowering performance. Despite ongoing mitigation efforts, customers could still experience a temporary reboot or shutdown in the worst case. Service improvement: As part of our continuous improvement policy, we will be doing a maintenance on our cooling infrastructure. Thank you for your understanding.
Affected components
1OVHcloud in the last 90 days
Full historyIncidents in 90 days
234
Days with an incident
90
Median duration
1 h 38 min
This incident
Not comparable
Other OVHcloud incidents
All incidentsOVHcloud·[GRA6][Storage] - Instance Backup incident notification
OVHcloud Public Cloud Instance Backup and image management are temporarily unstable in the GRA6 region. Customers may see failures when they create backups or manage images. OVHcloud reports that the incident is under investigation.
OVHcloud·[EU-WEST-PAR-B][Storage] - Block Storage incident notification
OVHcloud reports degraded performance on some Block Storage volumes in the EU-WEST-PAR-B region. This causes increased latency and reduced performance on affected volumes. OVHcloud is investigating the incident and its teams work to improve storage performance.
OVHcloud·[EU-WEST-PAR-A][Storage] - Block Storage incident notification
OVHcloud reports that Block Storage volumes in the EU-WEST-PAR-A region have performance degradation. Some volumes have increased latency and reduced performance. OVHcloud is investigating and its teams work to improve the storage infrastructure performance.
OVHcloud·[RBX8][Dedicated Servers] - Rack RBX0840B05B incident notification
All servers in rack RBX0840B05B of the OVHcloud Dedicated Servers offering in the RBX region are temporarily unavailable. OVHcloud identified the cause as an electrical equipment issue. Some servers in the rack are becoming operational again.
OVHcloud·[US/SYD][Infrastructure] - Backbone incident notification
We would like to inform you that an incident affected our Infrastructure offering. This incident has since been resolved. Please find the details of this incident below : Start time : 04/11/2026 13:37 UTC End time : 04/11/2026 14:00 UTC Impacted Service(s) : Increased latency was observed on the link between US and SYD. Customers Impact : Customers may have experienced increased latency when accessing their services passing from US and SYD. 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