[RBX4][Cooling System] - Rack 53A05 maintenance notification
Scheduled maintenance is currently in progress. We will provide updates as necessary.
The latest update from OVHcloud.
State
In progress
Started
1 h ago
2026-11-02 08:00 UTC
Ongoing for
1 h 1 min
Worst impact
Maintenance
Timeline
2 updatesScheduled
3 min 6%
In progress
57 min 94%
Updates
Times in UTCAs posted by OVHcloud
Scheduled maintenance is currently in progress. We will provide updates as necessary.
As part of our continuous improvement plan, we will be carrying out maintenance on our cooling infrastructure. Start time : 02/11/2026 08:00 UTC End time : 02/11/2026 16:00 UTC 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 performing maintenance on our cooling infrastructure. Thank you for your understanding.
Affected components
2OVHcloud in the last 90 days
Full historyIncidents in 90 days
216
Days with an incident
90
Median duration
1 h 35 min
This incident
Not comparable
Other OVHcloud incidents
All incidentsOVHcloud·[Global][Domains] - .CO Domains Name incident notification
OVHcloud reports that multiple .CO domain operations do not work. Registration, Renew, Transfer, Restore, and Delete for .CO domains are affected. OVHcloud identified the cause and works with its provider to restore service.
OVHcloud·[ERI1][Dedicated Servers] - Rack E105A01 incident notification
OVHcloud reports that Dedicated Servers in rack E105A01 in the ERI region were unavailable. The incident is resolved. It lasted 5 minutes, from 07:38 to 07:43 UTC.
OVHcloud·[RBX3][Dedicated Servers] - Rack 42C19 incident notification
OVHcloud reports an incident that affects some Dedicated Servers in rack 42C19 in the RBX region. These servers were temporarily unavailable. OVHcloud identified an electrical equipment issue as the cause. The incident is resolved. It lasted from 05:48 UTC to 07:18 UTC.
OVHcloud·[SBG8][Virtual Private Servers] - VPS Incident Notification
OVHcloud reports that some Virtual Private Servers in the SBG8 region were temporarily unreachable. OVHcloud identified the cause as a network equipment issue. The incident is resolved and lasted about 1 hour and 59 minutes.
OVHcloud·[SBG6/8][Virtual Private Servers] - VPS Incident Notification
We are pleased to inform you that the incident affecting our VPS offering has been resolved. Start time : 01/11/2026 17:55 UTC End time : 01/11/2026 19:30 UTC Root Cause : This incident was caused by a network equipment issue. We apologize for any inconvenience caused and appreciate your understanding.
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