[SBG5][Cooling System] - Rack SBG0506A07C
As part of our continuous improvement plan, we will be carrying out a maintenance on our cooling infrastructure. Start time: 10/11/2026 07:00 UTC End time: 10/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 doing a maintenance on our cooling infrastructure. Thank you for your understanding.
The latest update from OVHcloud.
State
Scheduled
Starts
in 7 d
2026-11-10 07:00 UTC
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: 10/11/2026 07:00 UTC End time: 10/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 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
224
Days with an incident
90
Median duration
1 h 37 min
This incident
Not comparable
Other OVHcloud incidents
All incidentsOVHcloud·[DE1][Network] - Network API incident notification
OVHcloud reports that the Network API for the public network and the private network (vRack) is unstable in the DE1 region. Customers can get API errors when they create, change, or manage public and private network (vRack) configurations in DE1. OVHcloud is investigating the cause.
OVHcloud·[EU-WEST-PAR][Storage] - Object Storage incident notification
OVHcloud Object Storage has latency problems in the EU-WEST-PAR region. This affects the EU-WEST-PAR-A, EU-WEST-PAR-B, and EU-WEST-PAR-C components. OVHcloud reports that it is investigating the incident.
OVHcloud·[Global][AI & Machine Learning] - AI Notebooks, AI Training, AI Deploy incident notification
We would like to inform you that an incident affected our AI & Machine Learning offering. This incident has since been resolved. Please find the details of this incident below : Start time : 31/10/2026 07:08 UTC End time : 31/10/2026 07:58 UTC Impacted Service(s) : AI Notebooks, AI Training and AI Deploy services were temporarily unavailable. Customers Impact : Customers were temporarily unable to create, manage or access their notebooks, training jobs and AI applications. Root Cause : This incident was caused by a software issue. We thank you for your understanding and patience throughout this incident.
OVHcloud·[BHS5][Dedicated Servers] - Racks T05B28, T05B29 incident notification
Some Dedicated Servers in racks T05B28 and T05B29 in BHS5 were unavailable. OVHcloud reports that the incident is resolved. The incident lasted about 1 hour.
OVHcloud·[RBX8][Dedicated Servers] - Rack R809R19 Incident Notification
OVHcloud Dedicated Servers in Rack R809R19 at RBX were temporarily unavailable. OVHcloud reports that the incident is resolved. The incident lasted from 03:33 UTC to 04:49 UTC.
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