rewindex

ChangesOVHcloud[SBG3][Managed VMware vSphere] - Racks S345A01, S345A02 incident notification

OVHcloud: Major incident: [SBG3][Managed VMware vSphere] - Racks S345A01, S345A02 incident notification

Major incidentmajor (vendor)Changed Detected hosted-private-cloud.status-ovhcloud.com (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

Struck in red is what OVHcloud removed; blue is what they added. Muted text is unchanged context.

AddedTitle#1
Before: not present
After: [SBG3][Managed VMware vSphere] - Racks S345A01, S345A02 incident notification
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: identified
AddedStart time#4
Before: not present
After: 2026-11-13 12:54 UTC
AddedAffected components#5
Before: not present
After: Managed VMware vSphere || SBG - Compute
AddedUpdateidentified#6
Before: not present
After: 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.

First version of this incident archived by Rewindex. View the live incident (opens in new tab).

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

History of this incident

YesterdayFriday, November 13Fri, Nov 13

6 incident changes

Cite this

Major incident: [SBG3][Managed VMware vSphere] - Racks S345A01, S345A02 incident notification on OVHcloud’s status page, changed 2026-11-13 12:54 UTC (change 1 of 6).

Title
Major incident: [SBG3][Managed VMware vSphere] - Racks S345A01, S345A02 incident notification
Vendor
OVHcloud
Date
URL
https://rewindex.com/change/i0cdc4abbc0b865

All OVHcloud changesOVHcloud profileMarkdownJSON