outages.live
Live
OVHcloudIncident ·

[RBX8][Dedicated Servers] - Rack R808L04 incident notification

Partial outageOfficial update
0

OVHcloud reports the vRack network is temporarily unavailable in rack R808L04. This affects Dedicated Servers in the RBX region. OVHcloud identified a cooling system issue as the root cause, and teams are working to restore service. The incident started at 23:47 UTC on 05/11/2026.

State

Identified

Started

Ongoing for

1 h 8 min

Worst impact

Partial outage

Timeline

2 updates
23:5500:1200:2900:4601:03
Partial outageUpdate postedTimes in UTC

Investigating

26 min 38%

Identified

43 min 62%

Updates

Times in UTC

As posted by OVHcloud

Identified

We are currently experiencing an incident affecting our Dedicated Servers offering in the rack R808L04. The root cause has been identified. Please find the details of this incident below : Start time : 05/11/2026 23:47 UTC Impacted Service(s) : vRack network is temporarily unavailable in the specified rack. Customers Impact : Customers are temporarily unable to access and use their servers through vRack network. 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.

Investigating

We are currently experiencing an incident affecting our Dedicated Servers offering, which is causing temporary availability issues in the rack R808L04. Please find the details of this incident below : Start time : 05/11/2026 23:47 UTC Impacted Service(s) : vRack network is temporarily unavailable in the specified rack. Customers Impact : Customers are temporarily unable to access and use their servers through vRack network. Ongoing Actions : Our teams are investigating to determine the origin of the incident to fix it. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

Affected components

2
RBXDedicated Servers || Network - RBX

OVHcloud in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

237

Days with an incident

90

Median duration

1 h 38 min

This incident

30% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

41 days
median 1 h 38 min
90 days agoToday

Other OVHcloud incidents

All incidents

OVHcloud·[BHS6][Dedicated Servers] - Rack T06F27 incident notification

The vRack network is not available in rack T06F27 of the BHS region. This affects the Dedicated Servers offering. OVHcloud reports that it is investigating the incident.

Partial outage

OVHcloud·[GRA6][Virtual Private Servers] - VPS incident notification

OVHcloud reports that backup and image management for Virtual Private Servers did not work correctly in the GRA6 region. The incident is resolved. It started at 15:26 UTC and ended at 18:35 UTC on 05 November 2026.

Resolved

OVHcloud·[GRA6][Storage] - Instance Backup incident notification

OVHcloud reports that Instance Backup and image management were unstable in the GRA6 region. Customers may have had failures when they created backups or managed images. OVHcloud states that the incident is resolved and lasted 1 hour and 39 minutes.

Resolved

OVHcloud·[EU-WEST-PAR-B][Storage] - Block Storage incident notification

OVHcloud reports degraded performance on some Block Storage volumes in the EU-WEST-PAR-B region. This causes increased latency and reduced performance on affected volumes. OVHcloud is investigating the incident and its teams work to improve storage performance.

Degraded

OVHcloud·[EU-WEST-PAR-A][Storage] - Block Storage incident notification

OVHcloud reports that Block Storage volumes in the EU-WEST-PAR-A region have performance degradation. Some volumes have increased latency and reduced performance. OVHcloud is investigating and its teams work to improve the storage infrastructure performance.

Degraded

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.

Prompt
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.

RSS
https://outages.live/feed.xml?providers=ovhcloud
Slack
/feed subscribe https://outages.live/feed.xml?providers=ovhcloud

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane