[RBX8][Infrastructure] - Racks R803R22maintenance notification
As part of our continuous improvement plan, we will be carrying out a maintenance on our electrical infrastructure, on racks R803R22. Start time : 16/11/2026 05:00 UTC End time : 16/11/2026 16:00 UTC Service impact : Customers could still experience a temporary reboot or shutdown in the worst case of their servers. Service improvement : As part of our continuous improvement policy, we will be doing a maintenance on our electrical infrastructure. Thank you for your understanding.
The latest update from OVHcloud.
State
Resolved
Starts
Lasted
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 electrical infrastructure, on racks R803R22. Start time : 16/11/2026 05:00 UTC End time : 16/11/2026 16:00 UTC Service impact : Customers could still experience a temporary reboot or shutdown in the worst case of their servers. Service improvement : As part of our continuous improvement policy, we will be doing a maintenance on our electrical infrastructure. Thank you for 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 38 min
This incident
Not comparable
Other OVHcloud incidents
All incidentsOVHcloud·[BHS6][Dedicated Servers] - Rack T06F27 incident notification
The vRack network is temporarily unavailable for Dedicated Servers in rack T06F27 in the BHS region. OVHcloud reports that this incident is under investigation. OVHcloud states that teams are investigating the origin of the incident.
OVHcloud·[RBX8][Dedicated Servers] - Rack R808L04 incident notification
OVHcloud reports that the vRack network does not work for Dedicated Servers in rack R808L04 in the RBX region. OVHcloud identified the root cause and is working to restore service.
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.
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