[SBG3][Managed VMware vSphere] - Racks S345A01, S345A02 incident notification
Some hosts in racks S345A01 and S345A02 in SBG3 do not work. The Managed VMware vSphere service in the SBG region is affected. OVHcloud has identified the cause and states that a cooling system issue caused the outage.
State
Identified
Started
Ongoing for
57 min
Worst impact
Partial outage
Timeline
1 updateIdentified
57 min 100%
Updates
Times in UTCAs posted by OVHcloud
We are currently experiencing an incident affecting our Managed VMware vSphere offering in the racks S345A01 and S345A02 in SBG3. The root cause has been identified. Please find the details of this incident below : Start time : 13/11/2026 12:35 UTC Impacted Service(s) : Some hosts in the racks S345A01 and S345A02 are temporarily unavailable. Customers Impact : Customers are temporarily unable to access their hosts located on the specified racks. Root Cause : This incident is caused by a cooling system issue. Ongoing Actions : Our teams are actively working 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
262
Days with an incident
90
Median duration
1 h 41 min
This incident
43% shorter than the median
Other OVHcloud incidents
All incidentsOVHcloud·[SBG3][Dedicated Servers] - Rack S345A03 incident notification
Some dedicated servers in rack S345A03 in the SBG region do not work. OVHcloud reports that it identified the incident. The cause is a cooling system issue.
OVHcloud·[SYD][Dedicated Servers] - Room S2-5X incident notification
The public network did not work for OVHcloud Dedicated Servers in several racks of the SYD zone. OVHcloud reported a network equipment issue. OVHcloud resolved the incident after 53 minutes.
OVHcloud·[US-EAST-VA][Storage] - Object Storage Incident Notification
OVHcloud Object Storage in the US-EAST-VA region had a partial outage. High Performance and Standard Object Storage had increased latency and 500/503 errors. OVHcloud reports that the incident is resolved. The incident lasted 1 hour and 43 minutes.
OVHcloud·[RBX8][Dedicated Servers] - Racks RBX0841A05A and RBX0841A05B incident notification
OVHcloud Dedicated Servers in racks RBX0841A05A and RBX0841A05B were temporarily unavailable in the RBX region. OVHcloud reports that the incident is resolved. The incident lasted from 13:09 UTC to 18:36 UTC on 12/11/2026.
OVHcloud·[GRA3][Dedicated Servers] - Rack GRA0326A03B incident notification
OVHcloud reports that the public network did not work in rack GRA0326A03B in the GRA region. This affected Dedicated Servers. The incident is resolved. It lasted from 10:37 UTC to 14:35 UTC.
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