[SBG5][Cooling System] - Rack SBG0506B07D
As part of our continuous improvement plan, we will be carrying out a maintenance on our cooling infrastructure. Start time: 17/11/2026 07:00 UTC End time: 17/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
Resolved
Starts
Lasted
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: 17/11/2026 07:00 UTC End time: 17/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
247
Days with an incident
90
Median duration
1 h 39 min
This incident
Not comparable
Other OVHcloud incidents
All incidentsOVHcloud·[RBX8][Dedicated Servers] - Rack R809R07 incident notification
Some OVHcloud dedicated servers in rack R809R07 in the RBX region are unavailable. OVHcloud identified the cause as an electrical equipment issue. OVHcloud teams are working to restore service.
OVHcloud·[BHS1][Dedicated Servers] - Rack T01C28 incident notification
OVHcloud reports a partial outage of Dedicated Servers public network in rack T01C28 in the BHS region. Since 03:15 UTC, the public network in this rack is unavailable. OVHcloud identified a network equipment issue and its teams work to restore service.
OVHcloud·[Global][Collaborative Solutions] - Zimbra incident notification
OVHcloud reports that access to Zimbra mailboxes and webmail was unavailable. The affected components are Web Access and Zimbra Web Access. OVHcloud says the incident is resolved, and it lasted about 53 minutes.
OVHcloud·[Global][Collaborative Solutions] - Zimbra Incident Notification
OVHcloud reports slow delivery to some Zimbra mailboxes and webmail accounts. The incident affects the Zimbra Delivery email component. OVHcloud identified the root cause and its teams are working to restore service. Incoming emails are queued.
OVHcloud·[GLOBAL][Domains] - .DK Domain Names Incident Notification
OVHcloud reports that multiple operations on .DK domain names do not work. Registration, Renew, Transfer, Restore, and Delete are affected for .DK domain names. OVHcloud identified the root cause and teams are working to restore service.
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