# OVHcloud: Major incident: [SBG5][Dedicated Servers] - Rack SBG0506B04C Incident Notification

> Major incident: [SBG5][Dedicated Servers] - Rack SBG0506B04C Incident Notification. Detected 2026-11-18 by Rewindex: what changed on OVHcloud’s status page, with the before/after diff.

Canonical: https://rewindex.com/change/i22c4b6132aa4ca
Last updated: 2026-11-18T12:43:35Z

**Summary:** _summary pending_
- Kind: Major incident · Label: major (vendor)
- Changed: 2026-11-18 12:41 UTC · Detected: 2026-11-18 12:43 UTC
- [Source: https://bare-metal-servers.status-ovhcloud.com/incidents/6qcsdy4qs7n1](https://bare-metal-servers.status-ovhcloud.com/incidents/6qcsdy4qs7n1)
- [Company: OVHcloud](https://rewindex.com/company/ovhcloud.md)
- Versions: before (none: first archived) → after incident\_version:765/6qcsdy4qs7n1@c2b7f5313bbb
- Change 1 of 2 for this incident

Incident page (full timeline): [\[SBG5\]\[Dedicated Servers\] - Rack SBG0506B04C Incident Notification](https://rewindex.com/company/ovhcloud/incidents/6qcsdy4qs7n1.md)
## What changed

**1. Added: Title**

```diff
+ [SBG5][Dedicated Servers] - Rack SBG0506B04C Incident Notification
```

**2. Added: Impact**

```diff
+ major
```

**3. Added: Status**

```diff
+ identified
```

**4. Added: Start time**

```diff
+ 2026-11-18 12:41 UTC
```

**5. Added: Affected components**

```diff
+ Dedicated Servers || Network - SBG
```

**6. Added: Update** (identified) · 2026-11-18 12:41 UTC

```diff
+ We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Dedicated Servers offer in Rack SBG0506B04C. Here are some supplementary details : Start time : 18/11/2026 11:54 UTC Impacted Service(s) : vRack Private Network is temporarily unavailable on servers in rack SBG0506B04C. Customers Impact : Customers are temporarily unable to access their servers located in the specified rack via Vrack Private Network Root Cause : This incident is caused by a network equipment 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.
```

## History of this incident

| When (UTC) | Change | Label |
| --- | --- | --- |
| 2026-11-18 12:41 UTC | Major incident: \[SBG5\]\[Dedicated Servers\] - Rack SBG0506B04C Incident Notification (this change) | major |
| 2026-11-18 15:43 UTC | [Incident updated: \[SBG5\]\[Dedicated Servers\] - Rack SBG0506B04C Incident Notification](https://rewindex.com/change/r00c1c01a4a9194.md) |  |

Next: [change](https://rewindex.com/change/r00c1c01a4a9194.md) · All OVHcloud changes: [timeline](https://rewindex.com/company/ovhcloud/changes.md)
_Diff excerpts are shown on normalized text: dates, counters and tokens appear as ‹date›, ‹count›, ‹tok›; noise-only edits are hidden. Rewindex shows the changed passages, not a copy of the page._

## Cite this

Major incident: [SBG5][Dedicated Servers] - Rack SBG0506B04C Incident Notification on OVHcloud’s status page, changed 2026-11-18 12:41 UTC (change 1 of 2).

- Canonical URL: https://rewindex.com/change/i22c4b6132aa4ca
- Citation: OVHcloud, “Major incident: [SBG5][Dedicated Servers] - Rack SBG0506B04C Incident Notification” (2026-11-18 12:41 UTC). Archived by Rewindex: https://rewindex.com/change/i22c4b6132aa4ca (CC BY 4.0).
- Markdown link: `[OVHcloud: Major incident: SBG5Dedicated Servers - Rack SBG0506B04C Incident Notification (2026-11-18)](https://rewindex.com/change/i22c4b6132aa4ca)`


---
Canonical: https://rewindex.com/change/i22c4b6132aa4ca · Markdown: https://rewindex.com/change/i22c4b6132aa4ca.md · JSON: https://rewindex.com/api/v1/changes/i22c4b6132aa4ca · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-18T19:10:00.205Z
