[LIM3][Cooling System] - Rack LIM0301B04B
As part of our continuous improvement plan, we will be carrying out a maintenance on our cooling infrastructure. Start time: 11/11/2026 06:00 UTC End time: 11/11/2026 15: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
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: 11/11/2026 06:00 UTC End time: 11/11/2026 15: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
229
Days with an incident
90
Median duration
1 h 36 min
This incident
Not comparable
Other OVHcloud incidents
All incidentsOVHcloud·[GRA][Web Hosting] - Some Filerz incident notification
OVHcloud reports that some websites on some Filerz were temporarily unavailable in the GRA region. The affected components include clusters 100 to 128. OVHcloud reports that the incident is resolved. It started at 20:20 UTC and ended at 21:05 UTC, so it lasted 45 minutes.
OVHcloud·[GLOBAL][Dedicated Servers] - Administrative network task incident notification
OVHcloud reports that administrative changes to public and private network settings did not work on Dedicated Servers. The affected regions include BHS, CCH, ERI, GRA, IEB, LIM, MR9, RBX, SBG, SGP, SYD, WAW, YNM, YYZ, US-EAST-VA, US-WEST-OR and US-WEST-LZ-SEA. OVHcloud resolved the incident, which lasted about 13 hours and 18 minutes.
OVHcloud·[DE1][Network] - Load balancer incident notification
The load balancer delivery service in the DE1 region did not work. OVHcloud reports that the incident is resolved. The incident lasted from 17:00 UTC to 19:13 UTC.
OVHcloud·[GRA11][Network] - Network API incident notification
OVHcloud reports that the Network API for the public network and the private network (vRack) was unstable in the GRA11 region. The Managed Kubernetes Service in GRA11 was also affected. OVHcloud says that the incident is resolved and that it lasted about 6 hours and 18 minutes.
OVHcloud·[Global][Dedicated Servers] - Delivery incident notification
OVHcloud Dedicated Servers delivery was degraded. The processing of suspension and reactivation requests was delayed in Zone Europe, Zone APAC, and Zone Canada. OVHcloud reports that the incident is resolved. It lasted about 7 hours and 25 minutes.
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