[SBG3][Cooling System] - Rack S357B07 maintenance notification
Scheduled maintenance is currently in progress. We will provide updates as necessary.
The latest update from OVHcloud.
State
In progress
Started
Ongoing for
1 h 55 min
Worst impact
Maintenance
Timeline
2 updatesScheduled
2 min 2%
In progress
1 h 52 min 98%
Updates
Times in UTCAs posted by OVHcloud
Scheduled maintenance is currently in progress. We will provide updates as necessary.
As part of our continuous improvement plan, we will be carrying out a maintenance on our cooling infrastructure. Start time : 10/11/2026 07:25 UTC End time : 10/11/2026 16:00 UTC List of concerned racks: - Rack S357B07 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
2OVHcloud in the last 90 days
Full historyIncidents in 90 days
249
Days with an incident
90
Median duration
1 h 40 min
This incident
Not comparable
Other OVHcloud incidents
All incidentsOVHcloud·[US][Infrastructure] - Backbone incident notification
OVHcloud reports a backbone incident in the US region. The US backbone has increased latency. OVHcloud identified the cause as a network equipment issue. The situation is mitigated, but latency can stay higher than usual while the network stabilizes.
OVHcloud·[SGP1][Dedicated Servers] - Rack 040816B incident notification
The public network does not work for OVHcloud Dedicated Servers in rack 040816B in the SGP region. OVHcloud reports that this incident is resolved. The outage lasted 15 minutes, from 06:54 UTC to 07:09 UTC. A network equipment issue caused the incident.
OVHcloud·[RBX8][Dedicated Servers] - Rack R809R07 incident notification
OVHcloud reports that some Dedicated Servers in rack R809R07 in the RBX region did not work. OVHcloud identified an electrical equipment issue. OVHcloud resolved the incident, which lasted 3 hours and 7 minutes.
OVHcloud·[BHS1][Dedicated Servers] - Rack T01C28 incident notification
The public network does not work for Dedicated Servers in rack T01C28 in the BHS region. OVHcloud reports that this incident is resolved. It lasted from 02:28 UTC to 06:12 UTC.
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.
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