[BHS][Managed VMware vSphere] - Rack BHS0816B04B incident notification
We are pleased to inform you that the incident affecting our Managed VMware vSphere offering has been resolved. Start time : 29/08/2026 06:00 UTC End time : 29/08/2026 09:04 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
65 d ago
2026-08-29 06:03 UTC
Lasted
3 h 29 min
until 2026-08-29 09:33 UTC
Worst impact
Partial outage
Timeline
2 updatesIdentified
3 h 29 min 100%
Updates
Times in UTCAs posted by OVHcloud
We are pleased to inform you that the incident affecting our Managed VMware vSphere offering has been resolved. Start time : 29/08/2026 06:00 UTC End time : 29/08/2026 09:04 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 BHS regions. Here are some supplementary details : Start time : 29/08/2026 06:00 UTC Impacted Service(s) : Some hosts are temporarily unavailable. Customers Impact : Some customers are temporarily unable to access their hosts located on the specified rack. 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.
Affected components
2OVHcloud in the last 90 days
Full historyIncidents in 90 days
213
Days with an incident
90
Median duration
1 h 35 min
This incident
2.2× the median
Other OVHcloud incidents
All incidentsOVHcloud·[SBG8][Virtual Private Servers] - VPS Incident Notification
OVHcloud reports that some Virtual Private Servers in the SBG8 region were temporarily unreachable. OVHcloud identified the cause as a network equipment issue. The incident is resolved and lasted about 1 hour and 59 minutes.
OVHcloud·[SBG6/8][Virtual Private Servers] - VPS Incident Notification
We are pleased to inform you that the incident affecting our VPS offering has been resolved. Start time : 01/11/2026 17:55 UTC End time : 01/11/2026 19:30 UTC Root Cause : This incident was caused by a network equipment issue. We apologize for any inconvenience caused and appreciate your understanding.
OVHcloud·[RBX3][Dedicated Servers] - Rack 46E19 Incident Notification
We are pleased to inform you that the incident affecting our Dedicated Servers offering has been resolved. Start time : 01/11/2026 17:15 UTC End time : 01/11/2026 19:38 UTC Root Cause : This incident was caused by a network equipment issue. We apologize for any inconvenience caused and appreciate your understanding.
OVHcloud·[SBG5/7][Compute - Instance] - Compute Instance Incident Notification
We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. Start time : 01/11/2026 17:55 UTC End time : 01/11/2026 19:30 UTC Root Cause : A service disruption occurred due to an unexpected infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.
OVHcloud·[RBX2][Dedicated Servers] - Rack 21D12 Incident Notification
We are pleased to inform you that the incident affecting our Dedicated Servers offering has been resolved. Start time : 31/10/2026 19:38 UTC End time : 31/10/2026 22:10 UTC Root Cause : This incident was caused by an electrical equipment issue. We apologize for any inconvenience caused and appreciate your understanding.
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