[BHS8][Cooling System] - Rack BHS0810A02C
As part of our continuous improvement plan, we will be carrying out a maintenance on our cooling infrastructure. Start time: 19/11/2026 12:00 UTC End time: 19/11/2026 20:30 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
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: 19/11/2026 12:00 UTC End time: 19/11/2026 20:30 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
255
Days with an incident
90
Median duration
1 h 41 min
This incident
Not comparable
Other OVHcloud incidents
All incidentsOVHcloud·[GLOBAL][Network] - API Network incident notification
OVHcloud reports that API requests on VPS services do not work correctly in the BHS, ERI, GRA, LIM, SBG, SGP, SYD, UK2, WAW, MIL, YNM, EU-WEST-LZ-MRS, US-EAST-LZ-ATL, US-EAST-LZ-DAL, US-EAST-LZ-MIA, US-EAST-LZ-NYC, US-EAST-VA, US-WEST-LZ-PAO, US-WEST-OR and EU-WEST-LZ-DLN regions. Customers can get slow responses or intermittent HTTP 500 errors. OVHcloud resolved the incident. It lasted 113 minutes.
OVHcloud·[EU/CA/MUM][Network] - API Network incident notification
OVHcloud API requests on the public cloud did not work in the BHS, DE, GRA, RBX, SBG, SGP, SYD, and UK regions. The US region was not affected. OVHcloud reports that the incident is resolved. It lasted 2 hours and 9 minutes.
OVHcloud·[DE2][Virtual Private Servers] - Some VPS incident notification
Some Virtual Private Servers did not work in the DE2 region. The affected components were LIM and Virtual Private Servers Global Infrastructure - LIM. OVHcloud reports that the incident is resolved. It lasted from 08:35 UTC to 10:23 UTC on 11 November 2026.
OVHcloud·[DE1][Compute - Instance] - Some instances incident notification
Some Compute instances in the DE1 region did not work. OVHcloud reports that the incident is resolved. The incident lasted from 08:35 UTC to 10:23 UTC.
OVHcloud·[CHI/BHS][Backbone] - Backbone incident notification
We had an incident on Backbone offer which has now been resolved. Here are some supplementary details : Start time : 11/11/2026 05:40 UTC End time : 11/11/2026 06:40 UTC Impacted Service(s) : Network traffic experienced temporary latency between BHS and CHI. Customers Impact : Customers may have temporarily experienced network latency between CHI and BHS. Root Cause : This incident was caused by a network equipment issue. 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