OVHcloud: [RBX5][Dedicated Servers] - Rack 45D18 incident notification
OVHcloud reported a major outage starting 20/11/2026 08:07 UTC: the vRack network was unavailable for Dedicated Servers in RBX5 rack 45D18, preventing customers from accessing and using servers through vRack. The vendor said the root cause was identified but provided no details; the incident remained open when archived (0 min at the last update).
Machine-written from the archived incident (Sol). Check the timeline before relying on it.
Affected components: Dedicated Servers || Network - RBX
Timeline of updates
- identified
We are currently experiencing an incident affecting our Dedicated Servers offering in the rack 45D18. The root cause has been identified.
Please find the details of this incident below :
Start time : 20/11/2026 08:07 UTC
Impacted Service(s) : vRack network is temporarily unavailable in the rack 45D18.
Customers Impact : Customers are temporarily unable to access and use their servers through vRack network.
Root Cause : This incident is caused by a network equipment 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. - resolved
We would like to inform you that the incident affecting our Dedicated Servers offering has now been resolved.
Please find the details of this incident below :
Start time : 20/11/2026 08:07 UTC
End time : 20/11/2026 11:14 UTC
Impacted Service(s) : vRack network was temporarily unavailable in the rack 45D18.
Customers Impact : Customers were temporarily unable to access and use their servers through vRack network.
Root Cause : This incident was caused by a network equipment issue.
We thank you for your understanding and patience throughout this incident.
Changes Rewindex caught on this incident
- Major incident: [RBX5][Dedicated Servers] - Rack 45D18 incident notification
- Incident updated: [RBX5][Dedicated Servers] - Rack 45D18 incident notification
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.
How the archive is checked, and what it cannot prove.
Rewindex captured this after the last checkpoint; the next run () commits it.
Impact, status and times are the vendor’s own, as last archived. View on bare-metal-servers.status-ovhcloud.com (opens in new tab).
Cite this
Status incident (vendor impact label: major) posted by OVHcloud, started 2026-11-20 09:43 UTC, resolved after 2.6 h, 2 update(s); edited after publishing.
- Title
- [RBX5][Dedicated Servers] - Rack 45D18 incident notification
- Vendor
- OVHcloud
- Date
- URL
- https://rewindex.com/company/ovhcloud/incidents/p5v1j5y7zv7r
OVHcloud profileRecent OVHcloud incidentsAll outages on November 20, 2026OVHcloud in November 2026MarkdownJSON