[BHS7][Managed VMware vSphere] - Cluster81 incident notification
We are pleased to inform you that the incident affecting our Managed VMware vSphere offering on Cluster81 has been resolved. Start time : 07/10/2026 17:44 UTC End time : 07/10/2026 19:42 UTC Root Cause : This incident was caused by a cooling system issue. We apologize for any inconvenience caused and appreciate your understanding.
The latest update from OVHcloud.
State
Resolved
Started
25 d ago
2026-10-07 18:31 UTC
Lasted
1 h 19 min
until 2026-10-07 19:50 UTC
Worst impact
Partial outage
Timeline
3 updatesInvestigating
16 min 21%
Identified
1 h 3 min 79%
Updates
Times in UTCAs posted by OVHcloud
We are pleased to inform you that the incident affecting our Managed VMware vSphere offering on Cluster81 has been resolved. Start time : 07/10/2026 17:44 UTC End time : 07/10/2026 19:42 UTC Root Cause : This incident was caused by a cooling system issue. We apologize for any inconvenience caused and appreciate your understanding.
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Managed VMware vSphere offer on the specific Cluster81. Here are some supplementary details : Start time : 07/10/2026 17:44 UTC Impacted Service(s) : Cluster81 is temporarily unavailable. Customers Impact : Customers are temporarily unable to access their data located in the specified cluster. Root Cause : This incident is caused by a cooling system issue. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
We are currently investigating an incident affecting our Managed VMware vSphere offering, which is causing temporary availability issue in the Cluster81. Here are some supplementary details : Start time : 07/10/2026 17:44 UTC Impacted Service(s) : Cluster81 is temporarily unavailable. Customers Impact : Customers are temporarily unable to access their data located in the specified cluster. Ongoing Actions : Our teams are investigating to determine the origin of the incident and fix it. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
Affected components
2Follow 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.cc/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.cc/feed.xml?providers=ovhcloud/feed subscribe https://outages.cc/feed.xml?providers=ovhcloudFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane