rewindex

CompaniesOVHcloudIncidents

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

MajorStatus: monitoringeditedStarted Not resolved6 updateshosted-private-cloud.status-ovhcloud.com (opens in new tab)

Affected components: Managed VMware vSphere || SBG - Compute

Timeline of updates

  1. identified

    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.

  2. identified

    We have new information regarding the incident that affected your service(s).
    Please find below an update on the situation:
    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.

  3. identifiedDeleted by the vendor

    We have new information regarding the incident that affected your service(s).
    Please find below an update on the situation:
    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.

  4. identified

    We have new information regarding the incident that affected your service(s).
    Please find below an update on the situation:
    Update : A significant number of the hosts are operational again. Our technical team is still working on the incident to resolve it as quickly as possible.
    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.

  5. identified

    We have new information regarding the incident that affected your service(s).
    Please find below an update on the situation:
    Update : Our technical team is continuing to work on the incident.
    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.

  6. monitoring

    We would like to inform you that our service has been fully restored as of 13/11/2026 22:04 UTC. Monitoring is still in place to ensure long-term stability.
    Please find the details of this incident below :
    Start time : 13/11/2026 12:35 UTC
    Impacted Service(s) : Some servers in the rack S345A03 were temporarily unavailable.
    Customers Impact : Customers were temporarily unable to access their servers located on the specified rack.
    Root Cause : This incident was caused by a cooling system issue.
    We apologize for any inconvenience caused and appreciate your understanding.

Changes Rewindex caught on this incident

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 these records existed by then and have not been changed since, by anyone, Rewindex included.

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

Impact, status and times are the vendor’s own, as last archived. View on hosted-private-cloud.status-ovhcloud.com (opens in new tab).

Cite this

Status incident (vendor impact label: major) posted by OVHcloud, started 2026-11-13 12:54 UTC, not resolved, 6 update(s); edited after publishing.

Title
[SBG3][Managed VMware vSphere] - Racks S345A01, S345A02 incident notification
Vendor
OVHcloud
Date
URL
https://rewindex.com/company/ovhcloud/incidents/08xzsj2by8sl

OVHcloud profileRecent OVHcloud incidentsAll outages on November 13, 2026OVHcloud in November 2026MarkdownJSON