[GRA3][Cooling System] - Rack GRA0317A01C
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 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
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 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
221
Days with an incident
90
Median duration
1 h 37 min
This incident
Not comparable
Other OVHcloud incidents
All incidentsOVHcloud·[BHS5][Dedicated Servers] - Racks T05B28, T05B29 incident notification
Some Dedicated Servers in racks T05B28 and T05B29 in the BHS5 region are temporarily unavailable. OVHcloud reports that the root cause is a cooling system issue. OVHcloud has identified the cause.
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.
OVHcloud·[DE1][Network] - Public network incident notification
OVHcloud reports a public network incident in the DE1 region. Network administrative tasks were slowed, and customers had errors or delays when they created or changed instance network settings. OVHcloud reports that the incident is resolved, and it lasted from 09:22 UTC to 18:32 UTC.
OVHcloud·[Global][Domains] - .TOP Domains Name incident notification
The .TOP domain operations do not work. Registration, Renew, Transfer, Restore, and Delete are affected in all regions. OVHcloud reports the state as identified. The cause comes from a provider.
OVHcloud·[SBG5][Dedicated Servers] - Rack SBG0505B05B incident notification
Some servers in rack SBG0505B05B were unavailable. This affected the Dedicated Servers offering in the SBG region. OVHcloud reports that the incident is resolved and that it lasted 2 hours and 52 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